[
https://issues.apache.org/jira/browse/BLUR-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728720#comment-13728720
]
Aaron McCurry commented on BLUR-120:
------------------------------------
-I am not getting an exception even if my search resulted in 0 results. How can
I generate the exception?
I believe the exception occurs when you send in a bad query uuid into
queryStatusById(table, uuid). Basically this can happen when the status is
cleared after 60 seconds and an external client requests the status for the
uuid.
-When we perform a search, we first get all the documents/records which contain
the search term(Actual Search) and then we get the Row(if a selector is
specified) which contains that document. It appears as though we are fetching
the Row multiple times. In the BlurUtil.convertToHits method we iterate over
the "hitsIterable" which eventually calls the fetchRow method in IndexManager.
In the same BlurUtil.convertToHits method a few lines below we are making
future calls to iface.fetchRow. Can you clarify what I am missing here?
I will have to review the code and follow up with you. But I don't think that
we fetch the row multiples time, but I definitely could be wrong.
-Also are ResolveId, LocationId same as the Document Path on a shard server?
Where is resolvedId mentioned? But locationId is <shard id>/<lucene document
id>.
> 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
