[
https://issues.apache.org/jira/browse/OAK-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066443#comment-15066443
]
Tommaso Teofili commented on OAK-2511:
--------------------------------------
{quote}
Looks like I confused you when I mentioned to move facet config to a separate
node. What I intended was that top level facet config should be moved to
separate node (#1 below). While property level facet config (which I think is a
single property) remaining a direct property in property definition node (#2
below)
{quote}
ah, got it now! I agree that's probably better.
{quote}
This class is currently adding some nodes at indexing time a node config
directly under index definition node
{quote}
Yes that's the repository persisted version of the in memory {{FacetsConfig}}
class, which is where the config for indexing facets is defined (e.g.
multivalued fields). We currently use it at indexing time only to keep a
consistent config for multivalued fields. Regarding visibility that could be
hidden, as values of that persisted config are anyway created while indexing
and any change human change would be overridden .
> Support for faceted search in Lucene index
> ------------------------------------------
>
> Key: OAK-2511
> URL: https://issues.apache.org/jira/browse/OAK-2511
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: lucene
> Reporter: Tommaso Teofili
> Assignee: Tommaso Teofili
> Fix For: 1.3.13
>
> Attachments: OAK-2511-chetan-1.patch
>
>
> A Lucene index should be able to provide faceted search results, based on the
> support provided in the query engine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
