[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-904) Have TwoWayFieldBridge report which fields should be loaded from a Document

[Hardy Ferentschik (JIRA)]

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

Hardy Ferentschik commented on HSEARCH-904:
-------------------------------------------

the initial plan was to get rid of the _LuceneOptions_ parameter in _FieldBridge_ as well and move it into the _initialize_ method. It turns out thought that the _LuceneOptions_ are not static as expected. In fact a new _LuceneOptions_ is created for each call to _FieldBridge#set_. See also _PropertiesMetadata#getClassLuceneOptions_ and _PropertiesMetadata#getFieldLuceneOptions_. The field lucene option can differ in the boost value, since it can apply a dynamic boost. Also for indexing null tokens a custom _LuceneOptions_ is used.
So we can:
# Introduce _FieldBridge#initalize(String fieldName)_ and leave the _LuceneOptions_ as part of set
# Dig deeper and find a better way to handle dynamic boosting
Thoughts!?

> Have TwoWayFieldBridge report which fields should be loaded from a Document
> ---------------------------------------------------------------------------
>
>                 Key: HSEARCH-904
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-904
>             Project: Hibernate Search
>          Issue Type: Task
>            Reporter: Sanne Grinovero
>            Assignee: Hardy Ferentschik
>             Fix For: 4.0.0.Beta2
>
>
> This is needed to use a FieldSelector in more cases. See also HSEARCH-213.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira