lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3760) Cleanup DR.getCurrentVersion/DR.getUserData/DR.getIndexCommit().getUserData()
Date Wed, 08 Feb 2012 22:53:00 GMT


Michael McCandless commented on LUCENE-3760:

bq. what are the high-level use-cases for these static methods?

Well, they let you get the version and commit userData w/o having to open the full index...
it's a nice "freedom" (much lower cost than opening a reader), but how applications actually
make use of that freedom specifically, I'm not sure?

(as mentioned on the list), I like the improvements to the javadocs,
 but shouldn't we do the same for getLastCommitUserData(Directory)? (if we keep it)

Woops, I'll fix...

bq. Should we fix the getCurrentXXX methods in for consistency?

Ahh right I will...
> Cleanup DR.getCurrentVersion/DR.getUserData/DR.getIndexCommit().getUserData()
> -----------------------------------------------------------------------------
>                 Key: LUCENE-3760
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: 3.6, 4.0
>         Attachments: LUCENE-3760.patch
> Spinoff from Ryan's dev thread "DR.getCommitUserData() vs DR.getIndexCommit().getUserData()"...
these methods are confusing/dups right now.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message