[
https://issues.apache.org/jira/browse/LUCENE-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208567#comment-13208567
]
Shai Erera commented on LUCENE-3760:
------------------------------------
Yes, I know that I can write it. But it means I'll need to write it in every
project that I work on. And so will other people. I really don't get it --
what's the problem with having such utility method. If we move it to a
DirectoryUtils, will that be better? If we move it to DirectoryReader (on
trunk) will that be better?
I don't understand since when we decided to drop API that our users need,
because some people "don't understand the scenario". Is there a technical
reason to remove the method? Is it badly implemented? Is it buggy? Is it hard
to maintain?
> 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, 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
