[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-472?pag...
]
Sanne Grinovero commented on HSEARCH-472:
-----------------------------------------
true, clustering would be problematic - a notification to clients must be send about the
full list of available shards; I'd implement it with Infinispan, providing a shared
cache containing {shard-business-key, DP configuration} but wouldn't like to introduce
Infinispan at this level.
The use case would be when sharding by a business key, for example city name for
addresses, and a new city name is inserted in the database while previously unknown: a new
shard should be started.
Sharding by business key is quite cool as it can enable usage of HSEARCH-251
Runtime creation of new shards
------------------------------
Key: HSEARCH-472
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-472
Project: Hibernate Search
Issue Type: New Feature
Components: query
Affects Versions: 3.2.0.Beta1
Reporter: Dobes Vandermeer
Assignee: Emmanuel Bernard
Priority: Minor
Fix For: 3.3.0.Beta3
Hibernate Search's shard support has added the ability to select a shard based on a
parameter of the query; however, you must use a fixed number of shards. In order to best
support our use case originally reported in
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-470 it would be
necessary to add support for dynamically added shards at runtime.
Also related:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-251 and
http://www.opensubscriber.com/message/hibernate-dev@lists.jboss.org/97703...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira