[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-960) Index.UN_TOKENIZED overrides other tokenized fields that share the same name
Hardy Ferentschik (JIRA)
noreply at atlassian.com
Thu Nov 10 14:53:22 EST 2011
[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44294#comment-44294 ]
Hardy Ferentschik commented on HSEARCH-960:
-------------------------------------------
Right, let's go for a warning for now
I like the idea of taking care of the analyizing step. As you say, we could do this earlier similar to what we do in Analyzer utils. Would also make dynamic analyzer selection easier. Do you see any drawback in doing it ourselves?
Nevertheless, for now let's stick with what we have and add a warning.
> Index.UN_TOKENIZED overrides other tokenized fields that share the same name
> ----------------------------------------------------------------------------
>
> Key: HSEARCH-960
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-960
> Project: Hibernate Search
> Issue Type: Bug
> Components: mapping
> Affects Versions: 3.4.0.Final
> Environment: 3.4.0 Final
> Reporter: John-Michael Au
> Assignee: Hardy Ferentschik
> Labels: annotations, bug, override, tokenized, un_tokenized
> Fix For: 3.4.2, 4.0.0.CR2
>
>
> Marking one field as un-tokenized causes all other fields with the same names to be un-tokenized.
> i.e.
> {code}
> @Field(name = "simple_search", index = Index.UN_TOKENIZED, store = Store.NO)
> private String string;
> @Field(name = "simple_search", index = Index.TOKENIZED, store = Store.NO)
> private String string2;
> {code}
> The resulting behaviour is that "simple_search" will be made up of un-tokenized 'string' and 'string2' values, even though 'string2' was specified to be tokenized.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list