[
https://issues.apache.org/jira/browse/LUCENE-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204082#comment-13204082
]
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?
{quote}
(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)
{quote}
Woops, I'll fix...
bq. Should we fix the getCurrentXXX methods in SegmentInfos.java for
consistency?
Ahh right I will...
> Cleanup DR.getCurrentVersion/DR.getUserData/DR.getIndexCommit().getUserData()
> -----------------------------------------------------------------------------
>
> Key: LUCENE-3760
> URL: https://issues.apache.org/jira/browse/LUCENE-3760
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
