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
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?