lucene-solr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Solr Wiki] Trivial Update of "ReleaseNote41" by YonikSeeley
Date Sat, 19 Jan 2013 14:31:40 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.

The "ReleaseNote41" page has been changed by YonikSeeley:
http://wiki.apache.org/solr/ReleaseNote41?action=diff&rev1=11&rev2=12

  Solr 4.1 Release Highlights:
  
  SolrCloud enhancements (see http://wiki.apache.org/solr/SolrCloud):
- * Collection specific document routing:
+ * Simple multi-tenancy through enhanced 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, e.g.
      'customerB!', will be routed to the same shard, allowing for
      efficient querying.  At query time, one can specify a "shard.keys"
-     parameter that lists what shards the query should cover.
+     parameter that lists the domains, e.g. 'shard.keys=customerB!', and
+     controls what shards the query is routed to.
    - 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.
+ * Short circuiting for distributed search if a request only needs
+   to query a single shard.
  * Allow creating more than one shard per instance with the Collection
    API.
  * Allow access to the collections API through CloudSolrServer without
@@ -53, +56 @@

  * Indexed term offsets, specifiable via a 'storeOffsetsWithPositions'
    flag on field definitions in the schema.  Useful for highlighters.
  * Solr QParsers may now be directly invoked in the lucene query syntax
-   without the _query_ magic field hack.
+   via localParams and without the _query_ magic field hack.
    Example: foo AND {!term f=myfield v=$qq}
  * Solr now parses request parameters (from URL or sent with POST using
    content-type application/x-www-form-urlencoded) in its dispatcher code.

Mime
View raw message