[hibernate-issues] [Hibernate-JIRA] Updated: (HSEARCH-697) Think about improving type mismatch detection between QueryBuilder output and targeted FullTextQuery

[Sanne Grinovero (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sanne Grinovero updated HSEARCH-697:
------------------------------------

    Fix Version/s:     (was: 4.1)

> Think about improving type mismatch detection between QueryBuilder output and targeted FullTextQuery
> ----------------------------------------------------------------------------------------------------
>
>                 Key: HSEARCH-697
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-697
>             Project: Hibernate Search
>          Issue Type: Bug
>          Components: query
>            Reporter: Sanne Grinovero
>            Assignee: Emmanuel Bernard
>
> Use cases:
> 1)we ask for the target type when creating a QueryBuilder, then we ask again for the same information again at FullTextQuery creation - they must match.
> 2)it seems that when people get the match wrong, they receive cryptic error messages (see https://forum.hibernate.org/viewtopic.php?f=9&t=1009700 )
> It would be nice if we could infer the target type from the builder, we'd likely have to introduce a new class hiding away org.apache.search.Query in something which knows a bit more about types. Or maybe introduce a new method in FullTextSession to create a Hibernate.Query directly from the builder, projecting on the known types.
> train of thoughts.. maybe this could lead to a typesafe API to define fulltext projections reusing JPA2 metamodel in case it's available.

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