[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-176) explicitly setting cfg property to lucene default
Emmanuel Bernard (JIRA)
noreply at atlassian.com
Thu Apr 10 15:35:33 EDT 2008
[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_29981 ]
Emmanuel Bernard commented on HSEARCH-176:
------------------------------------------
Applied. Need some fixes before closing.
> 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
More information about the hibernate-issues
mailing list