Expand selection on PathFacetHandler

[Roman_Garcia]

Hi,

I see there's another thread here for PathFacetHandler not working,
but I can't seem to find any issue on Jira about this.

Shall I create one for this? Or is there a reason why anyone thinks
this is a won't fix or something?

If I can help anyone with this fix, just let me know.

Regards,
Roman

[John Wang]

Hi Roman:

     Absolutely! http://linkedin.jira.com

-John

--
You received this message because you are subscribed to the Google Groups "bobo-browse" group.
To post to this group, send email to bobo-...@googlegroups.com.
To unsubscribe from this group, send email to bobo-browse...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/bobo-browse?hl=en.

[Roman_Garcia]

Done! http://linkedin.jira.com/browse/BOBO-87

Let me know if I can help

Thanks!

Roman

[Volker]

I have also a problem with PathFacetHandler. As long a the index is
newly generated everthing is working as it should. But when some new
entries are added, I get wrong results for the beginning auf the path.
Only the last node is showing the correct number. the values at the
beginning change over time. they can go e.g. down to one and after
some more entries are added jump up to 1000. so they are not stable
(only as long, as there are no new entries added). Do you have any
suggestions what might be the problem?

I am using lucene 3.1 and build from bobo 3.x

kind regards

[John Wang]

Do you have a reproducible test case? If so, would you mind open a ticket with the test case at linkedin.jira.com and we will get to it right away, and hopefully include it in the next bobo release.

Thanks

-John

--
You received this message because you are subscribed to the Google Groups "bobo-browse" group.

[Volker]

Up to now I have not a test case. But I will see whether I can
reproduce it outside our production index and will then produce a test
case for the problem.

thanks!

kind regards

[Volker]

I have not found the time to create a testcase yet.

But I found, that, when I have an unoptimized index, I sometimes get
the same facet more than once.and all added hit counts for the facet
are correct. But the problem is, that a get e.g.

value:1/2/3/4/ count:261
value:1/2/3/4/ count:85
value:1/2/3/4/ count:6

instead of

value:1/2/3/4/ count:352

does anyone have a hint, where the problem may arise, so that I can
try to fix it?

kind regards