lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rodrigo Vega (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4461) Multiple FacetRequest with the same path creates inconsistent results
Date Tue, 09 Oct 2012 14:39:02 GMT


Rodrigo Vega commented on LUCENE-4461:

Yes, I know that but i need a generic way to handle the facet requests during search preparation
stage. For that reason I have a FacetParams object with the following properties: int limit,
String[] path, boolean filter

Then I can have some peace of code like this:

// Query is a bean that wraps a lucene query just to make easy the integration with our UI.
REal lucene query is // handle by "q"
if (query.isFaceted())
	for (FacetParams facet : query.getFacet()) {

		CategoryPath c = new CategoryPath(facet.getPath());
		facetSearchParams.addFacetRequest(new CountFacetRequest(c, facet.getLimit()));

		if (facet.isFilter())
			q = DrillDown.query(q, c);

... preapre collectors and finally search

This is because the user can create its own query using some kind of wizard. So I have two
* Support this feature
* Avoid configurations with this kind of cases.

It is not a really big problem it is mostly about how to keep my code as neat as I can :)
. I can't ask you to solve my code issues :D
> Multiple FacetRequest with the same path creates inconsistent results
> ---------------------------------------------------------------------
>                 Key: LUCENE-4461
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: modules/facet
>    Affects Versions: 3.6
>            Reporter: Rodrigo Vega
>              Labels: facet, faceted-search
>         Attachments:
> Multiple FacetRequest are getting merged into one creating wrong results in this case:
> FacetSearchParams facetSearchParams = new FacetSearchParams();
> 		facetSearchParams.addFacetRequest(new CountFacetRequest(new CategoryPath("author"),
> 		facetSearchParams.addFacetRequest(new CountFacetRequest(new CategoryPath("author"),
> Problem can be fixed by defining hashcode and equals in certain way that Lucene recognize
we are talking about different requests.
> Attached test case.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message