[Hibernate-JIRA] Created: (HSEARCH-960) Index.UN_TOKENIZED overrides other tokenized fields that share the same name
8:30 p.m.
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
Marking one field as un-tokenized causes all other fields with the same names to be
un-tokenized.
i.e.
@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;
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
2:28 a.m.
New subject: [Hibernate-JIRA] Updated: (HSEARCH-960) Index.UN_TOKENIZED overrides other tokenized fields that share the same name
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-960?pag...
]
Sanne Grinovero updated HSEARCH-960:
------------------------------------
Fix Version/s: 4.0.0.CR2
3.4.2
Hi, would you expect this to work? When you search on the field you will need to know if
all fields of a specific name where indexed as tokenized or not, as you will need
different kinds of queries.
I think this should be solved by throwing an exception, or am I missing a valid use case?
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
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.
@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;
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
2:42 a.m.
New subject: [Hibernate-JIRA] Updated: (HSEARCH-960) Index.UN_TOKENIZED overrides other tokenized fields that share the same name
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-960?pag...
]
Hardy Ferentschik updated HSEARCH-960:
--------------------------------------
Description:
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.
was:
Marking one field as un-tokenized causes all other fields with the same names to be
un-tokenized.
i.e.
@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;
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.
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
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
2:58 a.m.
New subject: [Hibernate-JIRA] Commented: (HSEARCH-960) Index.UN_TOKENIZED overrides other tokenized fields that share the same name
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-960?pag...
]
Hardy Ferentschik commented on HSEARCH-960:
-------------------------------------------
I maybe can understand the use case of using _Index.TOKENIZED_ and _Index.UN_TOKENIZED_
for the same field name, but what if you take the other indexing options into account as
well.
I am also interested in the actual use case. Is the idea to write a query which targets
only one field?
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
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
3:18 p.m.
New subject: [Hibernate-JIRA] Commented: (HSEARCH-960) Index.UN_TOKENIZED overrides other tokenized fields that share the same name
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-960?pag...
]
John-Michael Au commented on HSEARCH-960:
-----------------------------------------
We have a single "simple search" box for all our lists- the approach we've
used is to add an additional @Field annotation for each value we want users to be able to
search on. Yes, we use a single query on the "simple_search" field, as opposed
to using a multi-field approach. We've found that this offers an equivalent amount of
search granularity, as well as effectively hiding the need for each application to
"know" the required field(s) for searching.
I'm not sure that the indexed value needs to be known before executing a query; the
reason we've marked certain fields as un-tokenized is to enforce the return of
complete matches (in the case of ID fields, etc.). Since indexing multiple fields with the
same name is done via concatenation of tokens, it seems logical that non-tokenized values
should merely be appended to whatever values were already indexed at that point.
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
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
3:46 p.m.
New subject: [Hibernate-JIRA] Commented: (HSEARCH-960) Index.UN_TOKENIZED overrides other tokenized fields that share the same name
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-960?pag...
]
Sanne Grinovero commented on HSEARCH-960:
-----------------------------------------
Hi, thank you for the explanation.
Still you might have a problem: let's say you have an entity with the two fields
annotated as in your description, having the values "ID5" and "Title of
this book", and you use an Analyzer which includes lowercasing and removal of digits.
Now during the query, you'll have to apply the same analyzer - which one? If you
process the user input with the same analyzer your users will never be able to find
"ID5", while if you don't process them they will need to type exactly
"Title of this book", matching the same case, same whitespace and all terms in
exactly the same order.
So in both cases you'll have elements in the index which can't be found and
can't possibly produce hits - you would be better off with not indexing them at all.
Indexing multiple properties in the same field is indeed useful for the reasons as you
say, but I'm afraid that to be useful they should all use the same Analyzer and Index
options.
I think we should throw an exception or log a warning - unless someone can make a good
example of a valid combination of a mismatched set of options.
Also.. why do you have users search for ID fields?
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
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
4:45 p.m.
New subject: [Hibernate-JIRA] Commented: (HSEARCH-960) Index.UN_TOKENIZED overrides other tokenized fields that share the same name
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-960?pag...
]
John-Michael Au commented on HSEARCH-960:
-----------------------------------------
Hi Sanne,
In our case, having an ID (I apologize for the ambiguity- these are not the actual object
identifiers as in the database table primary keys) such as '1234.56.abcd' which we
would like to be added verbatim to the index, and text such as '1234 Years Ago'
which should be tokenized. In this case of course, 1234 should match the document with
'1234 Years Ago', but not '1234.56.abcd'.
I understand that the standard tokenizer will not break up '1234.56.abcd' anyway,
but it does seem that such behaviour should be explicitly defined rather than implied by
the functionality of other components. I suppose that if you look at it from the point of
view that multiple fields with the same name should essentially behave as one field, being
able to specify different indexing options for each field doesn't make much sense. On
the other hand, if you see the field as the end-product of concatenation of other
individual fields, it would make sense if each field could be indexed as required.
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
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
4:50 p.m.
New subject: [Hibernate-JIRA] Commented: (HSEARCH-960) Index.UN_TOKENIZED overrides other tokenized fields that share the same name
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-960?pag...
]
Sanne Grinovero commented on HSEARCH-960:
-----------------------------------------
right you have a point. But even assuming that this mapping was possible, in your example
of '1234 Years Ago' and '1234.56.abcd' being present in the index, would
you tokenize or would you not tokenize the query input? Are you thinking in querying the
index on both options by building a boolean query?
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
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
4:55 p.m.
New subject: [Hibernate-JIRA] Commented: (HSEARCH-960) Index.UN_TOKENIZED overrides other tokenized fields that share the same name
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-960?pag...
]
John-Michael Au commented on HSEARCH-960:
-----------------------------------------
Querying done using the standard analyzer/standard query parser; so search terms are
automatically tokenized and lowercased in an identical manner to how the values are
indexed. In this case '1234.56.abcd' fed through the box will in fact be written
as +simple_search:1234.56.abcd
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
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
5:13 p.m.
New subject: [Hibernate-JIRA] Updated: (HSEARCH-960) Index.UN_TOKENIZED overrides other tokenized fields that share the same name
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-960?pag...
]
Sanne Grinovero updated HSEARCH-960:
------------------------------------
Suitable for new contributors: [Yes, likely]
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
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
5:13 p.m.
New subject: [Hibernate-JIRA] Commented: (HSEARCH-960) Index.UN_TOKENIZED overrides other tokenized fields that share the same name
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-960?pag...
]
Sanne Grinovero commented on HSEARCH-960:
-----------------------------------------
ok, you convinced me of it's usefulness :) Now we just need to find the time to fix
it, a volunteer?
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
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
9:27 a.m.
New subject: [Hibernate-JIRA] Assigned: (HSEARCH-960) Index.UN_TOKENIZED overrides other tokenized fields that share the same name
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-960?pag...
]
Sanne Grinovero reassigned HSEARCH-960:
---------------------------------------
Assignee: Hardy Ferentschik
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
10:35 a.m.
New subject: [Hibernate-JIRA] Commented: (HSEARCH-960) Index.UN_TOKENIZED overrides other tokenized fields that share the same name
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-960?pag...
]
Hardy Ferentschik commented on HSEARCH-960:
-------------------------------------------
After reviewing some code and digging a little deeper I am not so sure that we actually
can do something. The problem is not so much on the Hibernate Search side, than on the
Lucene API.
On the Search side we actually keep the metadata per field and use the right option when
building the document. See _assertValuesAreIndexedWithDifferentAnalyzeSettings_ of this
[test|https://github.com/hferentschik/hibernate-search/blob/a0352df5845c18...]
The problem is that the analyzing step does not occur at the time the _Document_ is built,
but when we add the document is added to the index (see eg _AddWorkDelegate_ -
{code}writer.addDocument( work.getDocument(), analyzer ){code})
Analyzers work per field name and we have our own implementation _ScopedAnalyzer_.
Depending on a field name it returns an analyzer. In the case of non analyzed field we use
_PassThroughAnalyzer_. To implement the described use case our _ScopedAnalyzer_ would have
to return in one case the _PassThroughAnalyzer_ and in the other the _StandardAnalyzer_
for the same field name. There is not enough information to make the distinction.
I think we are better of logging a warning or throwing an exception. Or does anyone have a
better idea?
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
10:49 a.m.
New subject: [Hibernate-JIRA] Commented: (HSEARCH-960) Index.UN_TOKENIZED overrides other tokenized fields that share the same name
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-960?pag...
]
Sanne Grinovero commented on HSEARCH-960:
-----------------------------------------
Right. Your explanation makes it sound a limitation of how we do it, but it's just a
Lucene API limitation; sorry for not thinking about that right away.
I'd vote for the warning to be logged for now.
In the long term, we could actually work around Lucene's limitation implementing
pre-index tokenization; something which is on my whish list to improve clustering.
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
1:53 p.m.
New subject: [Hibernate-JIRA] Commented: (HSEARCH-960) Index.UN_TOKENIZED overrides other tokenized fields that share the same name
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-960?pag...
]
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
3:57 p.m.
New subject: [Hibernate-JIRA] Commented: (HSEARCH-960) Index.UN_TOKENIZED overrides other tokenized fields that share the same name
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-960?pag...
]
Sanne Grinovero commented on HSEARCH-960:
-----------------------------------------
{quote}Do you see any drawback in doing it ourselves?{quote}
Lucene can do some crazy performance optimizations, for example but not only by skipping
String instance generation; we should make sure we don't lose such benefits so
it's not trivial and introduces even more maintenance for every Lucene version
chance.
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
10:34 a.m.
New subject: [Hibernate-JIRA] Updated: (HSEARCH-960) Index.UN_TOKENIZED overrides other tokenized fields that share the same name
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-960?pag...
]
Hardy Ferentschik updated HSEARCH-960:
--------------------------------------
Fix Version/s: (was: 3.4.2)
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: 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
7:12 a.m.
New subject: [Hibernate-JIRA] Resolved: (HSEARCH-960) Index.UN_TOKENIZED overrides other tokenized fields that share the same name
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-960?pag...
]
Hardy Ferentschik resolved HSEARCH-960.
---------------------------------------
Resolution: Fixed
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: 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
4583
days inactive
4604
days old
hibernate-issues@lists.jboss.org
17 comments
3 participants
participants (3)
-
Hardy Ferentschik (JIRA) -
John-Michael Au (JIRA)
-
Sanne Grinovero (JIRA)