[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-682?pag... ] Nick Fenwick updated HSEARCH-682: --------------------------------- Attachment: HSEARCH-682-unittest1.tgz Following advice from Sanne I tried again to make a unit test but again it fails when I run "mvn test -Dtest=neekEmbeddedQueryTest.EmbeddedSearch" with "org.hibernate.MappingException: Unknown entity: neekEmbeddedQueryTest.EmbeddedEntity", the same pattern of error I was getting with JIRA 678. I'd love to know what I'm doing wrong :) -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-682?pag... ] Nick Fenwick commented on HSEARCH-682: -------------------------------------- Just to reiterate.. I cannot move this forward. I am not capable of getting my attached test case to run, probably because I've made some simple error. Would appreciate some assistance in verifying what I've done. If it runs for others as it is, then I know I've got something broken in my local system. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-682?pag... ] Emmanuel Bernard updated HSEARCH-682: ------------------------------------- Fix Version/s: (was: 4.1) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://hibernate.onjira.com/browse/HSEARCH-682?page=com.atlassian.jira.p... ] Sanne Grinovero commented on HSEARCH-682: ----------------------------------------- Davide, thank you; if you have a working test please send a pull request, even if the code is working fine. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://hibernate.onjira.com/browse/HSEARCH-682?page=com.atlassian.jira.p... ] Sanne Grinovero updated HSEARCH-682: ------------------------------------ Description: Changed this to "add test" rather than bug as it actually works fine. Original description: Discussed in https://forum.hibernate.org/viewtopic.php?f=9&t=1009440, "Re: Correct to use ignoreFieldBridge for "subentity.field" DSL?". I find I have to set ignoreFieldBridge when querying for a field indexed using @IndexEmbedded, i.e.: {code}@Entity class CategoryEntity { @Column(name="lft") @Field(name="left", index=Index.UN_TOKENIZED, store=Store.YES) @FieldBridge(impl=PadNumberBridge.class, params = { @Parameter(name="pad", value="4") } ) private int left; ... same for 'right' ... } @Entity class ItemEntity { @IndexedEmbedded(depth=1) private CategoryEntity category; }{code} results in fields for ItemEntity being stored in the Lucene index like: {code} category.left = 0004 category.right = 0012 {code} To query for these, I cannot do: {code} qb.range().onField("category.left").above(4).createQuery() {code} I get an exception saying it doesn't know what FieldBridge to use for "category.left". Instead, I can do: {code} qb.range().onField("category.left").ignoreFieldBridge().above(4).createQuery() {code} but the 'value' is no longer padded according to the FieldBridge that was specified in CategoryEntity for its 'left' attribute, I have to pass value as e.g. "0004". It would be good to mention this situation in the documentation (5.1.2. "Building a Lucene query with the Hibernate Search query DSL"), at least to specify that it is/isn't supported, so that people attempting this kind of @IndexEmbedded mapping know how to safely build a query for such fields. was: Discussed in https://forum.hibernate.org/viewtopic.php?f=9&t=1009440, "Re: Correct to use ignoreFieldBridge for "subentity.field" DSL?". I find I have to set ignoreFieldBridge when querying for a field indexed using @IndexEmbedded, i.e.: {code}@Entity class CategoryEntity { @Column(name="lft") @Field(name="left", index=Index.UN_TOKENIZED, store=Store.YES) @FieldBridge(impl=PadNumberBridge.class, params = { @Parameter(name="pad", value="4") } ) private int left; ... same for 'right' ... } @Entity class ItemEntity { @IndexedEmbedded(depth=1) private CategoryEntity category; }{code} results in fields for ItemEntity being stored in the Lucene index like: {code} category.left = 0004 category.right = 0012 {code} To query for these, I cannot do: {code} qb.range().onField("category.left").above(4).createQuery() {code} I get an exception saying it doesn't know what FieldBridge to use for "category.left". Instead, I can do: {code} qb.range().onField("category.left").ignoreFieldBridge().above(4).createQuery() {code} but the 'value' is no longer padded according to the FieldBridge that was specified in CategoryEntity for its 'left' attribute, I have to pass value as e.g. "0004". It would be good to mention this situation in the documentation (5.1.2. "Building a Lucene query with the Hibernate Search query DSL"), at least to specify that it is/isn't supported, so that people attempting this kind of @IndexEmbedded mapping know how to safely build a query for such fields. Priority: Minor (was: Major) Affects Version/s: (was: 3.3.0.Final) Fix Version/s: 4.1.0.Beta2 Issue Type: Task (was: New Feature) Summary: Add tests for DSL handling fieldBridge for @IndexEmbedded fields (was: DSL cannot handle fieldBridge for @IndexEmbedded fields) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira