[
https://issues.apache.org/jira/browse/SOLR-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Chattopadhyaya updated SOLR-9506:
---------------------------------------
Attachment: SOLR-9506-combined-deletion-key.patch
While working on SOLR-5944, I realized that the current per segment caching
logic works fine for deleted documents (due to comparison of numDocs in a
segment for the criterion of cache hit/miss). However, if a segment has
docValues updates, the same logic is insufficient. It is my understanding that
changing the key for caching from reader().getCoreCacheKey() to
reader().getCombinedCoreAndDeletesKey() would work here, since the docValues
updates are internally handled using deletion queue and hence the "combined"
core and deletes key would work here. Attaching a patch for the same.
> 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-combined-deletion-key.patch, SOLR-9506.patch,
> SOLR-9506.patch, SOLR-9506.patch, SOLR-9506.patch, SOLR-9506_POC.patch,
> SOLR-9506_final.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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
