[hibernate-issues] [Hibernate-JIRA] Updated: (HSEARCH-176) explicitly setting cfg property to lucene default

[Sanne Grinovero (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sanne Grinovero updated HSEARCH-176:
------------------------------------

    Attachment: HSearch-values-settable-to-default.patch

This patch contains support for "default" keyword for indexing-finetuning parameters
and relevant documentation updates and tests.

I had thought it would be trivial, instead I've hit some problems:

I've been hit by some bugs about the sharding-configuration as it forgets to bring along some values;
also it would detect the wrong number of shards in many scenarios, so for
this "trivial" patch some changes to how DirectoryProviderFactory parses the configuration were needed.

I'm quite confident I've tested all sort of weird shard configuration setup, still I could use some help in testing that part, as I don't know all use cases.

> explicitly setting cfg property to lucene default
> -------------------------------------------------
>
>                 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
>            Priority: Trivial
>         Attachments: 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: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira