Search default properties are ignored when at least one shard property exist
----------------------------------------------------------------------------
Key: HIBERNATE-103
URL:
https://jira.jboss.org/jira/browse/HIBERNATE-103
Project: Hibernate
Issue Type: Bug
Reporter: Rafal Glowacz
Assignee: Steve Ebersole
I'm trying to use shared strategy for search. So my basic setup was:
common.hibernate.search.default.indexBase = /lucene/index
common.hibernate.search.default.optimizer.operation_limit.max = 1000
common.hibernate.search.default.optimizer.transaction_limit.max = 1000
common.hibernate.search.default.directory_provider =
org.hibernate.search.store.FSDirectoryProvider
common.hibernate.search.default.sharding_strategy =
com.newbay.search.sharding.strategy.IdShardingStrategy
common.hibernate.search.blogentry.sharding_strategy.nbr_of_shards = 5
But this won't work for me because when sharding configuration properties exist then
those default ones are completely ignored - I can't understand that. To change this I
changed ".default." to ".blogentry." and then I found the bug that the
number of properties decides how many shards I want for current index. (nbrOfShards =
nbrOfShards >= indexSpecificDefaultProps.size() ?
nbrOfShards :
indexSpecificDefaultProps.size();)
So in this case I can't do anything. I'm looking for such config:
common.hibernate.search.default.indexBase = /lucene/index
common.hibernate.search.default.optimizer.operation_limit.max = 1000
common.hibernate.search.default.optimizer.transaction_limit.max = 1000
common.hibernate.search.default.directory_provider =
org.hibernate.search.store.FSDirectoryProvider
common.hibernate.search.default.sharding_strategy =
com.newbay.search.sharding.strategy.IdShardingStrategy
common.hibernate.search.website.sharding_strategy.nbr_of_shards = 2
common.hibernate.search.website.indexBase = /lucene/website
common.hibernate.search.blogentry.sharding_strategy.nbr_of_shards = 5
common.hibernate.search.blogentry.indexBase = /lucene/blogentry
But it doesn't work for now.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira