[jira] Closed: (LUCENE-581) Index, a new generalization super root

[ http://issues.apache.org/jira/browse/LUCENE-581?page=all ] Hoss Man closed LUCENE-581. --- > Index, a new generalization super root > -- > > Key: LUCENE-581 > URL: http://issues.apache.org/jira/bro

[jira] Resolved: (LUCENE-581) Index, a new generalization super root

[ http://issues.apache.org/jira/browse/LUCENE-581?page=all ] Hoss Man resolved LUCENE-581. - Resolution: Won't Fix resolved per orriginal reporter as part of a larger (seperately tracked) issue > Index, a new generalization super root > -

Re: Gdata - opening/closing index

Now the question is how does the indexer handle this? I could index into a second index while the first index used for searching. That's not necessary. You can open an IndexSearcher for doing searches, and go ahead and add documents directly to the same index. The operations are not exclusive,

Re: Gdata - opening/closing index

I think a lag between adding a new document and being able to find it in a search is acceptable. You could optionally provide better latency for low volume indicies by having a maximumCommitFrequency parameter (say 60 seconds). When the first document is added in a while, a new IndexSearcher can

Re: Gdata - opening/closing index

On 7/23/06, karl wettin <[EMAIL PROTECTED]> wrote: On Sun, 2006-07-23 at 19:10 +0200, Simon Willnauer wrote: > So if I index every change immediately I have to open and close the > index reader and writer all the time. This is not very efficient. How often do you plan to close the readers and w

[att: pmc] [off topic] ezmlm and reply-to

It seems as the list does not change mail header reply-to when set by user, so in many cases I reply to users instead of the list. Perhaps it is an intended feature, a user requesting a reply-all. Personally I find it quite annoying, forcing me to send the message twice. Maybe I should learn to us

Re: Gdata - opening/closing index

On Sun, 2006-07-23 at 19:10 +0200, Simon Willnauer wrote: > So if I index every change immediately I have to open and close the > index reader and writer all the time. This is not very efficient. How often do you plan to close the readers and writers? > Now the question is how does the indexer h

Gdata - opening/closing index

Hello everyone, You might have read some mails about the gdata server and what he does so I assume that you are kind of familar with it. I need to index every change to any entry in any feed to make the modifications searchable. I'm especially worried about updates and inserts. So if I index ever

[jira] Updated: (LUCENE-631) GData Server - Milestone 3 Patch, Bugfixes, Documentation

[ http://issues.apache.org/jira/browse/LUCENE-631?page=all ] Simon Willnauer updated LUCENE-631: --- Attachment: gdata_06_07_23.diff > GData Server - Milestone 3 Patch, Bugfixes, Documentation > - >

[jira] Created: (LUCENE-631) GData Server - Milestone 3 Patch, Bugfixes, Documentation

GData Server - Milestone 3 Patch, Bugfixes, Documentation - Key: LUCENE-631 URL: http://issues.apache.org/jira/browse/LUCENE-631 Project: Lucene - Java Issue Type: New Feature

[jira] Commented: (LUCENE-581) Index, a new generalization super root

[ http://issues.apache.org/jira/browse/LUCENE-581?page=comments#action_12422898 ] Karl Wettin commented on LUCENE-581: This issue can be deleted. It is now a part of issue 550, and have been changed from inheritence to an aggregation (strate

[jira] Updated: (LUCENE-550) InstanciatedIndex - faster but memory consuming index

[ http://issues.apache.org/jira/browse/LUCENE-550?page=all ] Karl Wettin updated LUCENE-550: --- Attachment: lucene2-karl_20060723.tar.gz Updated to match the current svn with Fieldable, et.c. All changes to Lucene core are now gathered in a small patch (de-

Re: ant javacc-QueryParser

Yes, but I always get "Could not create task or type of type: javacc". I use a javacc that I downloaded and installed (i.e. unpacked) manually. Could be anything... :) ant version?! Anyway, I did run the javacc task with a javacc 3.2 version, the generated files don't differ from your commit. So

[jira] Updated: (LUCENE-544) MultiFieldQueryParser field boost multiplier

[ http://issues.apache.org/jira/browse/LUCENE-544?page=all ] Karl Wettin updated LUCENE-544: --- Attachment: MultiFieldQueryParser.java.diff A new patch that does not screw up the formatting and that is up to date with 2.0 > MultiFieldQueryParser field boos

Re: ant javacc-QueryParser

On Sonntag 23 Juli 2006 15:02, Simon Willnauer wrote: > Did you set the property in your common-build.xml? Yes, but I always get "Could not create task or type of type: javacc". I use a javacc that I downloaded and installed (i.e. unpacked) manually. Regards Daniel -- http://www.danielnaber.

Re: ant javacc-QueryParser

I did run the ant task after updating to your changes and I do have a difference between the head and the generated file. But this is also missing in revision < 424708. Index: QueryParser.java === --- QueryParser.java(revision 42

ant javacc-QueryParser

Hi, as I cannot get "ant javacc-QueryParser" working I manually applied the changes from my latest commit to QueryParser.java. The change was very simple so I think this should be okay. Maybe someone can run "ant javacc-QueryParser" just to be sure. Regards Daniel -- http://www.danielnaber.