]
Sanne Grinovero reassigned HSEARCH-176:
---------------------------------------
Assignee: Sanne Grinovero
Permits alignment properties to lucene default (Sanne Grinovero)
----------------------------------------------------------------
Key: HSEARCH-176
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-176
Project: Hibernate Search
Issue Type: Improvement
Components: directory provider, documentation
Reporter: Sanne Grinovero
Assignee: Sanne Grinovero
Priority: Trivial
Fix For: 3.1.0.Beta1
Attachments: HSEARCH-176-secondFix.patch,
HSearch-values-settable-to-default.patch
As highlighted by previous patch for
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-153 ,
some configuration settings may be inherited, so it becomes difficult to explicitly set
"default" settings on some settings as some values are
"Integer.MAX_VALUE" or "null" but
the cfg parser only accepts int values.
Also if the users wants to explicitly set lucene defaults it needs to study the current
lucene
source code.
I'm going to provide a patch to support besides current int values also
"default" and "null"
Strings, to explicitly configure H.Search to:
"default" -> don't mess with the value
"null" -> explicitly null the value
Also someone may find it useful to represent "MAX_VALUE", what do you think
about that,
or other configurations that should be recognized?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: