[ 
https://issues.apache.org/jira/browse/LUCENE-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Male updated LUCENE-2883:
-------------------------------

    Attachment: LUCENE-2883.patch

Patch that factors out the core FunctionQuery stuff into a queries module.  
Theres alot of issues here but it does compile.  

The following issues need to be addressed:

- MutableValue & MutableFloatValue are used in the FunctionQuery code so I've 
pulled them into the module too.  Should all the other Mutable*Value classes 
come too? Should they go into some other module?

- What to return in ValueSource#getSortField which currently returns a 
SortField which implements SolrSortField.  This is currently commented out so 
we can determine what best to do.  Having this commented out breaks the Solr 
tests.

- Many of the ValueSources and DocValues in Solr could be moved to the module, 
but not all of them.  Some have dependencies on Solr dependencies / Solr core 
code.

- Module isn't full integrated into the build.xmls and dev-tools.

- Lucene core's FunctionQuery stuff needs to be removed.

I'll add a script that needs to be run before adding this patch shortly.

> 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: core/search
>    Affects Versions: 4.0
>            Reporter: Simon Willnauer
>              Labels: gsoc2011, lucene-gsoc-11, mentor
>             Fix For: 4.0
>
>         Attachments: LUCENE-2883.patch
>
>
> Spin-off from the [dev list | 
> http://www.mail-archive.com/[email protected]/msg13261.html]  

--
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]

Reply via email to