[jira] [Issue Comment Deleted] (SOLR-9506) cache IndexFingerprint for each segment

["Keith Laban (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Laban updated SOLR-9506:
------------------------------
    Comment: was deleted

(was: Are you implying that if you add a document. commit it, compute the index fingerprint and cache the segments. Then delete that document and commit that change, and compute the fingerprint again with the cached segment fingerprint, you will end up with the same index fingerprint?)

> cache IndexFingerprint for each segment
> ---------------------------------------
>
>                 Key: SOLR-9506
>                 URL: https://issues.apache.org/jira/browse/SOLR-9506
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Noble Paul
>         Attachments: SOLR-9506.patch, SOLR-9506.patch, SOLR-9506_POC.patch
>
>
> The IndexFingerprint is cached per index searcher. it is quite useless during high throughput indexing. If the fingerprint is cached per segment it will make it vastly more efficient to compute the fingerprint



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org