[
https://issues.apache.org/jira/browse/LUCENE-8798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838508#comment-16838508
]
Atri Sharma commented on LUCENE-8798:
-------------------------------------
[~sokolov] Yes, as I commented in the other JIRA, this idea does not directly
relate to the CollectorScorer patch, but came as an outcome of reading through
it.
This is more of a readability and clarity perspective proposal – considering
that LeafReaderContext allows initialization without assigning a specific
ordinal, there should be an unique identifier which will be valid for any
constructed LeafReaderContext – irrespective of which constructor initialized
it.
My primary use case is to allow a secure way of storing in memory runtime
metadata about segments during a search execution, hence the invariant that the
ID has no relevance outside the scope of the owning IndexSearcher. Making
persistent IDs that get written to segment blocks is an interesting idea, but
is not what I planned to originally propose.
> Autogenerated ID for LeafReaderContexts Within An IndexSearcher
> ---------------------------------------------------------------
>
> Key: LUCENE-8798
> URL: https://issues.apache.org/jira/browse/LUCENE-8798
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Atri Sharma
> Priority: Minor
>
> It would be good to be able to uniquely identify LeafReaderContext objects
> associated within a single IndexSearcher. This would allow storing of
> metadata around segments, such as demonstrated in
> https://issues.apache.org/jira/browse/LUCENE-879
> The ID will be unique across the IndexSearcher instance and will make no
> guarantees of any semantic value outside the instance.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
