[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-632) Make sure indexAsNull and Query DSL work like a charm together

Hardy Ferentschik (JIRA) noreply at atlassian.com
Thu Nov 18 11:42:13 EST 2010


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

Hardy Ferentschik commented on HSEARCH-632:
-------------------------------------------

This 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}
In this case it is probably best to throw a {{SearchException}}

Regarding the analyzers - the responsibility is with the user. I think it most cases a useful usecase will involve a {{TermQuery}} and un-tokenized fields.

> 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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the hibernate-issues mailing list