Hi, > The implementation is currently that if you "forget" to remove it from the > index it will be filtered out of the query result silently... but over time > that list of dead entities could grow, if the index couldn't somehow > self-heal, which it definately could... well a lot could be done there.
Yes. This is what I noticed: I was deleting vertices/edges, and when querying the index, they were not returned. So I assumed that you had "auto clearing" in the Index implementation. I was excited. However, now I see its a "silent delete" on query. Now, I suppose in Blueprints, I can, for every deleted vertex/edge, go through the indices and remove them for every key/value property they have. However, this is time consuming and would yield slow delete speeds. Thoughts? Should I just let the "silent delete" happen? Will there be plans to automagically remove non-existent PropertyContainers from the indices? Thank you for your time, Marko. _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
