lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Earwin Burrfoot (JIRA)" <>
Subject [jira] Commented: (LUCENE-1654) Include diagnostics per-segment when writing a new segment
Date Tue, 26 May 2009 16:32:47 GMT


Earwin Burrfoot commented on LUCENE-1654:

bq. It's the reading side of that API that makes me nervous (SegmentInfo/s is not public).
No-no-no, don't open it up, it's suicidal :)

We can theoretically allow access to per-segment data from segment readers, as they have 1-1
So, when I finish always-use-MSR patch, you should be able to get per-commit data from MSR
and per-segment from SR using the same API. Sounds somewhat dirty, but would work well...
needs more thought.

> Include diagnostics per-segment when writing a new segment
> ----------------------------------------------------------
>                 Key: LUCENE-1654
>                 URL:
>             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:
For additional commands, e-mail:

View raw message