svn commit: r1433082 - /lucene/dev/trunk/solr/CHANGES.txt

[yo...@apache.org]

Author: yonik
Date: Mon Jan 14 20:01:29 2013
New Revision: 1433082

URL: http://svn.apache.org/viewvc?rev=1433082&view=rev
Log:
SOLR-2592: changes entry for doc routing

Modified:
    lucene/dev/trunk/solr/CHANGES.txt

Modified: lucene/dev/trunk/solr/CHANGES.txt
URL: http://svn.apache.org/viewvc/lucene/dev/trunk/solr/CHANGES.txt?rev=1433082&r1=1433081&r2=1433082&view=diff
==============================================================================
--- lucene/dev/trunk/solr/CHANGES.txt (original)
+++ lucene/dev/trunk/solr/CHANGES.txt Mon Jan 14 20:01:29 2013
@@ -210,6 +210,26 @@ New Features
 * SOLR-4302: New parameter 'indexInfo' (defaults to true) in CoreAdmin STATUS
   command can be used to omit index specific information (Shahar Davidson via shalin)
 
+* SOLR-2592: Collection specific document routing.  The "compositeId"
+  router is the default for collections with hash based routing (i.e. when
+  numShards=N is specified on collection creation).  Documents with ids sharing
+  the same domain (prefix) will be routed to the same shard, allowing for
+  efficient querying.
+  Example: 
+    The following two documents will be indexed to the same shard
+    since they share the same domain "customerB!". 
+       {"id" : "customerB!doc1" [...] }
+       {"id" : "customerB!doc2" [...] }
+    At query time, one can specify a "shard.keys" parameter that lists what
+    shards the query should cover.
+       http://.../query?q=my_query&shard.keys=customerB! 
+  Collections that do not specify numShards at collection creation time
+  use custom sharding and default to the "implicit" router.  Document updates
+  received by a shard will be indexed to that shard, unless a "_shard_" parameter
+  or document field names a different shard.
+  (Michael Garski, Dan Rosher, yonik)
+
+
 Optimizations
 ----------------------