See http://hudson.zones.apache.org/hudson/job/Lucene-trunk/416/changes
Changes:
[mikemccand] LUCENE-1244: don't use hard-coded path in AnalysisTest
--
[...truncated 13597 lines...]
[junit] Testsuite: org.apache.lucene.queryParser.TestMultiAnalyzer
MultiFieldQueryParser is not friendly for overriding
Key: LUCENE-1245
URL: https://issues.apache.org/jira/browse/LUCENE-1245
Project: Lucene - Java
Issue Type: Improvement
Compon
[
https://issues.apache.org/jira/browse/LUCENE-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic updated LUCENE-400:
Assignee: Grant Ingersoll (was: Otis Gospodnetic)
Sorry for hogging. Got some local compi
[
https://issues.apache.org/jira/browse/LUCENE-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Elschot updated LUCENE-1187:
-
Attachment: Contrib20080325.patch
The Contrib20080325 also includes Mark Miller's test patch, an
[
https://issues.apache.org/jira/browse/LUCENE-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582063#action_12582063
]
Paul Elschot commented on LUCENE-1187:
--
All tests pass, except the one for ChainedFil
[
https://issues.apache.org/jira/browse/LUCENE-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Elschot updated LUCENE-1187:
-
Attachment: BooleanFilter20080325.patch
BooleanFilter20080325.patch contains a non BitSet versio
: Subject: IndexWriter.flush dose not flush the segmentInfos in Lucene 2.3
: Message-ID: <[EMAIL PROTECTED]>
: In-Reply-To: <[EMAIL PROTECTED]>
http://people.apache.org/~hossman/#threadhijack
Thread Hijacking on Mailing Lists
When starting a new discussion on a mailing list, please do not reply
Hindsight is great !
I am not saying anything was done wrong. I just think the projects
that recognize where the API can be improved and do so in a later
release - when they've had the hindsight - do better long-term.
With decorator and facade classes you may still not get 100% code
compa
robert engels wrote:
Some would argue that all that Field needs is
FieldData getField(String name); and void setField(String name,FieldData
data);
and FieldData has
toBytes(); fromBytes()
Isn't hindsight wonderful!
Writing custom versions of IndexReader and IndexWriter was very
difficult
[
https://issues.apache.org/jira/browse/LUCENE-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Peuss updated LUCENE-1166:
-
Attachment: CompoundTokenFilter.patch
Dropped Java5 dependencies.
> A tokenfilter to decompose
[
https://issues.apache.org/jira/browse/LUCENE-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Peuss updated LUCENE-1166:
-
Attachment: (was: CompoundTokenFilter.patch)
> A tokenfilter to decompose compound words
> -
[
https://issues.apache.org/jira/browse/LUCENE-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Peuss updated LUCENE-1166:
-
Attachment: CompoundTokenFilter.patch
Moved compound word token filter to contrib.
> A tokenfil
[
https://issues.apache.org/jira/browse/LUCENE-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Peuss updated LUCENE-1166:
-
Attachment: CompoundTokenFilter.patch
Moved the compound word tokenfilter stuff to contrib.
> A
[
https://issues.apache.org/jira/browse/LUCENE-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581887#action_12581887
]
Hiroaki Kawai commented on LUCENE-1241:
---
{quote}
OK how about a separate issue for C
[
https://issues.apache.org/jira/browse/LUCENE-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581884#action_12581884
]
Michael McCandless commented on LUCENE-1241:
OK how about a separate issue for
[
https://issues.apache.org/jira/browse/LUCENE-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581860#action_12581860
]
Hiroaki Kawai commented on LUCENE-1241:
---
{quote}
This looks neat, but, can you pull
Ahhh, OK. In 2.3, when you open IndexWriter with autoCommit=false,
the only way to make changes visible is to close the writer. Can you
just open with autoCommit=true? Then flush() makes changes visible.
You can increase the flushing criteria to absurdly large values so
the writer nev
I used the new released 2.3 and set autoCommit=false.
Sorry my code to create the IndexWriter is like this:
Directory dir = FSDirectory.getDirectory(INDEX_DIR);
IndexWriter writer = new IndexWriter(dir, false, new
StandardAnalyzer(), true);
writer.setTerm
[
https://issues.apache.org/jira/browse/LUCENE-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581844#action_12581844
]
Michael McCandless commented on LUCENE-1241:
{quote}
Reading commit log in svn
[
https://issues.apache.org/jira/browse/LUCENE-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581843#action_12581843
]
Michael McCandless commented on LUCENE-1241:
{quote}
I think we should not use
Do you mean 2.4 (trunk) not 2.3? In 2.4, flush has been deprecated.
Instead, you should use commit() to force the changes to be visible
to a reader.
On 2.3 I believe this works correctly as long as the write is opened
with autoCommit=true (which your example below is).
Mike
[EMAIL PR
I found that for lucene 2.3, IndexWriter.flush does not flush the segmentInfos.
For example, I create a new index directory and add 10 documents to it:
IndexWriter writer = new IndexWriter(dir, new StandardAnalyzer(), true);
indexDocs(writer, SOURCE_DIR);//in the source directory,
[
https://issues.apache.org/jira/browse/LUCENE-1244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1244.
Resolution: Fixed
Fix Version/s: 2.4
I just committed this. Thanks Hasan!
23 matches
Mail list logo
