[
https://issues.apache.org/jira/browse/LUCENE-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13961017#comment-13961017
]
Robert Muir commented on LUCENE-5569:
-------------------------------------
We should also follow up by completely nuking readercontext,
atomicreadercontext. This indirection hurts and complicates all core lucene
apis, for all use cases, just to support bad practices and esoteric shit, like
climbing up reader tree and using slow wrappers.
Its ok if we are a little less flexible and simplify the API. For example we
could declare readers are instances and have a docbase and parent. Multireaders
and other weird shit could wrap the readers to fix this up.
> Rename AtomicReader to LeafReader
> ---------------------------------
>
> Key: LUCENE-5569
> URL: https://issues.apache.org/jira/browse/LUCENE-5569
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Priority: Minor
> Fix For: 5.0
>
> Attachments: LUCENE-5569.patch
>
>
> See LUCENE-5527 for more context: several of us seem to prefer {{Leaf}} to
> {{Atomic}}.
> Talking from my experience, I was a bit confused in the beginning that this
> thing is named {{AtomicReader}}, since {{Atomic}} is otherwise used in Java
> in the context of concurrency. So maybe renaming it to {{Leaf}} would help
> remove this confusion and also carry the information that these readers are
> used as leaves of top-level readers?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
