[jira] Updated: (LUCENE-1350) Filters which are "consumers" should not reset the payload or flags and should better reuse the token

[ https://issues.apache.org/jira/browse/LUCENE-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doron Cohen updated LUCENE-1350: Description: Passing tokens with payloads through SnowballFilter results in tokens with no payl

Extending TopDocCollector

Hi Is it possible to change TopDocCollector members to 'protected' instead of 'package' and 'private'? It will allow to easily extend it. Today, I have a need to extend it, but since I cannot use its members I have to implement the getTotalHits() and topDocs() exactly the same as TopDocCollector.

Re: lucene scoring

My understanding is this is an area of research in Info. Retrieval in general. There is some attempt at this with the query normalization factor in the scoring model, but my understanding is one shouldn't rely on it. You might try searching Google scholar (or MSN Academic Live, which I pr

[jira] Created: (LUCENE-1352) trailing escaped backslashes in quoted queries cause parse error

trailing escaped backslashes in quoted queries cause parse error Key: LUCENE-1352 URL: https://issues.apache.org/jira/browse/LUCENE-1352 Project: Lucene - Java Issue Type: Bug

[jira] Updated: (LUCENE-1352) trailing escaped backslashes in quoted queries cause parse error

[ https://issues.apache.org/jira/browse/LUCENE-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley updated LUCENE-1352: - Description: {noformat} The QueryParser fails to parse queries that contain escaped backslashes

[jira] Resolved: (LUCENE-1352) trailing escaped backslashes in quoted queries cause parse error

[ https://issues.apache.org/jira/browse/LUCENE-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley resolved LUCENE-1352. -- Resolution: Duplicate Resolving as a duplicate of LUCENE-1189 > trailing escaped backslashes

[jira] Commented: (LUCENE-1335) Correctly handle concurrent calls to addIndexes, optimize, commit

[ https://issues.apache.org/jira/browse/LUCENE-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620713#action_12620713 ] Yonik Seeley commented on LUCENE-1335: -- I've just started reviewing this patch. Since

Re[2]: lucene scoring

I want implement searching with ability to set so-called a confidence level below which I would treat documents as garbage. I cannot defile the level per query as the level should be relevant for all documents. With current scoring implementation the level would mean nothing. I don't believe th

[jira] Commented: (LUCENE-1335) Correctly handle concurrent calls to addIndexes, optimize, commit

[ https://issues.apache.org/jira/browse/LUCENE-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620723#action_12620723 ] Michael McCandless commented on LUCENE-1335: Thanks, Yonik. I'll add a commen

[jira] Updated: (LUCENE-1335) Correctly handle concurrent calls to addIndexes, optimize, commit

[ https://issues.apache.org/jira/browse/LUCENE-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-1335: --- Attachment: LUCENE-1335.patch Improved comments in expungeDeletes & copyExternalSegm

Re: Re[2]: lucene scoring

On Aug 7, 2008, at 3:05 PM, Александр Аристов wrote: I want implement searching with ability to set so-called a confidence level below which I would treat documents as garbage. I cannot defile the level per query as the level should be relevant for all documents. With current scoring imp

Re: lucene scoring

Александр Аристов wrote: I want implement searching with ability to set so-called a confidence level below which I would treat documents as garbage. I cannot defile the level per query as the level should be relevant for all documents. Hmm .. I'm not sure if I understand it properly - if the le