Re: Continuous Integration for Lucene

: Now Parabuild will re-build Lucene whenever new changes are committed : to the repository and send a message to the dev list if new changes : break the build. Here is the URL: : : http://parabuild.viewtier.com:8080/parabuild/index.htm?displaygroupid=5 Alex: thanks for setting this up. Just so

[jira] Commented: (LUCENE-753) Use NIO positional read to avoid synchronization in FSIndexInput

[ http://issues.apache.org/jira/browse/LUCENE-753?page=comments#action_12459868 ] Bogdan Ghidireac commented on LUCENE-753: - You can find a NIO variation of IndexInput attached to this issue:

Re: Payloads

Hi Michael, Have a look at https://issues.apache.org/jira/browse/LUCENE-662 I am planning on starting on this soon (I know, I have been saying that for a while, but I really am.) At any rate, another set of eyes would be good and I would be interested in hearing how your version

[jira] Commented: (LUCENE-753) Use NIO positional read to avoid synchronization in FSIndexInput

[ http://issues.apache.org/jira/browse/LUCENE-753?page=comments#action_12459967 ] Yonik Seeley commented on LUCENE-753: - Thanks for the pointer Bogdan, it's interesting you use transferTo instead of read... is there any advantage to this?

[jira] Commented: (LUCENE-753) Use NIO positional read to avoid synchronization in FSIndexInput

[ http://issues.apache.org/jira/browse/LUCENE-753?page=comments#action_12459971 ] Bogdan Ghidireac commented on LUCENE-753: - The Javadoc says that transferTo can be more efficient because the OS can transfer bytes directly from the

[jira] Commented: (LUCENE-754) FieldCache keeps hard references to readers, doesn't prevent multiple threads from creating same instance

[ http://issues.apache.org/jira/browse/LUCENE-754?page=comments#action_12459987 ] Otis Gospodnetic commented on LUCENE-754: - Since I was the one who first whined about this leak, I'm just following up to report that this change indeed

Re: Continuous Integration for Lucene

Chris Hostetter wrote: One thing you might want to watch out for, is that your system doesn't seem to run the unit tests, which is an important part of verifying that a build was successful (i notice this only because the trunk was acctually broken recently, yet the logs available on your system

Re: Payloads

Michael Busch wrote: Some weeks ago I started working on an improved design which I would like to propose now. The new design simplifies the API extensions (the Field API remains unchanged) and uses less disk space in most use cases. Now there are only two classes that get new methods: -

[jira] Created: (LUCENE-755) Payloads

Payloads Key: LUCENE-755 URL: http://issues.apache.org/jira/browse/LUCENE-755 Project: Lucene - Java Issue Type: New Feature Components: Index Reporter: Michael Busch Assigned To: Michael Busch This

[jira] Updated: (LUCENE-755) Payloads

[ http://issues.apache.org/jira/browse/LUCENE-755?page=all ] Michael Busch updated LUCENE-755: - Attachment: payloads.patch Payloads Key: LUCENE-755 URL: http://issues.apache.org/jira/browse/LUCENE-755

Re: Payloads

Nicolas Lalevée wrote: Le Mercredi 20 Décembre 2006 15:31, Grant Ingersoll a écrit : Hi Michael, Have a look at https://issues.apache.org/jira/browse/LUCENE-662 I am planning on starting on this soon (I know, I have been saying that for a while, but I really am.) At any rate, another set

Re: Continuous Integration for Lucene

Doug, - Original Message - From: Doug Cutting [EMAIL PROTECTED] To: java-dev@lucene.apache.org Sent: Wednesday, December 20, 2006 9:14 AM Subject: Re: Continuous Integration for Lucene Chris Hostetter wrote: One thing you might want to watch out for, is that your system doesn't seem

Re LUCENE-754

Hi, Am I reading this right? It sounds like you are saying LUCENE-651 did *not* fix the original problem it was supposed to fix, and in addition it introduced a bug that LUCENE-754 fixed. 28. LUCENE-754: Fix a problem introduced by LUCENE-651, causing IndexReaders to hang around forever,

Re: Payloads

Doug Cutting wrote: Michael, This sounds like very good work. The back-compatibility of this approach is great. But we should also consider this in the broader context of index-format flexibility. Three general approaches have been proposed. They are not exclusive. 1. Make the index

Re: Payloads

Michael Busch wrote: the other hand, if people would like to use the payloads soon I guess due to the backwards compatibility it would be low risk to add it to the current index format to provide this feature until we can finish the flexible format? A reason not to commit something like this

[jira] Resolved: (LUCENE-436) [PATCH] TermInfosReader, SegmentTermEnum Out Of Memory Exception

[ http://issues.apache.org/jira/browse/LUCENE-436?page=all ] Otis Gospodnetic resolved LUCENE-436. - Resolution: Fixed Applied and committed the LUCENE-436.patch (is JIRA smart enough not to hyperlink this?) - all unit tests still pass. [PATCH]

[jira] Updated: (LUCENE-724) Oracle JVM implementation for Lucene DataStore also a preliminary implementation for an Oracle Domain index using Lucene

[ http://issues.apache.org/jira/browse/LUCENE-724?page=all ] Marcelo F. Ochoa updated LUCENE-724: Attachment: ojvm-12-20-06.tar.gz This new release of the OJVMDirectory Lucene Store includes a fully functional Oracle Domain Index with a queue for

[jira] Resolved: (LUCENE-741) Field norm modifier (CLI tool)

[ http://issues.apache.org/jira/browse/LUCENE-741?page=all ] Otis Gospodnetic resolved LUCENE-741. - Resolution: Fixed Committed. I'll also remove the old version of this code (+ its unit test), the one that still lives in

Lucene nightly build failure

javacc-uptodate-check: javacc-notice: [echo] [echo] One or more of the JavaCC .jj files is newer than its corresponding [echo] .java file. Run the javacc target to regenerate the artifacts. [echo] init: clover.setup: clover.info: [echo]

Lucene nightly build failure

javacc-uptodate-check: javacc-notice: [echo] [echo] One or more of the JavaCC .jj files is newer than its corresponding [echo] .java file. Run the javacc target to regenerate the artifacts. [echo] init: clover.setup: [mkdir] Created dir:

[jira] Updated: (LUCENE-589) Demo HTML parser doesn't work for international documents

[ http://issues.apache.org/jira/browse/LUCENE-589?page=all ] Grant Ingersoll updated LUCENE-589: --- Issue Type: Improvement (was: Bug) Description: Javacc assumes ASCII so it won't work with, say, japanese documents. Ideally it would read the

[jira] Created: (LUCENE-756) Maintain norms in a single file .nrm

Maintain norms in a single file .nrm Key: LUCENE-756 URL: http://issues.apache.org/jira/browse/LUCENE-756 Project: Lucene - Java Issue Type: Improvement Reporter: Doron Cohen

[jira] Assigned: (LUCENE-756) Maintain norms in a single file .nrm

[ http://issues.apache.org/jira/browse/LUCENE-756?page=all ] Doron Cohen reassigned LUCENE-756: -- Assignee: Doron Cohen Maintain norms in a single file .nrm Key: LUCENE-756 URL:

[jira] Updated: (LUCENE-756) Maintain norms in a single file .nrm

[ http://issues.apache.org/jira/browse/LUCENE-756?page=all ] Doron Cohen updated LUCENE-756: --- Attachment: nrm.patch.txt Attached patch - nrm.patch.txt - modifies field norms maintenance to a single .nrm file. Modification is backwards compatible -

[jira] Assigned: (LUCENE-493) Nightly build archives do not contain Java source code.

[ http://issues.apache.org/jira/browse/LUCENE-493?page=all ] Grant Ingersoll reassigned LUCENE-493: -- Assignee: Grant Ingersoll Nightly build archives do not contain Java source code. ---

[jira] Created: (LUCENE-757) Source packaging fails if ${dist.dir} does not exist

Source packaging fails if ${dist.dir} does not exist Key: LUCENE-757 URL: http://issues.apache.org/jira/browse/LUCENE-757 Project: Lucene - Java Issue Type: Bug Components:

[jira] Updated: (LUCENE-756) Maintain norms in a single file .nrm

[ http://issues.apache.org/jira/browse/LUCENE-756?page=all ] Doron Cohen updated LUCENE-756: --- Lucene Fields: [Patch Available] (was: [New]) Maintain norms in a single file .nrm Key: LUCENE-756

[jira] Commented: (LUCENE-493) Nightly build archives do not contain Java source code.

[ http://issues.apache.org/jira/browse/LUCENE-493?page=comments#action_12460123 ] Grant Ingersoll commented on LUCENE-493: Scratch that comment on tar... Nightly build archives do not contain Java source code.

[jira] Resolved: (LUCENE-654) GData-Server - Website sandbox part

[ http://issues.apache.org/jira/browse/LUCENE-654?page=all ] Grant Ingersoll resolved LUCENE-654. Resolution: Fixed Committed (with some minor updates to the text). Should be sync'd on the website in 30 mins or so. GData-Server - Website sandbox

Re: [jira] Resolved: (LUCENE-654) GData-Server - Website sandbox part

Thank you Grant. :) On 12/20/06, Grant Ingersoll (JIRA) [EMAIL PROTECTED] wrote: [ http://issues.apache.org/jira/browse/LUCENE-654?page=all ] Grant Ingersoll resolved LUCENE-654. Resolution: Fixed Committed (with some minor updates to the text).

[jira] Resolved: (LUCENE-757) Source packaging fails if ${dist.dir} does not exist

[ http://issues.apache.org/jira/browse/LUCENE-757?page=all ] Grant Ingersoll resolved LUCENE-757. Resolution: Fixed Added init-dist target and had package and package-*-src call it so that it always builds the dist dir. Source packaging fails if

[jira] Updated: (LUCENE-493) Nightly build archives do not contain Java source code.

[ http://issues.apache.org/jira/browse/LUCENE-493?page=all ] Grant Ingersoll updated LUCENE-493: --- Priority: Minor (was: Major) Nightly build archives do not contain Java source code. ---

New Issues

+1 for changing the Create New Issue screen in JIRA to have a default priority of Minor instead of Major. Me thinks a fair number of people don't pay attention to the priority, so a lower default would be good for those of us scanning issue lists trying to prioritize. -Grant

[jira] Updated: (LUCENE-756) Maintain norms in a single file .nrm

[ http://issues.apache.org/jira/browse/LUCENE-756?page=all ] Doron Cohen updated LUCENE-756: --- Component/s: Index Maintain norms in a single file .nrm Key: LUCENE-756 URL:

[jira] Updated: (LUCENE-756) Maintain norms in a single file .nrm

[ http://issues.apache.org/jira/browse/LUCENE-756?page=all ] Doron Cohen updated LUCENE-756: --- Attachment: (was: nrm.patch.txt) Maintain norms in a single file .nrm Key: LUCENE-756

[jira] Updated: (LUCENE-756) Maintain norms in a single file .nrm

[ http://issues.apache.org/jira/browse/LUCENE-756?page=all ] Doron Cohen updated LUCENE-756: --- Attachment: nrm.patch.txt Replacing the patch file (prev file was garbage - svn stat instead of svn diff). Few words on how this patch works: - segment.nrm

Re: New Issues

+1 : +1 for changing the Create New Issue screen in JIRA to have a : default priority of Minor instead of Major. Me thinks a fair number -Hoss - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail:

Re: Re LUCENE-754

On 12/20/06, Otis Gospodnetic [EMAIL PROTECTED] wrote: Am I reading this right? It sounds like you are saying LUCENE-651 did *not* fix the original problem it was supposed to fix, and in addition it introduced a bug that LUCENE-754 fixed. Correct. The placeholder was filed under reader but

Re: potential indexing perormance improvement for compound index - cut IO - have more files though

Doron Cohen wrote: Doug Cutting wrote: Therefore, a semi compound segment file can be defined, that would be made of 4 files (instead of 1): - File 0: .fdx .tis .tvx - File 1: .fdt .tii .tvd - File 2: .frq .tvf - File 3: .fnm .prx .fN I think this is a promising direction.