[
https://issues.apache.org/jira/browse/BLUR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687492#comment-13687492
]
Aaron McCurry commented on BLUR-139:
------------------------------------
Jeff
I know some discussion has happened around this issue. Do you think this is
still needed?
Aaron
> Make querying by rowid less taxing on shard servers
> ---------------------------------------------------
>
> Key: BLUR-139
> URL: https://issues.apache.org/jira/browse/BLUR-139
> Project: Apache Blur
> Issue Type: Improvement
> Components: Blur
> Affects Versions: 0.2.0, 0.3.0
> Reporter: Jeff Borst
> Fix For: 0.2.0, 0.3.0
>
>
> Please add a mechanism that makes querying by rowid less taxing on the shard
> servers. Rowid is not something that I want to put in block cache, but it is
> a field that is convenient to use in queries.
> Currently in queries, rowid acts like any other field, so all shard servers
> that do not have the rowid in question have to parse the query and run the
> search even though they are guaranteed to not produce any results.
> It would be nice if this behavior could be short circuited when rowid is a
> required query element and is a full string (doesn't include wildcards or
> ranges of any sort).
--
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
