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

Hoss Man updated SOLR-2978:
---------------------------

    Fix Version/s:     (was: 4.0)

There is no indication that anyone is actively working on this issue, and it 
has no current patch, so removing 4.0 from the fixVersion.
                
> Language variable expansion in field names for search results clustering
> ------------------------------------------------------------------------
>
>                 Key: SOLR-2978
>                 URL: https://issues.apache.org/jira/browse/SOLR-2978
>             Project: Solr
>          Issue Type: Improvement
>          Components: contrib - Clustering
>            Reporter: Stanislaw Osinski
>            Assignee: Stanislaw Osinski
>            Priority: Minor
>
> This is a follow-up of SOLR-2939. 
> {quote}
> Another feature of language recognizer we should mirror is the expansion of 
> the {{lang}} token in field names into the language code of the document (in 
> case of multiple languages per document - the first Carrot2-supported 
> language code). The feature seems easy to implement in the non-distributed 
> setting of Solr, but the simple implementation isn't going to work in the 
> distributed setting because the name of the specific field to be fetched 
> depends on the content (language) of each matching document. Looking at the 
> SearchClusteringEngine.getFieldsToLoad(SolrQueryRequest) method, a quick but 
> costly solution would be to load the contents of all stored fields. I'm not 
> too strong in distributed-mode Solr, but maybe this could be optimized so 
> that only the required fields get fetched?
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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