lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Toke Eskildsen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-792) Pivot (ie: Decision Tree) Faceting Component
Date Sun, 07 Nov 2010 21:26:08 GMT

    [ https://issues.apache.org/jira/browse/SOLR-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929401#action_12929401
] 

Toke Eskildsen commented on SOLR-792:
-------------------------------------

The current interface does not allow for nested queries. It is my understanding that this
limits the functionality to conventional hierarchical faceting with the slight twist that
the counts are for the current level instead of current level + sub levels, but that should
be attainable with conventional hierarchical faceting too. This makes current pivot faceting
a sub-set of SOLR-64, provided that SOLR-64 is adjusted to accept a list of fields as building
blocks instead of expressing the hierarchy in a single field with delimiters. This is a good
thing. It means that it can be done fast and memory-efficient as well as sharing most of the
interface and output format with SOLR-64.

Now, if something like nested queries is introduced in the pivot faceting interface, this
changes the requirements of the underlying code as a complete recount is needed for each level.
One evil nested query could be "Select the documents where field X contains the last letter
of the current tag plus the first letter of the original query". This makes it hard (I try
and avoid using the word "impossible") to create an implementation without query-explosion.

So where am I going with all this? My point is that the interface (of course) dictates how
responsive the implementation can be. Focusing on interfaces and using small-scale test data
does carry a risk of ending up with something that is inherently slow. It might be unfeasible
to attain high scalability with a given interface addition and that is okay - as long as that
cost is known and accepted. Hence my questions about scale and my musings about how to do
it faster.

> Pivot (ie: Decision Tree) Faceting Component
> --------------------------------------------
>
>                 Key: SOLR-792
>                 URL: https://issues.apache.org/jira/browse/SOLR-792
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Erik Hatcher
>            Assignee: Yonik Seeley
>            Priority: Minor
>         Attachments: SOLR-792-as-helper-class.patch, SOLR-792-PivotFaceting.patch, SOLR-792-PivotFaceting.patch,
SOLR-792-PivotFaceting.patch, SOLR-792-PivotFaceting.patch, SOLR-792-raw-type.patch, SOLR-792.patch,
SOLR-792.patch, SOLR-792.patch, SOLR-792.patch, SOLR-792.patch, SOLR-792.patch, SOLR-792.patch
>
>
> A component to do multi-level faceting.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message