[
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
Make use of the new faceting API offered by Lucene
--------------------------------------------------
Key: HSEARCH-809
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-809
Project: Hibernate Search
Issue Type: Task
Components: engine
Affects Versions: 3.4.0.Final
Reporter: Hardy Ferentschik
Assignee: Hardy Ferentschik
Fix For: 4.0
Instead of relying on the custom _FieldCache_ approach for faceting, we should make use
of the API Lucene itself offers now. Or at least investigate how it is implemented in
Lucene. Hopefully this will also address the problem that the _FieldCache_ approach. See
also
https://issues.apache.org/jira/browse/LUCENE-3079
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira