[
https://issues.apache.org/jira/browse/LUCENE-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986529#action_12986529
]
Simon Willnauer commented on LUCENE-2883:
-----------------------------------------
bq. One issue here is the different purposes for lucene and solr function
queries.
Yonik, if that is your only issue then we are good to go. I don't think that
moving stuff to modules changes anything how we develop software.
Modularization, decoupling, interfaces etc. you know how to work with those ey?
so hey what is really the point here, this modularization is a key point of
merging development with lucene and everytime somebody proposes something like
this you fear that that monolithic thing under /solr could become more modular
and decoupled. I don't know why this is the case but we should and will move on
with modularization. Folks will use it once its there, thats for sure. Same is
true for faceting, replication, queryparsers, functionparser... those are on
the list!
> 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
