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-193) When searching directly on a shard server, the current code is fetching the row twice. We should only be fetching it once.
Date Tue, 29 Oct 2013 06:04:32 GMT

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

Rahul Challapalli commented on BLUR-193:
----------------------------------------

Hi Vikrant,

I believe we have not resolved the issue. I could not find the relevant discussion that happened
on the email list. (might be present in the comments of another issue).
If I remember it correctly, this has nothing to do with the row count, but it has to do with
whether a row is un-necessarily fetched twice or not? We validated that it was only fetching
the row once. However when any client (Java program) directly interacts with the shard server,
by-passing the controller, we are infact fetching it twice. 

I might be completely wrong here, but track through the BlurControllerServer.query() method
and see what happens when blurQuery.selector is null. It might actually be fetching it twice.

- Rahul

> When searching directly on a shard server, the current code is fetching the row twice.
We should only be fetching it once.
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: BLUR-193
>                 URL: https://issues.apache.org/jira/browse/BLUR-193
>             Project: Apache Blur
>          Issue Type: Improvement
>          Components: Blur
>    Affects Versions: 0.2.0, 0.3.0
>            Reporter: Rahul Challapalli
>            Priority: Minor
>             Fix For: 0.3.0
>
>




--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message