You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adds the ability to define the `dynamic` property for collection mapping.
This property can take 3 values:
- "true": Stores the document and updates the collection mapping with inferred type
- "false": Stores the document and does not update the collection mapping (fields are not indexed)
- "strict": Rejects document
See https://www.elastic.co/guide/en/elasticsearch/guide/current/dynamic-mapping.html
This is configurable in the `kuzzlerc` within the `server.db.dynamic` property.
The default value is `true` which allows the user to push arbitrary documents to Kuzzle and Elasticsearch will try to infer the corresponding mapping. (This is the current behaviour in Kuzzle)
Admin-Console (wip): kuzzleio/kuzzle-admin-console#502
Documentation: kuzzleio/documentation#271
## Other changes
Fixed the usage of the `_meta` property for ES collection. This property must be passed to each call to `putMapping`.
See #1268
chmod 777 on `node_modules/` because I'm tired of doing `sudo chmod +x node_modules/.bin/*` to run test locally
Expected Behavior
Set a
_meta
field on a collection, restart and be able to see the_meta
field.Current Behavior
The field has disappeared after the reload.
Possible Solution
Could this be tied to the
indexCache
?Steps to Reproduce
See the Expected Behavior.
The text was updated successfully, but these errors were encountered: