Build failed in Hudson: Lucene-trunk #1003

See Changes: [uschindler] LUCENE-2030: Fix locks in CachingWrapperFilter and CachingSpanFilter (make members private, also synchronize on WeakHashMap build, use new Java5 ReentrantLock) [mikemccand] LUCENE-2045: fix false FN

[jira] Commented: (LUCENE-1458) Further steps towards flexible indexing

[ https://issues.apache.org/jira/browse/LUCENE-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774849#action_12774849 ] Mark Miller commented on LUCENE-1458: - I still get OOM's on the reopen test every so o

Re: Welcome Robert Muir as Lucene Java core committer!

On Nov 7, 2009, at 11:13 PM, Mark Miller wrote: Def was great to hang out with everyone at ApacheCon +1 - Uwe and his "heavy committing" was worth the 6 hour plane ride each way alone. It never gets old - I can now laugh on cue. More beer is owed ;) Yeah, that and Busch's "UnexpectedSu

[jira] Commented: (LUCENE-1458) Further steps towards flexible indexing

[ https://issues.apache.org/jira/browse/LUCENE-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774848#action_12774848 ] Mark Miller commented on LUCENE-1458: - Indeed - the merging has been quite challenging

[jira] Updated: (LUCENE-2046) IndexReader.isCurrent incorrectly returns false after writer.prepareCommit has been called

[ https://issues.apache.org/jira/browse/LUCENE-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-2046: --- Attachment: LUCENE-2046.patch Attached patch. Simple fix. > IndexReader.isCurrent

[jira] Created: (LUCENE-2046) IndexReader.isCurrent incorrectly returns false after writer.prepareCommit has been called

IndexReader.isCurrent incorrectly returns false after writer.prepareCommit has been called -- Key: LUCENE-2046 URL: https://issues.apache.org/jira/browse/LUCENE-2046

[jira] Resolved: (LUCENE-2030) CachingSpanFilter synchronizing on a none final protected object

[ https://issues.apache.org/jira/browse/LUCENE-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler resolved LUCENE-2030. --- Resolution: Fixed Fix Version/s: (was: 3.1) 3.0 Committed revi

[jira] Issue Comment Edited: (LUCENE-2034) Massive Code Duplication in Contrib Analyzers - unifly the analyzer ctors

[ https://issues.apache.org/jira/browse/LUCENE-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774816#action_12774816 ] Robert Muir edited comment on LUCENE-2034 at 11/8/09 8:29 PM: --

[jira] Commented: (LUCENE-2034) Massive Code Duplication in Contrib Analyzers - unifly the analyzer ctors

[ https://issues.apache.org/jira/browse/LUCENE-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774816#action_12774816 ] Robert Muir commented on LUCENE-2034: - Simon, i started looking at this, the testStemE

Re: [jira] Updated: (LUCENE-2030) CachingSpanFilter synchronizing on a none final protected object

Uwe, happy that you found a nice way to do it! Java 5 concurrent is gonna be use in a whole lot of places I guess. Simon On Nov 8, 2009 8:07 PM, "Uwe Schindler (JIRA)" wrote: [ https://issues.apache.org/jira/browse/LUCENE-2030?page=com.atlassian.jira.plugin.system.issu. .. New patch that uses R

[jira] Updated: (LUCENE-2030) CachingSpanFilter synchronizing on a none final protected object

[ https://issues.apache.org/jira/browse/LUCENE-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-2030: -- Attachment: LUCENE-2030.patch New patch that uses ReentrantLock from Java5's concurrent packag

Re: A report for "Not so important (but still is a) bug"

Oh ... I missed 2.9.1? sigh Thanks Mike Shai On Sun, Nov 8, 2009 at 7:46 PM, Michael McCandless < luc...@mikemccandless.com> wrote: > I sure hope not :) I hope 3.0 is out soonish... > > But just in case, I've reopened & marked fix version 2.9.2, so if we > ever do a 2.9.2 that'll remind me to

[jira] Commented: (LUCENE-2012) Add @Override annotations

[ https://issues.apache.org/jira/browse/LUCENE-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774805#action_12774805 ] Uwe Schindler commented on LUCENE-2012: --- Yes, that was exactly the problem, but it i

[jira] Commented: (LUCENE-2012) Add @Override annotations

[ https://issues.apache.org/jira/browse/LUCENE-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774799#action_12774799 ] Robert Muir commented on LUCENE-2012: - Uwe, just curious if you had this problem? when

[jira] Updated: (LUCENE-2045) FNFE hit when creating an empty index and infoStream is on

[ https://issues.apache.org/jira/browse/LUCENE-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-2045: --- Fix Version/s: 2.9.2 > FNFE hit when creating an empty index and infoStream is on >

Re: A report for "Not so important (but still is a) bug"

I sure hope not :) I hope 3.0 is out soonish... But just in case, I've reopened & marked fix version 2.9.2, so if we ever do a 2.9.2 that'll remind me to backport. Mike On Sun, Nov 8, 2009 at 11:18 AM, Simon Willnauer wrote: > dude, will we have 2.9.2? :) > > simon > > On Sun, Nov 8, 2009 at 4

[jira] Reopened: (LUCENE-2045) FNFE hit when creating an empty index and infoStream is on

[ https://issues.apache.org/jira/browse/LUCENE-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless reopened LUCENE-2045: Reopening for possible future 2.9.2 backport. > FNFE hit when creating an empty index

Re: AW: Hudson build is back to normal: Lucene-trunk #1002

On Nov 8, 2009, at 5:10, "Uwe Schindler" wrote: Juhu! Heavy commiting made it at least. I am back in Bremen now. It was a pleasure to meet you all @ ApacheCon! Likewise ! Andi.. Uwe Mit einem Mobiltelefon von Sony Ericsson gesendet Originalnachricht Von: Apache Hudson Serve

[jira] Commented: (LUCENE-2012) Add @Override annotations

[ https://issues.apache.org/jira/browse/LUCENE-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774797#action_12774797 ] Uwe Schindler commented on LUCENE-2012: --- Thanks Robert! I was in plane and wasn't ab

Re: A report for "Not so important (but still is a) bug"

dude, will we have 2.9.2? :) simon On Sun, Nov 8, 2009 at 4:14 PM, Michael McCandless wrote: > We should fix this; I'll open an issue & dig. > > Somehow SegmentInfo.files() is being buggy, claiming _0.prx is a file > belonging to the segment, when it clearly isn't. > > BTW we can't hold 2.9.1, s

Re: Omit positions but not TF

Michael McCandless wrote: +1 I guess we'd add a Fieldable.setOmitPositions? And then save that in FieldInfos, and fix the postings writing/reading to respect it? Ie, we can just change the index format. Encoding as negative numbers Yes, that's what I had in mind. I was a bit shy of bumping

[jira] Commented: (LUCENE-1458) Further steps towards flexible indexing

[ https://issues.apache.org/jira/browse/LUCENE-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774787#action_12774787 ] Michael McCandless commented on LUCENE-1458: Yikes! That sounds challenging.

[jira] Commented: (LUCENE-1458) Further steps towards flexible indexing

[ https://issues.apache.org/jira/browse/LUCENE-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774785#action_12774785 ] Mark Miller commented on LUCENE-1458: - I'll merge up when I figure out how - merge do

[jira] Resolved: (LUCENE-2045) FNFE hit when creating an empty index and infoStream is on

[ https://issues.apache.org/jira/browse/LUCENE-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-2045. Resolution: Fixed Thanks Shai! > FNFE hit when creating an empty index and infoSt

[jira] Created: (LUCENE-2045) FNFE hit when creating an empty index and infoStream is on

FNFE hit when creating an empty index and infoStream is on -- Key: LUCENE-2045 URL: https://issues.apache.org/jira/browse/LUCENE-2045 Project: Lucene - Java Issue Type: Bug Co

Re: A report for "Not so important (but still is a) bug"

We should fix this; I'll open an issue & dig. Somehow SegmentInfo.files() is being buggy, claiming _0.prx is a file belonging to the segment, when it clearly isn't. BTW we can't hold 2.9.1, since it's now "out" (as of yesterday) :) Mike On Sun, Nov 8, 2009 at 8:58 AM, Shai Erera wrote: > Hi >

A report for "Not so important (but still is a) bug"

Hi I wanted to check something and wrote this very simple program, which surprisingly failed because of a FileNotFound exception: Directory dir = new RAMDirectory(); IndexWriter writer = new IndexWriter(dir, new SimpleAnalyzer(), MaxFieldLength.UNLIMITED); writer.setInfoStream(S

Re: AW: Hudson build is back to normal: Lucene-trunk #1002

Dito! Apparently robert is on heavy committing now ;) On Nov 8, 2009 2:14 PM, "Uwe Schindler" wrote: Juhu! Heavy commiting made it at least. I am back in Bremen now. It was a pleasure to meet you all @ ApacheCon! Uwe Mit einem Mobiltelefon von Sony Ericsson gesendet Originalnachricht --

[jira] Commented: (LUCENE-1458) Further steps towards flexible indexing

[ https://issues.apache.org/jira/browse/LUCENE-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774768#action_12774768 ] Michael McCandless commented on LUCENE-1458: OK new numbers after the above co

AW: Hudson build is back to normal: Lucene-trunk # 1002

Juhu! Heavy commiting made it at least. I am back in Bremen now. It was a pleasure to meet you all @ ApacheCon! Uwe Mit einem Mobiltelefon von Sony Ericsson gesendet Originalnachricht Von: Apache Hudson Server Gesendet: An: java-dev@lucene.apache.org Betreff: Hudson build is back t

[jira] Commented: (LUCENE-1458) Further steps towards flexible indexing

[ https://issues.apache.org/jira/browse/LUCENE-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774767#action_12774767 ] Michael McCandless commented on LUCENE-1458: Committed fixes addressing silly

[jira] Resolved: (LUCENE-2012) Add @Override annotations

[ https://issues.apache.org/jira/browse/LUCENE-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir resolved LUCENE-2012. - Resolution: Fixed Assignee: Uwe Schindler Committed revision 833867. (contrib, contrib tes

[jira] Updated: (LUCENE-2012) Add @Override annotations

[ https://issues.apache.org/jira/browse/LUCENE-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-2012: Attachment: LUCENE-2012_contrib.patch there were some places where @override was added for generat

[jira] Resolved: (LUCENE-2044) Allow random seed to be set in DeleteByPercentTask

[ https://issues.apache.org/jira/browse/LUCENE-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-2044. Resolution: Fixed > Allow random seed to be set in DeleteByPercentTask > -

[jira] Updated: (LUCENE-2044) Allow random seed to be set in DeleteByPercentTask

[ https://issues.apache.org/jira/browse/LUCENE-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-2044: --- Attachment: LUCENE-2044.patch Trivial fix, adds delete.percent.rand.seed config opti

[jira] Created: (LUCENE-2044) Allow random seed to be set in DeleteByPercentTask

Allow random seed to be set in DeleteByPercentTask -- Key: LUCENE-2044 URL: https://issues.apache.org/jira/browse/LUCENE-2044 Project: Lucene - Java Issue Type: Improvement Components

[jira] Updated: (LUCENE-2012) Add @Override annotations

[ https://issues.apache.org/jira/browse/LUCENE-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-2012: Attachment: LUCENE-2012_contrib.patch Uwe attached is a patch for contrib and its tests. > Add

Re: Omit positions but not TF

+1 I guess we'd add a Fieldable.setOmitPositions? And then save that in FieldInfos, and fix the postings writing/reading to respect it? Ie, we can just change the index format. Encoding as negative numbers isn't great because the termFreq is written as a vInt, which consumes 5 bytes to encode a

[jira] Updated: (LUCENE-2023) Improve performance of SmartChineseAnalyzer

[ https://issues.apache.org/jira/browse/LUCENE-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-2023: Fix Version/s: (was: 3.0) 3.1 if no one objects I'd rather work this into 3

[jira] Commented: (LUCENE-1526) For near real-time search, use paged copy-on-write BitVector impl

[ https://issues.apache.org/jira/browse/LUCENE-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774743#action_12774743 ] John Wang commented on LUCENE-1526: --- Michael: I think I confused you by not giving