[
https://issues.apache.org/jira/browse/LUCENE-3232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054395#comment-13054395
]
Chris Male commented on LUCENE-3232:
------------------------------------
bq. if we can get FQs factored out soonish
This is the last issue preventing me from doing just that :)
bq. I guess we keep the name "common" for now.
Awesome. I find it fairly common (ha) in projects to have a common module. If
it doesn't pan out, then we can either rename it or slurp it into another
module.
> Move MutableValues to Common Module
> -----------------------------------
>
> Key: LUCENE-3232
> URL: https://issues.apache.org/jira/browse/LUCENE-3232
> Project: Lucene - Java
> Issue Type: Sub-task
> Components: core/search
> Reporter: Chris Male
> Fix For: 4.0
>
> Attachments: LUCENE-3232.patch, LUCENE-3232.patch
>
>
> Solr makes use of the MutableValue* series of classes to improve performance
> of grouping by FunctionQuery (I think). As such they are used in ValueSource
> implementations. Consequently we need to move these classes in order to move
> the ValueSources.
> As Yonik pointed out, these classes have use beyond just FunctionQuerys and
> might be used by both Solr and other modules. However I don't think they
> belong in Lucene core, since they aren't really related to search
> functionality. Therefore I think we should put them into a Common module,
> which can serve as a dependency to Solr and any module.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
