Re: a few issues with 2.4.1 RC3

2009-03-13 Thread Andi Vajda
On Fri, 13 Mar 2009, Michael McCandless wrote: Andi Vajda wrote: I uploaded a new release candidate, rc4, with this fix to the staging are: http://people.apache.org/~vajda/staging_area/ +1 to release My previous example now works fine. I was able to build & search index of first 100K doc

Re: a few issues with 2.4.1 RC3

2009-03-13 Thread Michael McCandless
Andi Vajda wrote: I uploaded a new release candidate, rc4, with this fix to the staging are: http://people.apache.org/~vajda/staging_area/ +1 to release My previous example now works fine. I was able to build & search index of first 100K docs from wikipedia. Good job! Mike

Re: a few issues with 2.4.1 RC3

2009-03-13 Thread Andi Vajda
On Fri, 13 Mar 2009, Michael McCandless wrote: Andi Vajda wrote: On Fri, 13 Mar 2009, Michael McCandless wrote: OK, I created PYLUCENE-1, yay!: https://issues.apache.org/jira/browse/PYLUCENE-1 Andi can you go add some components to the Jira instance? What do you mean ? Please, give m

Re: a few issues with 2.4.1 RC3

2009-03-13 Thread Michael McCandless
OK thanks Andi. I'll switch to RC4. I opened https://issues.apache.org/jira/browse/LUCENE-1564 for the underlying Lucene bug. Mike Andi Vajda wrote: On Fri, 13 Mar 2009, Andi Vajda wrote: On Fri, 13 Mar 2009, Michael McCandless wrote: * I'm attempting to re-use a field, by changing

Re: a few issues with 2.4.1 RC3

2009-03-13 Thread Michael McCandless
Andi Vajda wrote: On Fri, 13 Mar 2009, Michael McCandless wrote: OK, I created PYLUCENE-1, yay!: https://issues.apache.org/jira/browse/PYLUCENE-1 Andi can you go add some components to the Jira instance? What do you mean ? Please, give me an example. If you go here: https://issu

Re: a few issues with 2.4.1 RC3

2009-03-13 Thread Andi Vajda
On Fri, 13 Mar 2009, Andi Vajda wrote: On Fri, 13 Mar 2009, Michael McCandless wrote: * I'm attempting to re-use a field, by changing its value, and then adding the document to an index: lucene.initVM(lucene.CLASSPATH) writer = lucene.IndexWriter(lucene.RAMDirectory(),

Re: a few issues with 2.4.1 RC3

2009-03-13 Thread Andi Vajda
On Fri, 13 Mar 2009, Michael McCandless wrote: OK, I created PYLUCENE-1, yay!: https://issues.apache.org/jira/browse/PYLUCENE-1 Andi can you go add some components to the Jira instance? What do you mean ? Please, give me an example. Andi.. Mike Andi Vajda wrote: On Fri, 13 Mar 20

Re: a few issues with 2.4.1 RC3

2009-03-13 Thread Michael McCandless
OK, I created PYLUCENE-1, yay!: https://issues.apache.org/jira/browse/PYLUCENE-1 Andi can you go add some components to the Jira instance? Mike Andi Vajda wrote: On Fri, 13 Mar 2009, Michael McCandless wrote: OK it's great that I can .printStackTrace() to see it... But shouldn't we

Re: a few issues with 2.4.1 RC3

2009-03-13 Thread Michael McCandless
Andi Vajda wrote: On Fri, 13 Mar 2009, Michael McCandless wrote: OK it's great that I can .printStackTrace() to see it... But shouldn't we override JavaError.__str__ so by default an unhandled exception originating from Java would reveal its Java trace as well? (And presumably vice/ver

Re: a few issues with 2.4.1 RC3

2009-03-13 Thread Andi Vajda
On Fri, 13 Mar 2009, Michael McCandless wrote: OK it's great that I can .printStackTrace() to see it... But shouldn't we override JavaError.__str__ so by default an unhandled exception originating from Java would reveal its Java trace as well? (And presumably vice/versa). Does that actual

Re: a few issues with 2.4.1 RC3

2009-03-13 Thread Michael McCandless
Andi Vajda wrote: Mike, what do you think ? Indeed this looks like a Lucene bug! Sneaky. I'll take it. Mike

Re: a few issues with 2.4.1 RC3

2009-03-13 Thread Michael McCandless
OK it's great that I can .printStackTrace() to see it... But shouldn't we override JavaError.__str__ so by default an unhandled exception originating from Java would reveal its Java trace as well? (And presumably vice/versa). I think on exception we should try to provide as much info as p

Re: a few issues with 2.4.1 RC3

2009-03-13 Thread Andi Vajda
On Fri, 13 Mar 2009, Michael McCandless wrote: * I'm attempting to re-use a field, by changing its value, and then adding the document to an index: lucene.initVM(lucene.CLASSPATH) writer = lucene.IndexWriter(lucene.RAMDirectory(), lucene.Standar

Re: a few issues with 2.4.1 RC3

2009-03-13 Thread Andi Vajda
On Fri, 13 Mar 2009, Andi Vajda wrote: If, however, you replace the field.setValue('abc') call in the Python code with passing 'abc' to the constructor, it works too. It looks like you found a bug with the setValue() wrapper. I'm looking into it... It also works if one calls field.setValue(

Re: a few issues with 2.4.1 RC3

2009-03-13 Thread Andi Vajda
On Fri, 13 Mar 2009, Bill Janssen wrote: Christian Heimes wrote: Bill Janssen wrote: I was thinking about this some more, and have an idea. How about only having the dictionary of the module init'ed by calling initVM? That is, it would be practically speaking impossible to call any other

Re: a few issues with 2.4.1 RC3

2009-03-13 Thread Andi Vajda
On Fri, 13 Mar 2009, Michael McCandless wrote: I'm playing with 2.4.1 RC3 (on OS X 10.5.6) and found a few issues: * I'm attempting to re-use a field, by changing its value, and then adding the document to an index: lucene.initVM(lucene.CLASSPATH) writer = lucene.IndexWriter(lu

Re: a few issues with 2.4.1 RC3

2009-03-13 Thread Bill Janssen
Christian Heimes wrote: > Bill Janssen wrote: > > I was thinking about this some more, and have an idea. How about only > > having the dictionary of the module init'ed by calling initVM? That is, > > it would be practically speaking impossible to call any other Java > > method until the VM has

Re: a few issues with 2.4.1 RC3

2009-03-13 Thread Andi Vajda
On Fri, 13 Mar 2009, Michael McCandless wrote: * When I hit an exception in Java, the carryover to Python fails to include the full stack trace (sources & line numbers) from Java, which makes debugging harder. Is that normal? That's right and documented here [1]. Andi.. [1] http://luce

Re: a few issues with 2.4.1 RC3

2009-03-13 Thread Andi Vajda
On Fri, 13 Mar 2009, Christian Heimes wrote: Bill Janssen wrote: I was thinking about this some more, and have an idea. How about only having the dictionary of the module init'ed by calling initVM? That is, it would be practically speaking impossible to call any other Java method until the V

Re: a few issues with 2.4.1 RC3

2009-03-13 Thread Andi Vajda
On Fri, 13 Mar 2009, Bill Janssen wrote: Michael McCandless wrote: I'm playing with 2.4.1 RC3 (on OS X 10.5.6) and found a few issues: * If I fail to call lucene.initVM, I get a rather unfriendly Bus Error. Is it possible (desirable?) to detect this and throw a friendly exception

Re: a few issues with 2.4.1 RC3

2009-03-13 Thread Christian Heimes
Bill Janssen wrote: > I was thinking about this some more, and have an idea. How about only > having the dictionary of the module init'ed by calling initVM? That is, > it would be practically speaking impossible to call any other Java > method until the VM has been initialized and the thread atta

Re: a few issues with 2.4.1 RC3

2009-03-13 Thread Bill Janssen
Michael McCandless wrote: > I'm playing with 2.4.1 RC3 (on OS X 10.5.6) and found a few issues: > > * If I fail to call lucene.initVM, I get a rather unfriendly Bus > Error. Is it possible (desirable?) to detect this and throw a > friendly exception instead? I was thinking about this