<p dir="auto"><a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/dcolebatch/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/dcolebatch">@dcolebatch</a>: 'There is conflicting reports out there, some google group posts say you can disable vertex ID reuse[1], some say you can't[2].</p>
<p dir="auto">We'd love to be able to disable ID reuse in embedded mode and think it could be documented in Chapter 21[3] if it is there already... ?</p>
<p dir="auto">1: <a href="https://groups.google.com/forum/?fromgroups#!searchin/neo4j/node$20ID/neo4j/wn5sQA1BFf4/T-siwqtof5QJ" rel="nofollow">https://groups.google.com/forum/?fromgroups#!searchin/neo4j/node$20ID/neo4j/wn5sQA1BFf4/T-siwqtof5QJ</a><br>
2: <a href="https://groups.google.com/forum/#!topic/neo4j/ilq7624PwaU" rel="nofollow">https://groups.google.com/forum/#!topic/neo4j/ilq7624PwaU</a><br>
3: <a href="http://docs.neo4j.org/chunked/milestone/embedded-configuration.html" rel="nofollow">http://docs.neo4j.org/chunked/milestone/embedded-configuration.html</a><br>
'</p>
<p dir="auto"><a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/cheadp/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/cheadp">@cheadp</a>: 'On node deletion, related indexes entries will be removed only when the next query on those indexes occurs and should return the deleted node.<br>
As indexes work with internal node id, and as they can be recycled, not removing indexes entries when a node is deleted can lead to index corruption (and happened in one of our pre-production database)</p>
<p dir="auto">As it was told, indexing will be refactored in a futur milestone.<br>
But I think a good thing to do now is to add a warning in the manual about this issue, and advice users to always think about removing indexes entries'</p>