[ https://issues.apache.org/jira/browse/LUCENE-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12987146#action_12987146 ]
Yonik Seeley commented on LUCENE-2883: -------------------------------------- One concern some people have had is that lucene not become too tailored just for solr - a very valid point, and I've tried hard not to add anything to lucene that's solr specific or that only solr would benefit from. Nevertheless, there have been a number of occasions (normally on IRC) where there has been disagreement/debate and I've had statements of the form "solr's not the only lucene user you know" type of arguments thrown up. I'm not against modularizing some solr functionality so lucene users can use it, but hopefully you understand why I think it should retain the solr package namespace and be a solr module (or at a minimum perhaps a lucene/solr module). It just wouldn't be fair to downgrade solr support for such a large core piece of solr, and have people cry foul when something is added that only solr can benefit from (as is done fairly regularly today since it's just part of solr). > Consolidate Solr & Lucene FunctionQuery into modules > ----------------------------------------------------- > > Key: LUCENE-2883 > URL: https://issues.apache.org/jira/browse/LUCENE-2883 > Project: Lucene - Java > Issue Type: Task > Components: Search > Affects Versions: 4.0 > Reporter: Simon Willnauer > Fix For: 4.0 > > > Spin-off from the [dev list | > http://www.mail-archive.com/dev@lucene.apache.org/msg13261.html] -- 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org