[
https://issues.apache.org/jira/browse/LUCENE-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713169#action_12713169
]
Michael McCandless commented on LUCENE-1654:
--------------------------------------------
OK let's hold off on the public API.
Jason can you give an example of how you'd use this in LUCENE-1313? I don't
see the connection. The initial intention was exactly cases like LUCENE-1474
where I'd really like to know which Lucene version wrote a given segment, in
helping to debug.
> 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
>
> Attachments: LUCENE-1654.patch, LUCENE-1654.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
