[jira] Updated: (LUCENE-1654) Include diagnostics per-segment when writing a new segment

["Michael McCandless (JIRA)" <ji...@apache.org>]

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

Michael McCandless updated LUCENE-1654:
---------------------------------------

    Attachment: LUCENE-1654.patch

OK I added per-segment private storage of diagnostics within IW.  It
records the current Lucene version plus OS & Java version details, and
the reason for the segment (flush or merge) as a Map<String, String>.

I also changed the commitUserData to be a Map<String,String> too.
This API has not yet been released so we are free to change it.

CheckIndex now prints both the commit level and per-segment level
maps.

I added Constants.LUCENE_VERSION to record the current version.  I try
to look up the impl version from the manifest and use that, else I
fallback to a String constant (now 2.9-dev).  I also added a unit test
that asserts this value matches what's in common-build.xml.

When I commit I'll update ReleaseTodo on the wiki to remember to
update this value.

I plan to commit in a day or two.


> 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
>
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org