Add configuration options to control maximum size of segments
-------------------------------------------------------------
Key: HSEARCH-754
URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-754
Project: Hibernate Search
Issue Type: New Feature
Components: documentation, engine, optimizer
Reporter: Sanne Grinovero
Assignee: Sanne Grinovero
Fix For: 4.0
org.apache.lucene.index.LogByteSizeMergePolicy exposes configuration settings which are currently not selectable in Hibernate Search:
- minMergeSize
- maxMergeSize
- maxMergeSizeForOptimize
being able to limit the size of a segment is very useful to get best performance out of the Infinispan Lucene Directory: performance degrades due to the need for readlocks when the size of a segment is higher than the maximum chunk size in Infinispan.
Readlocks are automatically engaged when needed, so this has no functional impact but is quite noticeable in terms of performance.
--
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
Add tests using Infinispan while scaling the cluster size
---------------------------------------------------------
Key: HSEARCH-738
URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-738
Project: Hibernate Search
Issue Type: Task
Components: tests
Reporter: Sanne Grinovero
Assignee: Sanne Grinovero
Fix For: 3.5
I initially thought we shouldn't need to test Infinispan more, as there are enough tests in the Infinispan project, but after some feedback from people not being able to "see" changes in other nodes I made some extra tests to keep us covered on that.
--
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
Point out that defining an Analyzer is not enough to use it
-----------------------------------------------------------
Key: HSEARCH-748
URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-748
Project: Hibernate Search
Issue Type: Improvement
Components: documentation
Reporter: Sanne Grinovero
Assignee: Sanne Grinovero
Priority: Minor
Fix For: 4.0
It seems we need to clarify that @AnalyzerDef is not enough to apply an analyzer to an entity (docs change only)
--
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