[
https://issues.apache.org/jira/browse/LUCENE-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712413#action_12712413
]
Earwin Burrfoot commented on LUCENE-1654:
-----------------------------------------
We can start with string key-value pairs per-segment that are created only from
inside Lucene and leave everything else for the latter.
What I'm trying to avoid is writing a partial solution, then a more generic one
(with different implementation) and having to keep that partial solution around
because it was already released. I.e. you're going to extend segment file
format, right? Let it be key-value pairs from the start, instead of a single
Int that is predetermined to be Lucene's version.
> Include diagnostics per-segment when writing a new segment
> ----------------------------------------------------------
>
> Key: LUCENE-1654
> URL: https://issues.apache.org/jira/browse/LUCENE-1654
> Project: Lucene - Java
> Issue Type: Improvement
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 2.9
>
>
> It would be very helpful if each segment in an index included
> diagnostic information, such as the current version of Lucene.
> EG, in LUCENE-1474 this would be very helpful to see if certain
> segments were written under 2.4.0.
> We can start with just the current version.
> We could also consider making this extensible, so you could provide
> your own arbitrary diagnostics, but SegmentInfo/s is not public so I
> think such an API would be "one-way" in that you'd have to use
> CheckIndex to check on it later. Or we could wait on such extensibility
> until we provide some consistent way to access per-segment details
> in the index.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
