[ 
https://issues.apache.org/jira/browse/SOLR-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058606#comment-15058606
 ] 

Hoss Man commented on SOLR-3229:
--------------------------------

I don't remember this issue at all, and w/o digging into it's history or 
looking at teh commits, i'm going to reply simply to this sentence...

bq. UniqueKey should be required for distributed-search to get TV info back. 

I have no objection to this.  if that's not how it works now, then i'm 
surprised and If i'm responsible for the code/decision in question then my 
suspicion is that it's simply because this issue predated SolrCloud and most of 
the other current "rules" regarding "distributed search" -- back when it was a 
query time only concept and people manually partitioned their shards.  it 
certainly pre-dates distrib.singlePass.

open/link a new jira w/whatever changes you think make sense to the existing 
functionality.

> TermVectorComponent does not return terms in distributed search
> ---------------------------------------------------------------
>
>                 Key: SOLR-3229
>                 URL: https://issues.apache.org/jira/browse/SOLR-3229
>             Project: Solr
>          Issue Type: Bug
>          Components: SearchComponents - other
>    Affects Versions: 4.0-ALPHA
>         Environment: Ubuntu 11.10, openjdk-6
>            Reporter: Hang Xie
>            Assignee: Hoss Man
>              Labels: patch
>             Fix For: 4.0, Trunk
>
>         Attachments: SOLR-3229.patch, TermVectorComponent.patch
>
>
> TermVectorComponent does not return terms in distributed search, the 
> distributedProcess() incorrectly uses Solr Unique Key to do subrequests, 
> while process() expects Lucene document ids. Also, parameters are transferred 
> in different format thus making distributed search returns no result.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to