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
her with SolrCloud.
>>
>> We're experimenting with adding a new shard and start directing all new
>> documents to this new shard. Hopefully that should work.
>>
>> Many Thanks!
>>
>> -Original Message-
>> From: ysee...@gmail.com
ader 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 might be seeing https://issues.apache.org/jira/browse/SOLR-4923 ?
The commit true part of the request th
lto: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 21, 2013 at 6:08 PM, Joshi, Shital wrote:
>> But now Solr stores composite id in the document id
>
> Correct, it
with adding a new shard 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
Su
ite key (it's 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
Subj
On Fri, Jun 21, 2013 at 6:08 PM, Joshi, Shital 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 while storing
compo
Message-
From: Shalin Shekhar Mangar [mailto:shalinman...@gmail.com]
Sent: Monday, June 17, 2013 3:48 PM
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 con
>
>
>
>
> -Original 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.
>
> htt
nstein [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
play/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.
> I
Subject: Re: shardkey
>From my understanding.
In SOLR cloud the CompositeIdDocRouter uses HashbasedDocRouter.
CompositeId router is default if your numShards>1 on collection creation.
CompositeId router generates an hash using the uniqueKey defined in your
schema.xml to route your document
>From my understanding.
In SOLR cloud the CompositeIdDocRouter uses HashbasedDocRouter.
CompositeId router is default if your numShards>1 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 c
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:
http://lucene.472066.n3.nabble.com/shardkey-tp4069940p40699
14 matches
Mail list logo
