Re: idea for reducing file handle use

Doug Cutting wrote: Dmitry, It would be cleaner if this could be done entirely as a Directory implementation. I know some folks who've implemented a filesystem-within-a-file solution for this problem that they're very happy with. It is a Directory, and requires no changes to Lucene. I'll a

Re: idea for reducing file handle use

Doug Cutting wrote: Dmitry, It would be cleaner if this could be done entirely as a Directory implementation. I know some folks who've implemented a filesystem-within-a-file solution for this problem that they're very happy with. It is a Directory, and requires no changes to Lucene. I'll a

Re: Revival of Dmitry's Term Vector patches

Otis Gospodnetic wrote: Dmitry and others, One of the relatively frequently asked for features is 'conceptual search', or 'search by similarity', etc. Lucene does not store term vectors in its index, so such searches cannot be supported. However, almost two years ago, Dmitry provided a large set

DO NOT REPLY [Bug 19736] - org.apache.lucene.store.FSDirectory#create bug

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 20123] - Add IndexSearcher.close if tag aborts unexpectedly

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 14373] - java.io.IOException on retrieving result

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 12588] - Delete failed after new Term is indexed

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 4568] - new IndexReader.terms(myterm) skips over first term

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug

DO NOT REPLY [Bug 20283] - New tags and functionality for lucene-taglib

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: cvs commit: jakarta-lucene build.xml

Erik Hatcher wrote: By the way, I'm currently getting 4 failures. TestRussionAnalyzer has two: testKOI8 and test1251. These work for me, using either Sun's 1.4.1_02 on Windows XP, or 1.4.2 on RedHat 8. What JVM/OS are you using? TestIndexReader has two: testDeleteReaderWriterConflict and test

Re: idea for reducing file handle use

Dmitry, It would be cleaner if this could be done entirely as a Directory implementation. I know some folks who've implemented a filesystem-within-a-file solution for this problem that they're very happy with. It is a Directory, and requires no changes to Lucene. I'll ask them if they're wi

Revival of Dmitry's Term Vector patches

Dmitry and others, One of the relatively frequently asked for features is 'conceptual search', or 'search by similarity', etc. Lucene does not store term vectors in its index, so such searches cannot be supported. However, almost two years ago, Dmitry provided a large set of patches that added t

Re: idea for reducing file handle use

Hello Dmitry, This would be a nice, juicy contribution. Your outline of the changes sounds good, but unfortunately I do not know how and if this will affect the performance of Lucene. Moreover, we don't even have any tools to measure the performance before and after the changes. :( Regardless,

Re: cvs commit: jakarta-lucene build.xml

+1 to that! That "bin" always bothered me. Otis --- Doug Cutting <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > More build file cleanup - making target names > > more sensible in an effort to start splitting the > > coupling between the demo, tests, and core. Test > > target

Re: cvs commit: jakarta-lucene build.xml

--- Erik Hatcher <[EMAIL PROTECTED]> wrote: > On Thursday, September 18, 2003, at 03:09 PM, Otis Gospodnetic > wrote: > >> Does anyone disagree with my change to make the test target fail > if > >> any of the unit tests fail? (I sure hope not! :) > > > > What does it mean for the test target to

Re: cleanup questions

--- Erik Hatcher <[EMAIL PROTECTED]> wrote: > In my efforts to create a clean demo application I'm doing a thorough > > review of the codebase and directory structure. I'll likely have > more > questions over time, but here are some to get the ball rolling > > - src/test/org/apache/lucene/

Re: cvs commit: jakarta-lucene build.xml

On Thursday, September 18, 2003, at 03:09 PM, Otis Gospodnetic wrote: Does anyone disagree with my change to make the test target fail if any of the unit tests fail? (I sure hope not! :) What does it mean for the test target to fail? Exit and stop executing the remaining tests as soon as one of

Re: cvs commit: jakarta-lucene build.xml

--- Erik Hatcher <[EMAIL PROTECTED]> wrote: > On Thursday, September 18, 2003, at 02:09 PM, [EMAIL PROTECTED] > wrote: > > test failure = build failure. > > Does anyone disagree with my change to make the test target fail if > any of the unit tests fail? (I sure hope not! :) What does it me

Re: cvs commit: jakarta-lucene build.xml

On Thursday, September 18, 2003, at 02:18 PM, Doug Cutting wrote: [EMAIL PROTECTED] wrote: More build file cleanup - making target names more sensible in an effort to start splitting the coupling between the demo, tests, and core. Test target is now "test" ("test-unit" alias remains). Whi

idea for reducing file handle use

Greetings, Luceeners! Looks like lot's of good stuff is happenning with the code as of late. It's great to see this momentum! Here's some more action coming your way... - We all love Lucene, but most would agree that it tends to use a very

Re: cleanup questions

Erik Hatcher wrote: - src/test/org/apache/lucene/IndexTest.java - this is not even a JUnit test case. Does anyone run it? It has a hardcoded path ("F:\test") and some FIXME comments. The code is totally useless except to someone with F:\test and F:\recipes. Any objections to just removing th

cleanup questions

In my efforts to create a clean demo application I'm doing a thorough review of the codebase and directory structure. I'll likely have more questions over time, but here are some to get the ball rolling - src/test/org/apache/lucene/IndexTest.java - this is not even a JUnit test case. Does

Re: cvs commit: jakarta-lucene build.xml

[EMAIL PROTECTED] wrote: More build file cleanup - making target names more sensible in an effort to start splitting the coupling between the demo, tests, and core. Test target is now "test" ("test-unit" alias remains). While you're renaming build-related stuff, I'd vote to rename the buil

Re: cvs commit: jakarta-lucene build.xml

On Thursday, September 18, 2003, at 02:09 PM, [EMAIL PROTECTED] wrote: test failure = build failure. Does anyone disagree with my change to make the test target fail if any of the unit tests fail? (I sure hope not! :) also, added XML test output capture and a standalone generate-test-rep

cvs commit: jakarta-lucene build.xml

ehatcher2003/09/18 11:09:28 Modified:.build.xml Log: test failure = build failure. also, added XML test output capture and a standalone generate-test-reports target to make HTML test results reports. Revision ChangesPath 1.46 +15 -1 jakarta-lucen

cvs commit: jakarta-lucene build.xml

ehatcher2003/09/18 10:42:35 Modified:.build.xml Log: More build file cleanup - making target names more sensible in an effort to start splitting the coupling between the demo, tests, and core. Test target is now "test" ("test-unit" alias remains). Revision Change

cvs commit: jakarta-lucene build.xml

ehatcher2003/09/18 10:19:19 Modified:.build.xml Log: fix manifest generation, which was broken by the previous indentation cleanup Revision ChangesPath 1.44 +26 -16jakarta-lucene/build.xml Index: build.xml ==

cvs commit: jakarta-lucene/metadata - New directory

ehatcher2003/09/18 09:59:04 jakarta-lucene/metadata - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: jakarta-lucene build.xml

ehatcher2003/09/18 09:56:18 Modified:.build.xml Log: Cosmetic - reformatted. I'm embarking on some refactorings to accomodate a snazzy new demo app and wanted to get indentation cleanup committed in one commit so the later meatier commits won't have whitespace diffs

Adding String in a Field

Hi, I am trying to add fields to a document as show below: doc.add(Field.Text(fieldName, newString)); Here fieldName and newString are both strings. I wanted to have the words in newString searchable, ie indexed. Currently, I am using a StringTokenizer to get tokens from the string and addin

cvs commit: jakarta-lucene CHANGES.txt

ehatcher2003/09/18 02:47:06 Modified:.CHANGES.txt Log: Added CachingWrapperFilter to change list Revision ChangesPath 1.51 +4 -2 jakarta-lucene/CHANGES.txt Index: CHANGES.txt === RC

cvs commit: jakarta-lucene/src/java/org/apache/lucene/search Similarity.java

ehatcher2003/09/18 02:26:06 Modified:src/java/org/apache/lucene/search Similarity.java Log: add back javadoc needed import darn IDEA! Revision ChangesPath 1.9 +5 -4 jakarta-lucene/src/java/org/apache/lucene/search/Similarity.java Index: Similarity.java

cvs commit: jakarta-lucene build.xml

ehatcher2003/09/18 02:25:35 Modified:.build.xml Log: allow @todo tags without warnings Revision ChangesPath 1.42 +1 -0 jakarta-lucene/build.xml Index: build.xml === RCS file: /home/