incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rahul Challapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BLUR-120) Add an attribute to the BlurQueryStatus object to set when the status is not found instead of throwing an exception.
Date Mon, 05 Aug 2013 01:06:46 GMT

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

Rahul Challapalli commented on BLUR-120:
----------------------------------------

Hi Aaron,

Thanks for your response. Your comments were really helpful. The controller not sending the
selector to the shard servers is the main missing part for me. I queried the shard server
directly and it looks like we are in-fact fetching the row twice, once while iterating through
the results and then while making future calls in the BlurUtil.convertToHits method. Is there
any reason we are doing this?

- Rahul
                
> Add an attribute to the BlurQueryStatus object to set when the status is not found instead
of throwing an exception.
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: BLUR-120
>                 URL: https://issues.apache.org/jira/browse/BLUR-120
>             Project: Apache Blur
>          Issue Type: Bug
>    Affects Versions: 0.2.0, 0.3.0
>            Reporter: Aaron McCurry
>             Fix For: 0.3.0
>
>


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

Mime
View raw message