incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron McCurry (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (BLUR-101) Create sessions in the shard servers to store indexreader between calls
Date Thu, 23 May 2013 11:26:20 GMT

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

Aaron McCurry closed BLUR-101.
------------------------------

    Resolution: Fixed

I committed this a couple of days ago but forgot to create a jira ticket for the issue.  Sorry.
                
> Create sessions in the shard servers to store indexreader between calls
> -----------------------------------------------------------------------
>
>                 Key: BLUR-101
>                 URL: https://issues.apache.org/jira/browse/BLUR-101
>             Project: Apache Blur
>          Issue Type: Sub-task
>    Affects Versions: 0.1.5
>            Reporter: Aaron McCurry
>             Fix For: 0.1.5
>
>
> Make use of the TServerEventHandler in Thrift that can give you sessions tied to Thrift
connections.  In the every call to Thrift always reset the IndexReaders in the session except
for when a query is followed by a fetch with locationIds happens.  That's when the controller
issues a query then after it has the top answers from all the shards in the table are calculated,
it fetches the data.
> The reason we need to do this is because in between those 2 calls the indexreader could
have been refreshed from the writer, and thus the lucene doc ids could changed.  This could
cause the fetch to fetch the wrong data back to the controller.

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