Lucene 3.0.3 with debug information

Hey paul,

you can simply checkout the tag or download the sources right?
http://svn.apache.org/repos/asf/lucene/java/tags/lucene_3_0_3/
or http://ftp.download-by.net/apache//lucene/java/3.0.3/

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

Can you expand on this too? What kind of "incredible bugs" did you see?
Without feedback there is little progress, so bug reports count.

Dawid

Instead of profiling, provide some more info about the following:

- what are the problematic (slow) queries -- are they generated from the
code, are they parsed from text? What are they? Certain query types are
slow(er) than other query types.

- what is the index built from? Natural language (text)? Something else?

If you describe the above folks may tell you right away why your queries are
slow -- people on this list continue to amaze me with the insight they have
even without looking at the code ;)

Dawid

This is the e-mail you're looking for, Steven (it wasn't forwarded to the
list, apparently).

Dawid

---------- Forwarded message ----------
From: Paul Taylor <paul_t100@fastmail.fm>
Date: Fri, Apr 29, 2011 at 10:11 PM
Subject: Re: Lucene 3.0.3 with debug information
To: Dawid Weiss <dawid.weiss@gmail.com>


On 29/04/2011 15:17, Dawid Weiss wrote:


Can you expand on this too? What kind of "incredible bugs" did you see?
Without feedback there is little progress, so bug reports count.

Dawid

Sorry, I'll withdraw that. I was getting all kinds of stacktraces and
exceptions when I tried to do searches but the problem was my fault. Because
I wanted to use my own analyzer I had a shells script that added it to the
classpath when I ran luke, however I had put it before the ant jar and my
jar built with maven also included lucene 3.0.3 and because luke 1.0.1 is
packaged with 3.0.0 it was confusing it, but I didnt realize this until I
notice done exception complained a lucene method was missing.

But having got it working I cannot see anything to help me work out why the
queries are taking too long, is it useful for this or just for refining your
queries ?

Paul

Thanks Dawid. – Steve

From: dawid.weiss@gmail.com On Behalf Of Dawid Weiss
Sent: Friday, April 29, 2011 4:45 PM
To: java-user@lucene.apache.org
Cc: Steven A Rowe
Subject: Lucene 3.0.3 with debug information


This is the e-mail you're looking for, Steven (it wasn't forwarded to the list, apparently).

Dawid
---------- Forwarded message ----------
From: Paul Taylor <paul_t100@fastmail.fm
Date: Fri, Apr 29, 2011 at 10:11 PM
Subject: Re: Lucene 3.0.3 with debug information
To: Dawid Weiss <dawid.weiss@gmail.com
Can you expand on this too? What kind of "incredible bugs" did you see? Without feedback there is little progress, so bug reports count.

Dawid
Sorry, I'll withdraw that. I was getting all kinds of stacktraces and exceptions when I tried to do searches but the problem was my fault. Because I wanted to use my own analyzer I had a shells script that added it to the classpath when I ran luke, however I had put it before the ant jar and my jar built with maven also included lucene 3.0.3 and because luke 1.0.1 is packaged with 3.0.0 it was confusing it, but I didnt realize this until I notice done exception complained a lucene method was missing.

But having got it working I cannot see anything to help me work out why the queries are taking too long, is it useful for this or just for refining your queries ?

Paul

Hi Paul,

What did you find about Luke that's buggy? Bug reports are very useful; please contribute in this way.

The official Lucene 3.0.3 distribution jars were compiled using the -g cmdline argument to javac - by default, though, only line number and source file information is generated. If you want local variable information too, you could download the source and make your own debug-enabled jar(s), right?:

0. Install Ant 1.7.1: <http://archive.apache.org/dist/ant/binaries/>

1. svn checkout http://svn.apache.org/repos/asf/lucene/java/tags/lucene_3_0_3

2. Add 'debuglevel="lines,source,vars"' to the "compile" <macrodef> in common-build.xml <http://svn.apache.org/viewvc/lucene/java/tags/lucene_3_0_3/common-build.xml?revision=1040994&view=markup#l536> in the <javac> task invocation, e.g.:

545: <javac
546: encoding="${build.encoding}"
547: srcdir="@{srcdir}"
548: destdir="@{destdir}"
549: deprecation="${javac.deprecation}"
550: debug="${javac.debug}"
Add --> debuglevel="lines,source,vars"
...

3. run "ant clean jar" from the command line. The Lucene core jar will be in the build/ directory. (If you need one of the contrib jars, run "ant package" instead.)

Steve

Hmm maybe that is enough, Im not sure. I'm profiling with
YourkitProfiler and it doesnt show anything within the lucene classes so
I assumed this meant they didnt contain the neccessary debugging info
but I would have thought that -g is all I need

thanks Paul

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

Aah, not using the filter correctly in Yourkit Profiler properly,
getting the info now

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

Right, YourKit filters out org.apache.* by default ;) I find it amusing!

Mike

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

Hi Paul,
Okay... Which previous post? I searched for posts by you to Lucene mailing lists, and found no mention of Luke other than the one complaining about bugs?

Steve