[
https://issues.apache.org/jira/browse/LUCENE-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721410#action_12721410
]
Hoss Man commented on LUCENE-1677:
----------------------------------
{quote}
I did ask:
http://www.mail-archive.com/java-u...@lucene.apache.org/msg26726.html
And nobody answered.
So I think we should remove it, and the org.apache.lucene.SegmentReader.class
system property? Can you post a patch? Thanks.
{quote}
FWIW: Google code search pops up a few uses in publicly available code...
http://www.google.co.uk/codesearch?hl=en&lr=&q=org.apache.lucene.SegmentReader.class+-package%3Arepos%2Fasf%2Flucene%2Fjava&sbtn=Search
What jumps out at me is that apparently older versions of Compass relied on
this feature ... it looks like Compass 2.0 eliminated the need for this class,
but i just wanted to point this out.
> Remove GCJ IndexReader specializations
> --------------------------------------
>
> Key: LUCENE-1677
> URL: https://issues.apache.org/jira/browse/LUCENE-1677
> Project: Lucene - Java
> Issue Type: Task
> Reporter: Earwin Burrfoot
> Assignee: Michael McCandless
> Fix For: 2.9
>
>
> These specializations are outdated, unsupported, most probably pointless due
> to the speed of modern JVMs and, I bet, nobody uses them (Mike, you said you
> are going to ask people on java-user, anybody replied that they need it?).
> While giving nothing, they make SegmentReader instantiation code look real
> ugly.
> If nobody objects, I'm going to post a patch that removes these from Lucene.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
