]
Sent: Thursday, June 27, 2013 5:35 PM
To: solr-user@lucene.apache.org
Subject: Re: shardkey
You might be seeing https://issues.apache.org/jira/browse/SOLR-4923 ?
The commit true part of the request that add documents? If so, it might be
SOLR-4923 and you should try the commit in a request after
:8983/solr/core3/update?commit=true; Is that
correct?
It doesn't matter whether HOST is leader or replica.
-Original Message-
From: Mark Miller [mailto:markrmil...@gmail.com]
Sent: Thursday, June 27, 2013 5:35 PM
To: solr-user@lucene.apache.org
Subject: Re: shardkey
You
Thanks!
-Original Message-
From: Mark Miller [mailto:markrmil...@gmail.com]
Sent: Friday, June 28, 2013 5:06 PM
To: solr-user@lucene.apache.org
Subject: Re: shardkey
Yeah, that is what I would try until 4.4 comes out - and it should not matter
replica or leader.
- Mark
On Jun 28
and start directing all new
documents to this new shard. Hopefully that should work.
Many Thanks!
-Original Message-
From: ysee...@gmail.com [mailto:ysee...@gmail.com] On Behalf Of Yonik Seeley
Sent: Friday, June 21, 2013 8:50 PM
To: solr-user@lucene.apache.org
Subject: Re: shardkey
@lucene.apache.org
Subject: Re: shardkey
On Fri, Jun 21, 2013 at 6:08 PM, Joshi, Shital shital.jo...@gs.com wrote:
But now Solr stores composite id in the document id
Correct, it's the document id itself that contains everything needed
for tje compositeId router to determine the hash.
It would only use
a String,
without timestamp) and per business date we're expecting about 3 million
documents.
-Original Message-
From: ysee...@gmail.com [mailto:ysee...@gmail.com] On Behalf Of Yonik Seeley
Sent: Friday, June 21, 2013 8:50 PM
To: solr-user@lucene.apache.org
Subject: Re: shardkey
On Fri, Jun
To: solr-user@lucene.apache.org
Subject: Re: shardkey
No, there is no way to do that right now. I think you'd be better off using
custom sharding because you can't really control that two shardKeys must go
to two different shards. We can only guarantee that docs with the same
shardKey will goto
On Fri, Jun 21, 2013 at 6:08 PM, Joshi, Shital shital.jo...@gs.com wrote:
But now Solr stores composite id in the document id
Correct, it's the document id itself that contains everything needed
for tje compositeId router to determine the hash.
It would only use it to calculate hash key but
[mailto:joels...@gmail.com]
Sent: Thursday, June 13, 2013 2:38 PM
To: solr-user@lucene.apache.org
Subject: Re: shardkey
Also you might want to check this blog post, just went up today.
http://searchhub.org/2013/06/13/solr-cloud-document-routing/
On Wed, Jun 12, 2013 at 2:18 PM, James Thomas jtho
Message-
From: Joel Bernstein [mailto:joels...@gmail.com]
Sent: Thursday, June 13, 2013 2:38 PM
To: solr-user@lucene.apache.org
Subject: Re: shardkey
Also you might want to check this blog post, just went up today.
http://searchhub.org/2013/06/13/solr-cloud-document-routing/
On Wed
/display/solr/Shards+and+Indexing+Data+in+SolrCloud
-Original Message-
From: Rishi Easwaran [mailto:rishi.easwa...@aol.com]
Sent: Wednesday, June 12, 2013 1:40 PM
To: solr-user@lucene.apache.org
Subject: Re: shardkey
From my understanding.
In SOLR cloud the CompositeIdDocRouter uses
I suppose you can implement custom hashing by using _shard_ field. I am not
sure on this, but I have come across this approach sometime back..
At query time, you can specify shard.keys parameter...
--
View this message in context:
From my understanding.
In SOLR cloud the CompositeIdDocRouter uses HashbasedDocRouter.
CompositeId router is default if your numShards1 on collection creation.
CompositeId router generates an hash using the uniqueKey defined in your
schema.xml to route your documents to a dedicated shard.
You
Subject: Re: shardkey
From my understanding.
In SOLR cloud the CompositeIdDocRouter uses HashbasedDocRouter.
CompositeId router is default if your numShards1 on collection creation.
CompositeId router generates an hash using the uniqueKey defined in your
schema.xml to route your documents
14 matches
Mail list logo
