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
Currently, single operation hashing (index/delete/get) is using the type as part of the hashing to decide which shard to direct to. It make more sense to just use the id for several reasons.
First, the new routing control capability will allow to direct docs to be placed in the same placement of another doc (blog, and commends for example) just based on that doc id (the routing when indexing a comment can use the blog post id, and thats it).
There are future features where this type of hashing will really simplify them, so it make sense to make this change now.
This change will require to reindex the data. In order to revert back to using the type for hashing as well, set cluster.routing.operation.use_type to true. This means that a cluster can be started by setting this flag, start another cluster, and reindex data from the old cluster into the new cluster.
The text was updated successfully, but these errors were encountered:
Currently, single operation hashing (index/delete/get) is using the type as part of the hashing to decide which shard to direct to. It make more sense to just use the id for several reasons.
First, the new routing control capability will allow to direct docs to be placed in the same placement of another doc (blog, and commends for example) just based on that doc id (the routing when indexing a comment can use the blog post id, and thats it).
There are future features where this type of hashing will really simplify them, so it make sense to make this change now.
This change will require to reindex the data. In order to revert back to using the type for hashing as well, set
cluster.routing.operation.use_type
totrue
. This means that a cluster can be started by setting this flag, start another cluster, and reindex data from the old cluster into the new cluster.The text was updated successfully, but these errors were encountered: