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
Some of these IndexingConstants are based on what ElasticSearch does by default. Changing this means changing the default naming convention of ElasticSearch.
As for the ContentItem it is a question of taste. I prefer how they actually are because they reflect how the shape is built. In the end what you are doing is removing the "Content" part to shorten the name here. If you are changing these, you are also breaking everyone's integrations.
Some of these IndexingConstants are based on what ElasticSearch does by default. Changing this means changing the default naming convention of ElasticSearch.
By using the dot notation we are inferring that these are nested properties (sub fields) of a composite object when in fact its just a flat field.
Also when running queries we view them as fields.
Just think it would be cleaner to treat the mappings as flat objects
Currently the indexing constants when using elastic search use the dot notatation in the name :
When creating an index in elasticsearch the mappings are structured in a hierarchy based on the dot notation and not as a flat property as expected.
this makes it difficult to read and follow .
I propose to remove the dot notation and use an underscore and make the constant names more shorter as so :
@Skrypt @MikeAlhayek any reason not to do this ?
Before i submit a PR.
The text was updated successfully, but these errors were encountered: