As per my understanding, distrib=false will be added in select query to
restrict the document selection to particular shard. But how should i route
the documents to only particular shard, is still my need.
Thanks
Hemanth
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
I suspect that when you create your collections, somehow you're not
doing it like you expect.
The red flag is:
I tried creating a collection with compositeId routing which
created shard1,shard2,shard3 , but when I indexed , all the documents went
to one shard only
This simply shouldn't be happen
Hi Erik,
Thanks for your reply. I have no issues of using either Implicit or
Composite routing but I want to insert the documents to a particular shard,
so that when I want to query the data , I can hit a particular shard, which
gives me the results in lesser time as it hits only particular shard.
You're misinterpreting the docs. _route_ is used to
tell _queries_ where to go, or to route a document
as part of the parameters when you send the doc,
not a field in the doc.
So when you added the _route_ field to the doc, you
didn't have it in the schema in the first place.
So you could add a _
I created a collection with implicit routing mechanism and my shared names
are Active and Disabled , these are the values of one of my collection
field: Status. But when I am trying to upload the document using Solr UI
documents section : Upload using JSON format with all the fields including
fiel
gt; necessary) and indexing id:shard1 id:shard2 id:shard3 takes all documents to
> the same (random) shard.
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/indexing-data-to-solrcloud-with-implicit-is-not-distributing-across-cluster-tp4232956p4282428.html
> Sent from the Solr - User mailing list archive at Nabble.com.
;id" field as the router.field (not sure if
necessary) and indexing id:shard1 id:shard2 id:shard3 takes all documents to
the same (random) shard.
--
View this message in context:
http://lucene.472066.n3.nabble.com/indexing-data-to-solrcloud-with-implicit-is-not-distributing-across-cluster-t
: The documentation int the Collections API says "The value can be ...
: *implicit*, which uses an internal default hash".
: I think most people would assume the "hash" would be used to route the
: data.
: Meanwhile the description of CompositID in the "Document Routing" section
: only discusses
On 10/6/2015 10:02 AM, Steve wrote:
> Thanks Shawn, that fixed it !
>
> The documentation int the Collections API says "The value can be ...
> *implicit*, which uses an internal default hash".
Thank you for pointing out this error in the documentation. I did not
know it was there. I have update
Thanks Shawn, that fixed it !
The documentation int the Collections API says "The value can be ...
*implicit*, which uses an internal default hash".
I think most people would assume the "hash" would be used to route the
data.
Meanwhile the description of CompositID in the "Document Routing" secti
On 10/6/2015 7:58 AM, Steve wrote:
> I’ve been unable to get solrcloud to distribute data across 4 solr nodes
> with the “route.name=implicit” feature of the collections API.
>
> The nodes are live, and the graphs are green. All the data (the “Films”
> example data) shows up on one node, the nod
I’ve been unable to get solrcloud to distribute data across 4 solr nodes
with the “route.name=implicit” feature of the collections API.
The nodes are live, and the graphs are green. All the data (the “Films”
example data) shows up on one node, the node that received the CREATE
command.
My C
12 matches
Mail list logo
