I suppose that /get is the query by id API. I wonder if its reasonable to
expect it to be smart in SolrCloud usage.
On Thursday, January 14, 2016, Doug Turnbull <
dturnb...@opensourceconnections.com> wrote:
> Stupid thought/question. Is there a query by id API that understands
> SolrCloud
On 1/14/2016 5:20 PM, Shivaji Dutta wrote:
> I am working with a customer that has about a billion documents on 20 shards.
> The documents are extremely small about 100 characters each.
> The insert rate is pretty good, but they are trying to fetch the document by
> using SolrJ SolrQuery
>
>
Stupid thought/question. Is there a query by id API that understands
SolrCloud routing and can simply fwd the query to the shard that would hold
said document? Barring that, can one use SolrJ's routing brains to see what
shard a given id would be routed to and only query that shard?
-Doug
On
Sounds intriguing. It would have to know for sure which query parser is
being used, which might be set in the server side defaults.
Over in Cassandra NoSQL database land we have the concept of "token aware
load balancing policy" on the client side that does the necessary magic
(requiring parsing
Team
Thanks for all the help before.
Current State
I am working with a customer that has about a billion documents on 20 shards.
The documents are extremely small about 100 characters each.
The insert rate is pretty good, but they are trying to fetch the document by
using SolrJ SolrQuery
Add =all to your query to see where the time is spent in the "timing"
section to see which Solr search component is consuming the time.
You may also have to add =track to get the shard-specific info.
In theory, 19 of the shards should return nothing and the 20th will return
a single document.
