Debugging Bobo results

20 views
Skip to first unread message

mschipperheyn

unread,
Nov 1, 2011, 9:30:25 AM11/1/11
to bobo-browse
Hi,

Bobo/Lucene is my number one time consumer when it comes to "things
that at first glance don't work as expected".
I use Luke as a way to test Browse Requests but I usually lose
enormous amounts of time when the BrowseRequest that I copy from the
BrowseRequest instance produces a result in Luke, but Bobo doesn't or
a different one. In my case I also use a numeric date field as a
filter which Luke doesn't support but when that is eliminated as a
factor, then the hours start going crazy.

It's often times quite hard to analyze why Bobo produces a certain
result or more specifically: a different result than Luke.

I'm wondering what recommendations the Bobo team has for these
situations? What steps can be recommended for drilling down to the
real issue as quickly as possible?

Kind regards,

Marc

John Wang

unread,
Nov 1, 2011, 1:26:25 PM11/1/11
to bobo-...@googlegroups.com
Hi Marc:

    We generally write a test Client to reproduce issues.

    But sounds like a Luke extension for Bobo is useful?

-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.


mschipperheyn

unread,
Nov 2, 2011, 8:34:19 AM11/2/11
to bobo-browse
That would be awesome yes. But one of the fundamental problems with
Luke is the fac that it doesn't seems to allow you to use numerical
field types.
A good start might also be to add the actual index field name to the
toString method for the BrowseRequest.
That would make it easier to eliminate stupid mistakes such as
mispelling the index field name.
Also, not sure how this would affect performance, but it would be a
good idea to throw a warnif an index field name doesn't exist.

Ok, all this is one class of bugs.The basic ability to get a Luke like
interface to the a Bobo managed index so that you're typed in query
would produce the same results as your programmatic query would be
awesome.

On Nov 1, 3:26 pm, John Wang <john.w...@gmail.com> wrote:
> Hi Marc:
>
>     We generally write a test Client to reproduce issues.
>
>     But sounds like a Luke extension for Bobo is useful?
>
> -John
>

mschipperheyn

unread,
Nov 2, 2011, 8:40:30 AM11/2/11
to bobo-browse
I guess my most difficult issues are the ones like I have now.
I have a browse request with two active facet selections on different
facets.
Bobo produces no result which I dont expect.
In Luke I type in the browse request query + the two facet selections
as +facet1fieldname:value +facet2fieldname:value. This produces the
expected results.

These are the issues that eat of loads and loads of time because it
doesn't make sense to (until it sometimes does).
I would love to have a toString method that translates the entire Bobo
Request into a Lucene compatible query (including the facet
selections).

mschipperheyn

unread,
Nov 2, 2011, 8:50:03 AM11/2/11
to bobo-browse
Reply all
Reply to author
Forward
0 new messages