Index Updation Issue

I am using Lucene on both Server Side(Java Web Application) and Client Side(C# Desktop client). Actually Client creates indexes and uploads it to server. And server searches from the index uploaded and shows the results to the user. Now first time all indexes from the files are created and

[jira] Created: (LUCENE-1265) Identify bottleneck associated with not pooling searchers

Identify bottleneck associated with not pooling searchers - Key: LUCENE-1265 URL: https://issues.apache.org/jira/browse/LUCENE-1265 Project: Lucene - Java Issue Type: Task

[jira] Commented: (LUCENE-1265) Identify bottleneck associated with not pooling searchers

[ https://issues.apache.org/jira/browse/LUCENE-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590082#action_12590082 ] Karl Wettin commented on LUCENE-1265: - I'll be looking in to this any year now.

Re: Back Compatibility of Contrib. was Re: [jira] Commented: (LUCENE-1142) Updated Snowball package

: Do we require the contrib to adhere to the same back compatibility rules as : trunk? I don't know that it has been established. Thoughts? Analysis is a : pretty tricky one, as compared to the other packages. we discussed this a little while back and put it on the wiki... All contribs are

Re: Back Compatibility of Contrib. was Re: [jira] Commented: (LUCENE-1142) Updated Snowball package

Chris Hostetter skrev: ...personally i think the analysis contrib should have the same compat reqruitements as the core given how heavily used it is. In this specific case it is possible to introduce the new stemmers via one method and leave the old stemmers accessable using old methods.

Re: Pooling of posting objects in DocumentsWriter

Marvin Humphrey [EMAIL PROTECTED] wrote: On Apr 13, 2008, at 2:28 AM, Michael McCandless wrote: In fact, RawPosting objects aren't even malloc'd individually -- they're assigned memory chunks by a custom MemoryPool object (which *does* have to maintain awareness of alignment issues).

Re: Flexible indexing design

Marvin Humphrey [EMAIL PROTECTED] wrote: On Apr 13, 2008, at 2:35 AM, Michael McCandless wrote: I think the major difference is locality? In a compound file, you have to seek far away to reach the prx skip data (if they are separate). There's another item worth mentioning, something

Re: Index Updation Issue

You should be able to upload only the changed files? Because of how Lucene works, often it's only a few small files that were changed on adding a few docs. Though there are times when many files change because a merge completed. Tools like rsync do this incremental syncing well. Mike

[jira] Commented: (LUCENE-626) Extended spell checker with phrase support and adaptive user session analysis.

[ https://issues.apache.org/jira/browse/LUCENE-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590189#action_12590189 ] Karl Wettin commented on LUCENE-626: If anyone have some rather large query logs with

lucy progress

Hi: What is the current progress on Lucy? Which version of Lucene index format is it up to? Thanks -John

Re: lucy progress

On Apr 17, 2008, at 3:00 PM, John Wang wrote: What is the current progress on Lucy? For various reasons, Dave Balmain has been largely unavailable over the last year. Without my primary co-conspirator, and without a user base, there weren't a lot of people to bounce ideas off of, so I

[jira] Created: (LUCENE-1266) IndexWriter.optimize(boolean doWait) ignores doWait parameter

IndexWriter.optimize(boolean doWait) ignores doWait parameter - Key: LUCENE-1266 URL: https://issues.apache.org/jira/browse/LUCENE-1266 Project: Lucene - Java Issue Type: Bug

[JIRA] Commented: (NXP-2324) Icon of documents created with LiveEdit

[ http://jira.nuxeo.org/browse/NXP-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=35325#action_35325 ] Solen Guitter commented on NXP-2324: On the Summary tab, the attached file has the correct icon however.