Flowpack.ElasticSearch.ContentRepositoryAdaptor
Flowpack.ElasticSearch.ContentRepositoryAdaptor copied to clipboard
Flowpack
Moving a node leads to double-indexed nodes
Currently, the identifier of the elasticsearch document is calculated using the nodepath. When a node is moved, a new document with a new identifier is added to the index instead of updating the existing.
why not use the identifier instead of the node-path when finding the nodes to delete/create on move? the identifier doesn't change when moving it, right?
why not use the identifier instead of the node-path when finding the nodes to delete/create on move? the identifier doesn't change when moving it, right?
Don't remember why we use the context path for this document identifier ... sounds odd ... but some memories could be nice .... maybe in the past the node uuid change during a move operation ?
We've been running a "patched" version of this that does exactly this (use the Identifier) without a problem. I thought we did a pull request back then, but apparently not. Maybe @remuslazar can provide a pull request?
