shopwarelabs / storage Goto Github PK

To remove all entries in the storage

Add how-to guide in the readme for local setups, including dynamo-db

Also add how-to guide regarding implementing new storages

Documentation should be done via php docblocks

Also provide examples in the docblock which are unit tested

Add documentation CI

Umlauts seems not working. Revert the \Meilisearch\MeilisearchSearchTest::match "Umlauts" case and make it running :)

• We want to support custom documents, but with doc blocks as properties
• Add support for nested objects

Each storage should have a setup function which generates the required tables/collections/indices whatever

This function should also support to update the storage, if the schema changed.

There are some tests in the FilterStorage test base which are disabled (object fields with null value)

How to allow "fallback-field" logic like translations.

Would be nice if you can define a key from the context and it uses this as fallback logic.

Each directory inside /src should be an own repository that projects just need to include the different engines they need

Currently there are just tests for single filters. Operators are not tested yet

• With keys in criteria
• Multiple filter tests
• Multiple aggregations at the same time

There are currently no test for translated fields inside objects or object-lists

To completly destroy the storage

How to have an unkown json blob.

Tests for:

• Scalar fields
• Object fields
• Translated fields
• Object+translated fields
• Multi sorting
• Null values

Following aggregations are not supported by opensearch, and got pre-catched in the storage

• Min/Max/Avg/Sum agg on text and string fields
• Distinct/Count agg on text fields

Current suggestions:

1. "ASS" - Abstract search storage
2. "ADS" - Abstract document storage
3. "DSE" - Document Search Engine
4. "SES" - Search Engine Storage

Add new mongodb storage for KeyValue implementation.

https://typesense.org/docs/26.0/api/search.html

Get mysql running in unit test

it would be nice, if we could exchange as much arrays as possible with simple objects with typed properties. first thing I saw, were the sorting and filter arrays

• Adding and removing properties
• Changing data type?

Filters, sortings, etc should be created via static factory methods

influx db

keydb

dragonflyDB

garnet

RocksDB

Sometimes it would be nice to check if a specific filter is set to a criteria.
It also helps consumers to remove this element from the criteria.
It also helps for error reporting

Provide tests which ensure that the storages can be extended.

Allow also patterns like cursor / last-id

Don't allow to deep nesting for "additional" fields on a schema (third party). Provide a config

To identify the source of each criteria, i want to enforce setting a title