[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-200) Expose IndexWriter setting MAX_FIELD_LENGTH via IndexWriterSetting

[Sanne Grinovero (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_30247 ] 

Sanne Grinovero commented on HSEARCH-200:
-----------------------------------------

for the sake of logs:
Emmanuel had some minutes on MSN to express this opinion:
* group all properties under a ".indexwriter" (e.g.) keyword, if possible being backwards compatible
* supporting the "default value" property has priority on backwards compatibility (if conflicting)
[I hope I understood it well]

He didn't express a strong direction about if we should permit different values for MAX_FIELD_LENGTH
in transaction or batch; I think I'll put a WARN both in logs and in documentation;
I don't really like the exception, someone could have a good reason to do it?

> Expose IndexWriter setting MAX_FIELD_LENGTH via IndexWriterSetting
> ------------------------------------------------------------------
>
>                 Key: HSEARCH-200
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-200
>             Project: Hibernate Search
>          Issue Type: New Feature
>          Components: engine
>    Affects Versions: 3.0.1.GA
>            Reporter: Hardy Ferentschik
>            Assignee: Sanne Grinovero
>            Priority: Minor
>         Attachments: HSEARCH-200.patch
>
>
> http://forum.hibernate.org/viewtopic.php?t=987001

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