[
https://issues.apache.org/jira/browse/LUCENE-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223276#comment-13223276
]
Benson Margulies commented on LUCENE-3853:
------------------------------------------
So, the explanation below what I patchd that I failed to read the first time
sort-of endorses Multi-Field.
I happen to be updating code of someone else's that want to walk all of the
fields, which is how I ran into this.
One possibility is to change the comment I added to say 'this is not the
recommended way, read below for more information on this' and then focus effort
on howto and examples instead of MIGRATION/CHANGE, rather than making the
little Migratin example bigger and bigger?
Where in the tree do you generally put examples?
> Improve MIGRATE.txt for FieldsEnum/TermsEnum
> --------------------------------------------
>
> Key: LUCENE-3853
> URL: https://issues.apache.org/jira/browse/LUCENE-3853
> Project: Lucene - Java
> Issue Type: Bug
> Components: core/other
> Affects Versions: 4.0
> Reporter: Benson Margulies
> Attachments: LUCENE-3853.patch
>
>
> The text in MIGRATE.txt that explains the new situation with FieldsEnum seems
> to be missing a level of object in explaining TermEnum. Perhaps it didn't
> keep with the code. here's a patch to MIGRATE.txt.
--
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
