[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-809?pag... ] Hardy Ferentschik commented on HSEARCH-809: ------------------------------------------- some initial thoughts: * need to include lucene-facet module * need to manage the new taxonomy index and make sure it is kept in sync with the actual index * might want to expose access to the taxonomy index via an API (not really required though. would be a power user feature) * current approach is agnostic of whether faceting is used. It uses the normal document fields. With Lucene's faceting approach we need to update the taxonomy index at indexing time. This means the user must somehow specify which fields are faceted under which facet path. Either we introduce a new annotation for that or we extend _@Field_ * Lucene's faceting can support current Search faceting API, but can offer even more. We need to decide how much more we want to expose and how we expose it -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-809?pag... ] Hardy Ferentschik edited comment on HSEARCH-809 at 9/21/11 2:05 PM: -------------------------------------------------------------------- We probably need to extends some of the _LuceneWork_ types to pass along the taxonomy information so that we can enhance/rebuild the _Document_ in the _LuceneWorkDelegate_ using the _CategoryDocumentBuilder_. This would require that _LuceneWorkDelegate#performWork_ also received a taxonomy writer. If I understand our new packaging scheme correctly it would be ok to change the API, because it is internal. was (Author: hardy.ferentschik): We probably need to extends some of the _LuceneWork_ types to pass along the taxonomy information so that we can enhance/rebuild the _Document_ in the _LuceneWorkDelegate_ using the _CategoryDocumentBuilder_. This would require that _LuceneWorkDelegate#performWork_ also received a taxonomy writer. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-809?pag... ] Hardy Ferentschik edited comment on HSEARCH-809 at 9/22/11 4:04 AM: -------------------------------------------------------------------- We probably need to extends some of the _LuceneWork_ types to pass along the taxonomy information so that we can enhance/rebuild the _Document_ in the _LuceneWorkDelegate_ using the _CategoryDocumentBuilder_. This would require that _LuceneWorkDelegate#performWork_ also received a taxonomy writer. If I understand our new packaging scheme correctly it would be ok to change the API, because it is internal. Changing _LuceneWork_ will require to update the serialization protocol with all the information we add for faceting. On top of the actual facet categories, there are several taxonomy indexing parameters which can be set and might be send along. was (Author: hardy.ferentschik): We probably need to extends some of the _LuceneWork_ types to pass along the taxonomy information so that we can enhance/rebuild the _Document_ in the _LuceneWorkDelegate_ using the _CategoryDocumentBuilder_. This would require that _LuceneWorkDelegate#performWork_ also received a taxonomy writer. If I understand our new packaging scheme correctly it would be ok to change the API, because it is internal. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-809?pag... ] Emmanuel Bernard updated HSEARCH-809: ------------------------------------- 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