[jira] Commented: (LUCENE-1754) Get rid of NonMatchingScorer from BooleanScorer2

[ https://issues.apache.org/jira/browse/LUCENE-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733145#action_12733145 ] Shai Erera commented on LUCENE-1754: I thought it's going to be easy too soon :). Aft

Re: Relevance's scores on TopFieldCollector/FieldComparator

In our use-case we are not using filterCache and documentCache in our solrconfig.xml because we are interested in the maximum random repetitions. That's the reason to don't use caches. Maybe that was the reason to get 0s in the ScoreCachingWrapper. Michael McCandless-2 wrote: > > It's odd tha

Re: Relevance's scores on TopFieldCollector/FieldComparator

Actually, were you seeing the 0 scores only on boolean queries? If so it could be this bug that you were hitting: https://issues.apache.org/jira/browse/LUCENE-1744 That bug only existed in trunk, and is now fixed. Mike On Mon, Jul 20, 2009 at 4:53 AM, Raimon Bosch wrote: > > > In our use-cas

[jira] Created: (LUCENE-1755) WriteLineDocTask should keep docs w/ just title and no body

WriteLineDocTask should keep docs w/ just title and no body --- Key: LUCENE-1755 URL: https://issues.apache.org/jira/browse/LUCENE-1755 Project: Lucene - Java Issue Type: Bug

[jira] Commented: (LUCENE-1754) Get rid of NonMatchingScorer from BooleanScorer2

[ https://issues.apache.org/jira/browse/LUCENE-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733188#action_12733188 ] Michael McCandless commented on LUCENE-1754: It seems like Weight.scorer() in

Re: Relevance's scores on TopFieldCollector/FieldComparator

Yes, seems this bug. We are using boolean queries. Michael McCandless-2 wrote: > > Actually, were you seeing the 0 scores only on boolean queries? If so > it could be this bug that you were hitting: > > https://issues.apache.org/jira/browse/LUCENE-1744 > > That bug only existed in trunk,

[jira] Updated: (LUCENE-1755) WriteLineDocTask should keep docs w/ just title and no body

[ https://issues.apache.org/jira/browse/LUCENE-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shai Erera updated LUCENE-1755: --- Attachment: LUCENE-1755.patch Fix in WriteLineDocTask + test cases. All Benchmark tests pass. > Wri

[jira] Resolved: (LUCENE-1755) WriteLineDocTask should keep docs w/ just title and no body

[ https://issues.apache.org/jira/browse/LUCENE-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller resolved LUCENE-1755. - Resolution: Fixed Assignee: Mark Miller Thanks Shai! > WriteLineDocTask should keep docs

[jira] Updated: (LUCENE-1754) Get rid of NonMatchingScorer from BooleanScorer2

[ https://issues.apache.org/jira/browse/LUCENE-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shai Erera updated LUCENE-1754: --- Attachment: LUCENE-1754.patch Patch which removes NonMatchingScorer, fixes tests and tag. I also ag

[jira] Updated: (LUCENE-1754) Get rid of NonMatchingScorer from BooleanScorer2

[ https://issues.apache.org/jira/browse/LUCENE-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shai Erera updated LUCENE-1754: --- Description: Over in LUCENE-1614 Mike has made a comment about removing NonMatchinScorer from BS2,

Re: Relevance's scores on TopFieldCollector/FieldComparator

OK, phew :) Mike On Mon, Jul 20, 2009 at 7:27 AM, Raimon Bosch wrote: > > > Yes, seems this bug. We are using boolean queries. > > > Michael McCandless-2 wrote: >> >> Actually, were you seeing the 0 scores only on boolean queries?  If so >> it could be this bug that you were hitting: >> >>   http

[jira] Commented: (LUCENE-1754) Get rid of NonMatchingScorer from BooleanScorer2

[ https://issues.apache.org/jira/browse/LUCENE-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733209#action_12733209 ] Yonik Seeley commented on LUCENE-1754: -- bq. It seems like Weight.scorer() in general

[jira] Commented: (LUCENE-1754) Get rid of NonMatchingScorer from BooleanScorer2

[ https://issues.apache.org/jira/browse/LUCENE-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733213#action_12733213 ] Shai Erera commented on LUCENE-1754: bq. See ConstantScoreQuery.explain() for instance

[jira] Commented: (LUCENE-1690) Morelikethis queries are very slow compared to other search types

[ https://issues.apache.org/jira/browse/LUCENE-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733234#action_12733234 ] Carl Austin commented on LUCENE-1690: - The cache used for this is a HashMap and this i

[jira] Commented: (LUCENE-1690) Morelikethis queries are very slow compared to other search types

[ https://issues.apache.org/jira/browse/LUCENE-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733237#action_12733237 ] Richard Marr commented on LUCENE-1690: -- Okay, so the ideal solution is an LRU cache b

[jira] Commented: (LUCENE-1690) Morelikethis queries are very slow compared to other search types

[ https://issues.apache.org/jira/browse/LUCENE-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733238#action_12733238 ] Carl Austin commented on LUCENE-1690: - I wasn't all that scientific I am afraid, just

[jira] Updated: (LUCENE-1644) Enable MultiTermQuery's constant score mode to also use BooleanQuery under the hood

[ https://issues.apache.org/jira/browse/LUCENE-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-1644: --- Attachment: LUCENE-1644.patch I'd really like to get this one in for 2.9. The API i

[jira] Updated: (LUCENE-1644) Enable MultiTermQuery's constant score mode to also use BooleanQuery under the hood

[ https://issues.apache.org/jira/browse/LUCENE-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-1644: --- Fix Version/s: (was: 3.1) 2.9 > Enable MultiTermQuery's const

[jira] Assigned: (LUCENE-1644) Enable MultiTermQuery's constant score mode to also use BooleanQuery under the hood

[ https://issues.apache.org/jira/browse/LUCENE-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless reassigned LUCENE-1644: -- Assignee: Michael McCandless > Enable MultiTermQuery's constant score mode to

[jira] Assigned: (LUCENE-1754) Get rid of NonMatchingScorer from BooleanScorer2

[ https://issues.apache.org/jira/browse/LUCENE-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless reassigned LUCENE-1754: -- Assignee: Michael McCandless > Get rid of NonMatchingScorer from BooleanScorer

[jira] Commented: (LUCENE-1754) Get rid of NonMatchingScorer from BooleanScorer2

[ https://issues.apache.org/jira/browse/LUCENE-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733315#action_12733315 ] Michael McCandless commented on LUCENE-1754: TermWeight.scorer returns null if

[jira] Commented: (LUCENE-1750) Create a MergePolicy that limits the maximum size of it's segments

[ https://issues.apache.org/jira/browse/LUCENE-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733389#action_12733389 ] Jason Rutherglen commented on LUCENE-1750: -- > Wouldn't you want them to be merged

Re: Throttling merges

Yep, pretty much like "ionice" for Linux. At the Directory level makes the most sense with the context passed in. > then somehow add throttling in there. Yeah I'm not sure how exactly that will work yet. On Sat, Jul 18, 2009 at 9:12 AM, Michael McCandless wrote: > The goal is to be like "ionic

[jira] Commented: (LUCENE-1754) Get rid of NonMatchingScorer from BooleanScorer2

[ https://issues.apache.org/jira/browse/LUCENE-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733402#action_12733402 ] Yonik Seeley commented on LUCENE-1754: -- Still surprising that scorer() can return nul

[jira] Commented: (LUCENE-1644) Enable MultiTermQuery's constant score mode to also use BooleanQuery under the hood

[ https://issues.apache.org/jira/browse/LUCENE-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733445#action_12733445 ] Robert Muir commented on LUCENE-1644: - Mike, one question: couldn't you consider FILTE

[jira] Commented: (LUCENE-1644) Enable MultiTermQuery's constant score mode to also use BooleanQuery under the hood

[ https://issues.apache.org/jira/browse/LUCENE-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733458#action_12733458 ] Mark Miller commented on LUCENE-1644: - Thats originally what I thought this issue was

[jira] Commented: (LUCENE-1754) Get rid of NonMatchingScorer from BooleanScorer2

[ https://issues.apache.org/jira/browse/LUCENE-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733493#action_12733493 ] Shai Erera commented on LUCENE-1754: That's a good point. IndexSearcher does not prote

[jira] Commented: (LUCENE-1750) Create a MergePolicy that limits the maximum size of it's segments

[ https://issues.apache.org/jira/browse/LUCENE-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733498#action_12733498 ] Shai Erera commented on LUCENE-1750: bq.we could add an optimize(long maxSegmentSize)