[jira] [Commented] (SOLR-5338) Split shards by a route key

2013-10-16 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13797117#comment-13797117
 ] 

ASF subversion and git services commented on SOLR-5338:
---

Commit 1532862 from sha...@apache.org in branch 'dev/branches/branch_4x'
[ https://svn.apache.org/r1532862 ]

SOLR-5338: Split shards by a route key using split.key parameter

 Split shards by a route key
 ---

 Key: SOLR-5338
 URL: https://issues.apache.org/jira/browse/SOLR-5338
 Project: Solr
  Issue Type: Improvement
  Components: SolrCloud
Reporter: Shalin Shekhar Mangar
Assignee: Shalin Shekhar Mangar
 Fix For: 4.6, 5.0

 Attachments: SOLR-5338.patch, SOLR-5338.patch, SOLR-5338.patch


 Provide a way to split a shard using a route key such that all documents of 
 the specified route key end up in a single dedicated sub-shard.
 Example:
 Assume that collection1, shard1 has hash range [0, 20]. Also that route key 
 'A!' has hash range [12,15]. Then invoking:
 {code}
 /admin/collections?action=SPLITcollection=collection1split.key=A!
 {code}
 should produce three sub-shards with hash range [0,11], [12,15] and [16,20].
 Specifying the source shard is not required here because the route key is 
 enough to figure it out. Route keys spanning more than one shards will not be 
 supported.
 Note that the sub-shard with the hash range of the route key may also contain 
 documents for other route keys whose hash ranges overlap.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (SOLR-5338) Split shards by a route key

2013-10-16 Thread Yonik Seeley (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13797127#comment-13797127
 ] 

Yonik Seeley commented on SOLR-5338:


bq. Would you mind reviewing the new CompositeIdRouter methods?

Yeah, these make sense.  You could optionally not throw this error:
+  throw new IllegalArgumentException(Route key must be a composite id);

and just return a range that covers the single hash code of the ID.

 Split shards by a route key
 ---

 Key: SOLR-5338
 URL: https://issues.apache.org/jira/browse/SOLR-5338
 Project: Solr
  Issue Type: Improvement
  Components: SolrCloud
Reporter: Shalin Shekhar Mangar
Assignee: Shalin Shekhar Mangar
 Fix For: 4.6, 5.0

 Attachments: SOLR-5338.patch, SOLR-5338.patch, SOLR-5338.patch


 Provide a way to split a shard using a route key such that all documents of 
 the specified route key end up in a single dedicated sub-shard.
 Example:
 Assume that collection1, shard1 has hash range [0, 20]. Also that route key 
 'A!' has hash range [12,15]. Then invoking:
 {code}
 /admin/collections?action=SPLITcollection=collection1split.key=A!
 {code}
 should produce three sub-shards with hash range [0,11], [12,15] and [16,20].
 Specifying the source shard is not required here because the route key is 
 enough to figure it out. Route keys spanning more than one shards will not be 
 supported.
 Note that the sub-shard with the hash range of the route key may also contain 
 documents for other route keys whose hash ranges overlap.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (SOLR-5338) Split shards by a route key

2013-10-16 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13797154#comment-13797154
 ] 

ASF subversion and git services commented on SOLR-5338:
---

Commit 1532868 from sha...@apache.org in branch 'dev/branches/branch_4x'
[ https://svn.apache.org/r1532868 ]

SOLR-5338: CompositeIdRouter.keyHashRange should not throw exception if route 
key is not composite

 Split shards by a route key
 ---

 Key: SOLR-5338
 URL: https://issues.apache.org/jira/browse/SOLR-5338
 Project: Solr
  Issue Type: Improvement
  Components: SolrCloud
Reporter: Shalin Shekhar Mangar
Assignee: Shalin Shekhar Mangar
 Fix For: 4.6, 5.0

 Attachments: SOLR-5338.patch, SOLR-5338.patch, SOLR-5338.patch, 
 SOLR-5338-remove-exception.patch


 Provide a way to split a shard using a route key such that all documents of 
 the specified route key end up in a single dedicated sub-shard.
 Example:
 Assume that collection1, shard1 has hash range [0, 20]. Also that route key 
 'A!' has hash range [12,15]. Then invoking:
 {code}
 /admin/collections?action=SPLITcollection=collection1split.key=A!
 {code}
 should produce three sub-shards with hash range [0,11], [12,15] and [16,20].
 Specifying the source shard is not required here because the route key is 
 enough to figure it out. Route keys spanning more than one shards will not be 
 supported.
 Note that the sub-shard with the hash range of the route key may also contain 
 documents for other route keys whose hash ranges overlap.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (SOLR-5338) Split shards by a route key

2013-10-16 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13797151#comment-13797151
 ] 

ASF subversion and git services commented on SOLR-5338:
---

Commit 1532867 from sha...@apache.org in branch 'dev/trunk'
[ https://svn.apache.org/r1532867 ]

SOLR-5338: CompositeIdRouter.keyHashRange should not throw exception if route 
key is not composite

 Split shards by a route key
 ---

 Key: SOLR-5338
 URL: https://issues.apache.org/jira/browse/SOLR-5338
 Project: Solr
  Issue Type: Improvement
  Components: SolrCloud
Reporter: Shalin Shekhar Mangar
Assignee: Shalin Shekhar Mangar
 Fix For: 4.6, 5.0

 Attachments: SOLR-5338.patch, SOLR-5338.patch, SOLR-5338.patch, 
 SOLR-5338-remove-exception.patch


 Provide a way to split a shard using a route key such that all documents of 
 the specified route key end up in a single dedicated sub-shard.
 Example:
 Assume that collection1, shard1 has hash range [0, 20]. Also that route key 
 'A!' has hash range [12,15]. Then invoking:
 {code}
 /admin/collections?action=SPLITcollection=collection1split.key=A!
 {code}
 should produce three sub-shards with hash range [0,11], [12,15] and [16,20].
 Specifying the source shard is not required here because the route key is 
 enough to figure it out. Route keys spanning more than one shards will not be 
 supported.
 Note that the sub-shard with the hash range of the route key may also contain 
 documents for other route keys whose hash ranges overlap.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (SOLR-5338) Split shards by a route key

2013-10-11 Thread Shalin Shekhar Mangar (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13792600#comment-13792600
 ] 

Shalin Shekhar Mangar commented on SOLR-5338:
-

[~ysee...@gmail.com] - Would you mind reviewing the new CompositeIdRouter 
methods?

 Split shards by a route key
 ---

 Key: SOLR-5338
 URL: https://issues.apache.org/jira/browse/SOLR-5338
 Project: Solr
  Issue Type: Improvement
  Components: SolrCloud
Reporter: Shalin Shekhar Mangar
Assignee: Shalin Shekhar Mangar
 Fix For: 4.6, 5.0

 Attachments: SOLR-5338.patch


 Provide a way to split a shard using a route key such that all documents of 
 the specified route key end up in a single dedicated sub-shard.
 Example:
 Assume that collection1, shard1 has hash range [0, 20]. Also that route key 
 'A!' has hash range [12,15]. Then invoking:
 {code}
 /admin/collections?action=SPLITcollection=collection1split.key=A!
 {code}
 should produce three sub-shards with hash range [0,11], [12,15] and [16,20].
 Specifying the source shard is not required here because the route key is 
 enough to figure it out. Route keys spanning more than one shards will not be 
 supported.
 Note that the sub-shard with the hash range of the route key may also contain 
 documents for other route keys whose hashes collide.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org