Re: test-tag does not really test against 2.4, it tests against a branch from trunk on 2008-11-29

On Fri, Jul 3, 2009 at 8:24 AM, Uwe Schindler wrote: > I used another solution, which is still not perfect but better than before. OK I think this is a good solution for now. We'll start a new back-compat branch on 3.0 once it's released... Mike -

[jira] Updated: (LUCENE-1688) Deprecating StopAnalyzer ENGLISH_STOP_WORDS - General replacement with an immutable Set

[ https://issues.apache.org/jira/browse/LUCENE-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated LUCENE-1688: Attachment: LUCENE-1688.patch > Deprecating StopAnalyzer ENGLISH_STOP_WORDS - General replacement

[jira] Resolved: (LUCENE-1599) SpanRegexQuery and SpanNearQuery is not working with MultiSearcher

[ https://issues.apache.org/jira/browse/LUCENE-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller resolved LUCENE-1599. - Resolution: Fixed Lucene Fields: [New, Patch Available] (was: [New]) > SpanRegexQuery an

Fwd: addIndexesNoOptimize

Guys: Any thoughts? Forwarding the question from the users list after not hearing back. Thanks -John -- Forwarded message -- From: John Wang Date: Fri, Jul 3, 2009 at 3:49 PM Subject: addIndexesNoOptimize To: java-u...@lucene.apache.org Hi guys: Running into a que

Re: Fwd: addIndexesNoOptimize

I don't see why we would disallow that. We would prob just want to remove one of the two checks though: if (dups.contains(dirs[i])) throw new IllegalArgumentException("Directory " + dirs[i] + " appears more than once"); -- - Mark http://www.lucidimagination.com John Wang wro

[jira] Commented: (LUCENE-1730) TrecContentSource should use a fixed encoding, rather than system dependent

[ https://issues.apache.org/jira/browse/LUCENE-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727359#action_12727359 ] Shai Erera commented on LUCENE-1730: Any volunteers to help me get it in? I think it's

Re: addIndexesNoOptimize

This was added defensively a while back (can't find the issue right now), because internally IndexWriter now identifies each SegmentInfo as its Directory + segment name. EG the "runningMerges" set makes use of this. If you comment the check out, and pass duplicate segments in, I think at least In

[jira] Updated: (LUCENE-1728) Move SmartChineseAnalyzer & resources to own contrib project

[ https://issues.apache.org/jira/browse/LUCENE-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-1728: Attachment: LUCENE-1728.txt Simon, below is the method I used to do the refactoring with this patc

[jira] Commented: (LUCENE-1373) Most of the contributed Analyzers suffer from invalid recognition of acronyms.

[ https://issues.apache.org/jira/browse/LUCENE-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727390#action_12727390 ] Mark Lassau commented on LUCENE-1373: - @Rob This issue is about how Lucene parses ACR

[jira] Updated: (LUCENE-1567) New flexible query parser

[ https://issues.apache.org/jira/browse/LUCENE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Busch updated LUCENE-1567: -- Attachment: new_query_parser_src.tar MD5 (new_query_parser_src.tar) = b678596e3dea63e8e66e035d

Re: addIndexesNoOptimize

Hi Mark and Michael: Thanks for your replies. Currently, addIndexesNoOptimize(Directory[] dir) is really really really fast! (I duplicated my index of 15k docs 200 times and created a 3M doc index in less than a minute) Perhaps we should handle duplicate directory names more gracefully?