[hibernate-issues] [Hibernate-JIRA] Updated: (HSEARCH-632) Make sure indexAsNull and Query DSL work like a charm together
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-632?pag...
]
Hardy Ferentschik updated HSEARCH-632:
--------------------------------------
Comment: was deleted
(was: The following already works fine:
{code}
QueryBuilder queryBuilder = getSearchFactory().buildQueryBuilder().forEntity( Value.class
).get();
queryBuilder.keyword().onField( "value" ).matching( null ).createQuery();
{code}
Problematic is:
{code}
QueryBuilder queryBuilder = getSearchFactory().buildQueryBuilder().forEntity( Value.class
).get();
queryBuilder.keyword().onField( "value" ).ignoreFieldBridge().matching( null
).createQuery();
{code}
Probably best to throw a {{SearchException}} in this case.
Regarding the analyzers. The responsibility lies with the user. )
Make sure indexAsNull and Query DSL work like a charm together
--------------------------------------------------------------
Key: HSEARCH-632
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-632
Project: Hibernate Search
Issue Type: Improvement
Components: query
Affects Versions: 3.3.0.CR1
Reporter: Emmanuel Bernard
Assignee: Hardy Ferentschik
Fix For: 3.3.0
HSEARCH-115
In particular stuffs like
{code}
keyword().onField("name").matching(null)
keyword().onField("date").matching(null)
{code}
This is not an exhaustive list.
The second point is how do analyzers and the null marker collapse? Is it the
responsibility of the user to chose a token that passes through the analyzer (I'm
thinking about ngram analyzers for example).
--
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira