Facetted search on embedded collections takes only first element from collection -------------------------------------------------------------------------------- Key: HSEARCH-726 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-726 Project: Hibernate Search Issue Type: Bug Components: query Affects Versions: 3.4.0.Alpha1, 3.4.0.Beta1, 3.4.0.CR1, 3.4.0.CR2 Environment: Any valid config I suppose, tested using Hibernate Core 3.6.3 + Search 3.4.0.CR2, mysql and in Hibernate Search test environment Reporter: Elmer van Chastelet Attachments: EmbeddedCollectionsFacetsTest.zip, HSEARCH-726.zip From [Hibernate Search Forum: Bug or not? Faceted search + embedded fields (*tomany)|https://forum.hibernate.org/viewtopic.php?f=9&t=1010472&start=0]. Faceted search won't work correctly when used on collections. For the cause I quote Hardy Ferentschik : ??The current faceting implementation utilizes the Lucene FieldCache which has a limitation that each document must have a single value for the specified field.?? I can think of many use cases in which faceted search on collections is really needed, some examples: Facetting on authors when searching for publications Facetting on ingredients when searching for recipes Facetting on actors when searching for movies ... Attached is a hibernate search test case. It fails on retrieving the right amount of matched authors. Currently I don't have the needed insight to suggest an improvement on current implementation to make it compatible with collections. Hopefully it can be achieved with small changes. Good luck :)

Facetted search on embedded collections takes only first element from collection -------------------------------------------------------------------------------- Key: HSEARCH-726 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-726 Project: Hibernate Search Issue Type: Bug Components: query Affects Versions: 3.4.0.Alpha1, 3.4.0.Beta1, 3.4.0.CR1, 3.4.0.CR2 Environment: Any valid config I suppose, tested using Hibernate Core 3.6.3 + Search 3.4.0.CR2, mysql and in Hibernate Search test environment Reporter: Elmer van Chastelet Attachments: EmbeddedCollectionsFacetsTest.zip, HSEARCH-726.zip From [Hibernate Search Forum: Bug or not? Faceted search + embedded fields (*tomany)|https://forum.hibernate.org/viewtopic.php?f=9&t=1010472&start=0]. Faceted search won't work correctly when used on collections. For the cause I quote Hardy Ferentschik : ??The current faceting implementation utilizes the Lucene FieldCache which has a limitation that each document must have a single value for the specified field.?? I can think of many use cases in which faceted search on collections is really needed, some examples: Facetting on authors when searching for publications Facetting on ingredients when searching for recipes Facetting on actors when searching for movies ... Attached is a hibernate search test case. It fails on retrieving the right amount of matched authors. Currently I don't have the needed insight to suggest an improvement on current implementation to make it compatible with collections. Hopefully it can be achieved with small changes. Good luck :)

Facetted search on embedded collections takes only first element from collection -------------------------------------------------------------------------------- Key: HSEARCH-726 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-726 Project: Hibernate Search Issue Type: Bug Components: query Affects Versions: 3.4.0.Alpha1, 3.4.0.Beta1, 3.4.0.CR1, 3.4.0.CR2 Environment: Any valid config I suppose, tested using Hibernate Core 3.6.3 + Search 3.4.0.CR2, mysql and in Hibernate Search test environment Reporter: Elmer van Chastelet Fix For: 4.0 Attachments: EmbeddedCollectionsFacetsTest.zip, HSEARCH-726.zip From [Hibernate Search Forum: Bug or not? Faceted search + embedded fields (*tomany)|https://forum.hibernate.org/viewtopic.php?f=9&t=1010472&start=0]. Faceted search won't work correctly when used on collections. For the cause I quote Hardy Ferentschik : ??The current faceting implementation utilizes the Lucene FieldCache which has a limitation that each document must have a single value for the specified field.?? I can think of many use cases in which faceted search on collections is really needed, some examples: Facetting on authors when searching for publications Facetting on ingredients when searching for recipes Facetting on actors when searching for movies ... Attached is a hibernate search test case. It fails on retrieving the right amount of matched authors. Currently I don't have the needed insight to suggest an improvement on current implementation to make it compatible with collections. Hopefully it can be achieved with small changes. Good luck :)

Facetted search on embedded collections takes only first element from collection -------------------------------------------------------------------------------- Key: HSEARCH-726 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-726 Project: Hibernate Search Issue Type: Bug Components: query Affects Versions: 3.4.0.Alpha1, 3.4.0.Beta1, 3.4.0.CR1, 3.4.0.CR2 Environment: Any valid config I suppose, tested using Hibernate Core 3.6.3 + Search 3.4.0.CR2, mysql and in Hibernate Search test environment Reporter: Elmer van Chastelet Attachments: EmbeddedCollectionsFacetsTest.zip, HSEARCH-726.zip From [Hibernate Search Forum: Bug or not? Faceted search + embedded fields (*tomany)|https://forum.hibernate.org/viewtopic.php?f=9&t=1010472&start=0]. Faceted search won't work correctly when used on collections. For the cause I quote Hardy Ferentschik : ??The current faceting implementation utilizes the Lucene FieldCache which has a limitation that each document must have a single value for the specified field.?? I can think of many use cases in which faceted search on collections is really needed, some examples: Facetting on authors when searching for publications Facetting on ingredients when searching for recipes Facetting on actors when searching for movies ... Attached is a hibernate search test case. It fails on retrieving the right amount of matched authors. Currently I don't have the needed insight to suggest an improvement on current implementation to make it compatible with collections. Hopefully it can be achieved with small changes. Good luck :)