[
https://issues.apache.org/jira/browse/BLUR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron McCurry closed BLUR-139.
------------------------------
Resolution: Fixed
Fix Version/s: 0.2.2
This was resolved in the last release.
> 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
> Priority: Minor
> Fix For: 0.2.2, 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 was sent by Atlassian JIRA
(v6.2#6252)
