hey folks,
with lucene 4 we got tons of new file formats which are different from
what we have in our fire format specification. This is going to be
worse once we add more codecs like PFOR etc. However updating the docs
manually is going to be very error prone so I wonder if somebody has
any idea
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/10729/
2 tests failed.
REGRESSION: org.apache.lucene.search.TestSimpleExplanations.testDMQ6
Error Message:
((-field:yy field:w3) | field:xx)~0.5: score(doc=0)=-4.4703484E-8 !=
explanationScore=-2.2351742E-8 Explanation:
On 04/10/2011 08:16, Simon Willnauer wrote:
hey folks,
with lucene 4 we got tons of new file formats which are different from
what we have in our fire format specification. This is going to be
worse once we add more codecs like PFOR etc. However updating the docs
manually is going to be very
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/10730/
2 tests failed.
FAILED: org.apache.lucene.search.TestSimpleExplanations.testDMQ7
Error Message:
((-field:yy field:w3) | field:w2)~0.5: score(doc=0)=-6.3329935E-8 !=
explanationScore=-4.221996E-8 Explanation: -4.221996E-8
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/10732/
2 tests failed.
REGRESSION: org.apache.lucene.search.TestSimpleExplanations.testDMQ6
Error Message:
((-field:yy field:w3) | field:xx)~0.5: score(doc=0)=-4.221996E-8 !=
explanationScore=-2.110998E-8 Explanation:
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk-java7/561/
1 tests failed.
REGRESSION: org.apache.solr.update.AutoCommitTest.testSoftAndHardCommitMaxTime
Error Message:
should not be there yet query failed XPath: //result[@numFound=0] xml response
was: ?xml version=1.0
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/10733/
2 tests failed.
FAILED: org.apache.lucene.search.TestSimpleExplanations.testDMQ7
Error Message:
((-field:yy field:w3) | field:w2)~0.5: score(doc=0)=-6.3329935E-8 !=
explanationScore=-4.221996E-8 Explanation: -4.221996E-8
[
https://issues.apache.org/jira/browse/LUCENE-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-3433:
Attachment: LUCENE-3433.patch
I looked at the code and figured that there is actually not
Can we stop trying to document the file format?
Is it really needed? It has been an error-proned process over time...
Can't the source code be the definitive resource one reads to
determine how a codec stores stuff?
Mike McCandless
http://blog.mikemccandless.com
On Tue, Oct 4, 2011 at
[
https://issues.apache.org/jira/browse/LUCENE-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Cohen reassigned LUCENE-3262:
---
Assignee: Doron Cohen
Facet benchmarking
--
Key:
On 04/10/2011 12:44, Michael McCandless wrote:
Can we stop trying to document the file format?
Is it really needed? It has been an error-proned process over time...
Can't the source code be the definitive resource one reads to
determine how a codec stores stuff?
I'm more or less
[
https://issues.apache.org/jira/browse/LUCENE-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120003#comment-13120003
]
Doron Cohen commented on LUCENE-3262:
-
I am working on a patch for this, much in the
[
https://issues.apache.org/jira/browse/LUCENE-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120014#comment-13120014
]
Uwe Schindler commented on LUCENE-3464:
---
This sophisticated backwards seems fine.
[
https://issues.apache.org/jira/browse/LUCENE-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120014#comment-13120014
]
Uwe Schindler edited comment on LUCENE-3464 at 10/4/11 11:17 AM:
On Tue, Oct 4, 2011 at 6:44 AM, Michael McCandless
luc...@mikemccandless.com wrote:
Can we stop trying to document the file format?
Is it really needed? It has been an error-proned process over time...
Can't the source code be the definitive resource one reads to
determine how a codec
[
https://issues.apache.org/jira/browse/SOLR-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120033#comment-13120033
]
Yonik Seeley commented on SOLR-2807:
+1 for upgrading, and hopefully it fixes SOLR-2424
I have several different types of documents in solr and I want the fieldNorm
score to be different based on the document.
Specifically docs of type User always get a fieldNorm score of 1 while
everything else gets their normal score. I've figured out how to globally
change the fieldNorm score by
On Tue, Oct 4, 2011 at 8:31 AM, Jason Toy jason...@gmail.com wrote:
I have several different types of documents in solr and I want the fieldNorm
score to be different based on the document.
Specifically docs of type User always get a fieldNorm score of 1 while
everything else gets their normal
I have custom scoring written for certain docs. Since the scoring uses a
combination of FieldNorm, td, idf, and other factors, I've modified some of
those values to fit my scoring needs. The last issue I have now is that I'm
not sure how to turn this on for the one doc type where this matters,
[
https://issues.apache.org/jira/browse/LUCENE-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120042#comment-13120042
]
Erick Erickson commented on LUCENE-2091:
Should this be closed as duplicate of
On Tue, Oct 4, 2011 at 8:27 AM, Robert Muir rcm...@gmail.com wrote:
On Tue, Oct 4, 2011 at 6:44 AM, Michael McCandless
luc...@mikemccandless.com wrote:
Can we stop trying to document the file format?
Is it really needed? It has been an error-proned process over time...
Can't the source
TaxonomyWriter parents array creation is not thread safe, can cause NPE
---
Key: LUCENE-3484
URL: https://issues.apache.org/jira/browse/LUCENE-3484
Project: Lucene - Java
On Tue, Oct 4, 2011 at 8:46 AM, Jason Toy jason...@gmail.com wrote:
I have custom scoring written for certain docs. Since the scoring uses a
combination of FieldNorm, td, idf, and other factors, I've modified some of
those values to fit my scoring needs. The last issue I have now is that I'm
[
https://issues.apache.org/jira/browse/LUCENE-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Cohen updated LUCENE-3484:
Attachment: LUCENE-3484.patch
Patch with test that fails same as the reported error.
None of the
On Tue, Oct 4, 2011 at 8:27 AM, Robert Muir rcm...@gmail.com wrote:
On Tue, Oct 4, 2011 at 6:44 AM, Michael McCandless
luc...@mikemccandless.com wrote:
Can we stop trying to document the file format?
Is it really needed? It has been an error-proned process over time...
Can't the source
[
https://issues.apache.org/jira/browse/SOLR-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120051#comment-13120051
]
Joan Codina commented on SOLR-2440:
---
I did some further changes.
A Filter query can be
[
https://issues.apache.org/jira/browse/LUCENE-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120049#comment-13120049
]
sebastian L. commented on LUCENE-3440:
--
Another patch for 4.0. This one makes
[
https://issues.apache.org/jira/browse/LUCENE-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sebastian L. updated LUCENE-3440:
-
Attachment: LUCENE-4.0-SNAPSHOT-3440-7.patch
Patch for trunk (1177996)
[
https://issues.apache.org/jira/browse/SOLR-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joan Codina updated SOLR-2440:
--
Attachment: LUCENE_4_schema_jsp.patch
This patch includes neww functionality and is adapted to lucene
[
https://issues.apache.org/jira/browse/SOLR-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120056#comment-13120056
]
Joan Codina commented on SOLR-2440:
---
the new interface is nice (well some colors have too
[
https://issues.apache.org/jira/browse/LUCENE-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sebastian L. updated LUCENE-3440:
-
Attachment: (was: WeightOrderFragmentsBuilder_table01.html)
FastVectorHighlighter:
[
https://issues.apache.org/jira/browse/LUCENE-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sebastian L. updated LUCENE-3440:
-
Attachment: weight-vs-boost_table01.html
FastVectorHighlighter: IDF-weighted terms for
[
https://issues.apache.org/jira/browse/LUCENE-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sebastian L. updated LUCENE-3440:
-
Attachment: (was: WeightOrderFragmentsBuilder_table02.html)
FastVectorHighlighter:
[
https://issues.apache.org/jira/browse/LUCENE-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sebastian L. updated LUCENE-3440:
-
Attachment: weight-vs-boost_table02.html
FastVectorHighlighter: IDF-weighted terms for
[
https://issues.apache.org/jira/browse/LUCENE-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sebastian L. updated LUCENE-3440:
-
Attachment: (was: LUCENE-3.5-SNAPSHOT-3440-6.patch)
FastVectorHighlighter:
[
https://issues.apache.org/jira/browse/LUCENE-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sebastian L. updated LUCENE-3440:
-
Attachment: (was: LUCENE-4.0-SNAPSHOT-3440-6.patch)
FastVectorHighlighter:
Robert,
I think we might have a miscommunication. The docs that require custom
sorting , of TYPE_ID = 1, never sort against other types of docs. They are
always only sorted between other docs of TYPE_ID = 1. I still need custom
scoring because for this particular doc type though to get the
On Tue, Oct 4, 2011 at 9:28 AM, Jason Toy jason...@gmail.com wrote:
Robert,
I think we might have a miscommunication. The docs that require custom
sorting , of TYPE_ID = 1, never sort against other types of docs. They are
always only sorted between other docs of TYPE_ID = 1. I still need
LuceneTaxonomyReader .decRef() may close the inner IR, renderring the LTR in a
limbo.
-
Key: LUCENE-3485
URL: https://issues.apache.org/jira/browse/LUCENE-3485
Node Recovery
-
Key: SOLR-2808
URL: https://issues.apache.org/jira/browse/SOLR-2808
Project: Solr
Issue Type: Sub-task
Components: SolrCloud
Reporter: Yonik Seeley
Node recovery encompasses everything
On Tue, Oct 04, 2011 at 09:06:18AM -0400, Yonik Seeley wrote:
I don't think we necessarily need a description where every bit must
match (i.e. the goal should be general documentation for
understanding, not specification for implementing).
+1
The file format documentation is not a spec. If
Robert, excellent, I didn't know of the omitNorms functionality before, my
schema is already set up like this. I think I still need to use my custom
scorer though because I've also modified the idf score.
Thanks,
Jason
On Tue, Oct 4, 2011 at 9:31 AM, Robert Muir rcm...@gmail.com wrote:
On
On Tue, Oct 4, 2011 at 9:41 AM, Jason Toy jason...@gmail.com wrote:
Robert, excellent, I didn't know of the omitNorms functionality before, my
schema is already set up like this. I think I still need to use my custom
scorer though because I've also modified the idf score.
if you use trunk,
Robert, very helpful, I am referencing this ticket to learn about the
functionality: https://issues.apache.org/jira/browse/SOLR-2338
thanks again!
On Tue, Oct 4, 2011 at 1:44 PM, Robert Muir rcm...@gmail.com wrote:
On Tue, Oct 4, 2011 at 9:41 AM, Jason Toy jason...@gmail.com wrote:
Robert,
[
https://issues.apache.org/jira/browse/LUCENE-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120143#comment-13120143
]
Koji Sekiguchi commented on LUCENE-3440:
Hi sebastian, thank you for the
[
https://issues.apache.org/jira/browse/SOLR-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120151#comment-13120151
]
Yonik Seeley commented on SOLR-2808:
When a node comes up, it starts in recovering
This is not a sim issue, its a problem with the explain() impl in some
query (disjunction max or bq).
The test is asking for trouble by boosting a document with a boost of
'0' which makes it look like an infinitely long document, returning a
tiny tiny score (in my opinion this similarity is
+1 for B.
Some of these explanation test queries are insane.
On Wed, Oct 5, 2011 at 3:19 AM, Robert Muir rcm...@gmail.com wrote:
This is not a sim issue, its a problem with the explain() impl in some
query (disjunction max or bq).
The test is asking for trouble by boosting a document with a
searcher leases
---
Key: SOLR-2809
URL: https://issues.apache.org/jira/browse/SOLR-2809
Project: Solr
Issue Type: New Feature
Reporter: Yonik Seeley
Leases/reservations on searcher instances would give us the
the disadvantage is it sucks to lose test coverage in case someone
boosts a document by zero (we do nothing to prevent someone from doing
such a thing).
again this sim is well-behaved here, its explain is always EXACTLY
what the score returns, you can even add this assert to IBSimilarity:
assert
On Tue, Oct 4, 2011 at 10:33 AM, Andrzej Bialecki a...@getopt.org wrote:
So far the list of possible file names was relatively small and well-known,
e.g. people knew that a prx file contained postings, and its size would
indicate this or that. We are going to have dozens of codecs soon, and if
[
https://issues.apache.org/jira/browse/SOLR-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120164#comment-13120164
]
Andrzej Bialecki commented on SOLR-2809:
-
Multiple leases could lead to searchers
[
https://issues.apache.org/jira/browse/LUCENE-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120053#comment-13120053
]
sebastian L. edited comment on LUCENE-3440 at 10/4/11 2:38 PM:
[
https://issues.apache.org/jira/browse/LUCENE-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sebastian L. updated LUCENE-3440:
-
Attachment: LUCENE-3.5-SNAPSHOT-3440-7.patch
Patch for branch_3x (1177996).
On Wed, Oct 5, 2011 at 3:33 AM, Robert Muir rcm...@gmail.com wrote:
the disadvantage is it sucks to lose test coverage in case someone
boosts a document by zero (we do nothing to prevent someone from doing
such a thing).
again this sim is well-behaved here, its explain is always EXACTLY
[
https://issues.apache.org/jira/browse/SOLR-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120169#comment-13120169
]
Robert Muir commented on SOLR-2809:
---
but fail+retry could lead to slow queries piling up?
On Tue, Oct 4, 2011 at 10:41 AM, Chris Male gento...@gmail.com wrote:
This last option sounds much better I think. I still don't especially like
that we have to deal with boosting by 0, but it'd be a huge pain to prevent.
I committed this for now (and tried a couple of these failing seeds
[
https://issues.apache.org/jira/browse/SOLR-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120185#comment-13120185
]
Yonik Seeley commented on SOLR-2809:
bq. Multiple leases could lead to searchers piling
[
https://issues.apache.org/jira/browse/SOLR-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120187#comment-13120187
]
Jason Rutherglen commented on SOLR-2809:
In RT the searchers are cheap. The
[
https://issues.apache.org/jira/browse/SOLR-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120189#comment-13120189
]
Jason Rutherglen commented on SOLR-2595:
How will splitting occur on an index that
I personally find the file format documentation useful. I want to understand
more than just the rough purpose of the file. If we don't document anywhere
how is the file written, exactly, how can someone ever come up with a
proposal for improvement?
I understand though that maintaining it
[
https://issues.apache.org/jira/browse/SOLR-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120193#comment-13120193
]
Yonik Seeley commented on SOLR-2809:
Distributed search already ensures that different
[
https://issues.apache.org/jira/browse/SOLR-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120196#comment-13120196
]
Robert Muir commented on SOLR-2809:
---
{quote}
The retry would only be necessary in the
[
https://issues.apache.org/jira/browse/SOLR-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120211#comment-13120211
]
Jason Rutherglen commented on SOLR-2809:
{quote}
if we support distributed stats
On 04/10/2011 16:37, Robert Muir wrote:
On Tue, Oct 4, 2011 at 10:33 AM, Andrzej Bialeckia...@getopt.org wrote:
So far the list of possible file names was relatively small and well-known,
e.g. people knew that a prx file contained postings, and its size would
indicate this or that. We are
[
https://issues.apache.org/jira/browse/SOLR-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120213#comment-13120213
]
Robert Muir commented on SOLR-2809:
---
{quote}
Sounds like you're thinking of a general
On Tue, Oct 4, 2011 at 11:23 AM, Andrzej Bialecki a...@getopt.org wrote:
I think that's ok as long as I can say that a .frq file could plausibly end
up in my Directory because it's documented to belong to a codec I was using.
(And also maybe we shouldn't insist on using the same extensions
[
https://issues.apache.org/jira/browse/SOLR-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120217#comment-13120217
]
Jason Rutherglen commented on SOLR-2809:
{quote}no need to modify any of the guts
[
https://issues.apache.org/jira/browse/SOLR-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120218#comment-13120218
]
Yonik Seeley commented on SOLR-2809:
bq. We just need a SolrQueryRequest.getSearcher()
[
https://issues.apache.org/jira/browse/SOLR-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120220#comment-13120220
]
Jan Høydahl commented on SOLR-2372:
---
Will commit Tika 0.10 with these jar changes:
{code}
[
https://issues.apache.org/jira/browse/SOLR-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120223#comment-13120223
]
Jason Rutherglen commented on SOLR-2809:
SOLR-2778 is the issue that seeks to clean
LBHttpSolrServer should be configurable to remove servers on some HTTP errors
-
Key: SOLR-2810
URL: https://issues.apache.org/jira/browse/SOLR-2810
Project: Solr
[
https://issues.apache.org/jira/browse/SOLR-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120225#comment-13120225
]
Yonik Seeley commented on SOLR-2810:
Yeah, sounds like a good idea.
[
https://issues.apache.org/jira/browse/LUCENE-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120232#comment-13120232
]
Shai Erera commented on LUCENE-3485:
Good catch Gilad ! Do you intend to prepare a
[
https://issues.apache.org/jira/browse/SOLR-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120234#comment-13120234
]
Jan Høydahl commented on SOLR-2303:
---
Ping() on this before 3.5 - branch_3x still has
[
https://issues.apache.org/jira/browse/LUCENE-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilad Barkai updated LUCENE-3485:
-
Attachment: LUCENE-3485.patch
Moving closer to IndexReader's ref counting paradigm, also
[
https://issues.apache.org/jira/browse/LUCENE-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120235#comment-13120235
]
Gilad Barkai edited comment on LUCENE-3485 at 10/4/11 3:57 PM:
[
https://issues.apache.org/jira/browse/SOLR-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120239#comment-13120239
]
Robert Muir commented on SOLR-2303:
---
I committed the patch to trunk-only before, because
[
https://issues.apache.org/jira/browse/SOLR-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120242#comment-13120242
]
Uwe Schindler commented on SOLR-2303:
-
In all cases!!! And the Maven POMs should also
Current SolrCloud implementation does not provide a mechanism to determine
which servers are masters/slaves
---
Key: SOLR-2811
URL:
[
https://issues.apache.org/jira/browse/LUCENE-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilad Barkai updated LUCENE-3485:
-
Attachment: (was: LUCENE-3485.patch)
LuceneTaxonomyReader .decRef() may close the
[
https://issues.apache.org/jira/browse/LUCENE-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilad Barkai updated LUCENE-3485:
-
Attachment: LUCENE-3485.patch
Removed deprecated constructors, no private directory to close
[
https://issues.apache.org/jira/browse/LUCENE-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120252#comment-13120252
]
Michael McCandless commented on LUCENE-1536:
What a tiny patch this has
[
https://issues.apache.org/jira/browse/SOLR-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reassigned SOLR-2369:
-
Assignee: Yonik Seeley
Zookeeper depends on log4j, thus also SolrCloud does
[
https://issues.apache.org/jira/browse/SOLR-2799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120256#comment-13120256
]
Mark Miller commented on SOLR-2799:
---
The tricky part is that if we ever want to have
[
https://issues.apache.org/jira/browse/SOLR-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reassigned SOLR-2622:
-
Assignee: Mark Miller
ZkSolrResourceLoader does not support getConfigDir()
[
https://issues.apache.org/jira/browse/SOLR-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-2622:
--
Priority: Minor (was: Major)
Affects Version/s: (was: 4.0)
Fix Version/s: 4.0
[
https://issues.apache.org/jira/browse/LUCENE-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120264#comment-13120264
]
Robert Muir commented on LUCENE-1536:
-
{quote}
For the default IS heuristic, how
[
https://issues.apache.org/jira/browse/SOLR-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120267#comment-13120267
]
Michael McCandless commented on SOLR-2809:
--
I've been working on a similar idea,
[
https://issues.apache.org/jira/browse/LUCENE-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13118023#comment-13118023
]
sebastian L. edited comment on LUCENE-3440 at 10/4/11 4:51 PM:
[
https://issues.apache.org/jira/browse/LUCENE-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120293#comment-13120293
]
Robert Muir commented on LUCENE-1536:
-
Also, when we pass filter down low as
[
https://issues.apache.org/jira/browse/SOLR-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120301#comment-13120301
]
Yonik Seeley commented on SOLR-2809:
bq. I'm not sure we can combine the approaches but
I get 193 documents found in my SolrDocumentList, but only 10 of them are
returned to me.. how can I remove the 10 document limit?
Thanks,
Andrew
Set rows=200
or page through it
start=40rows=20
and on the next one
start=60rows=20
Best
Erick
On Tue, Oct 4, 2011 at 1:44 PM, Andrew Clark
andrew.clark.at...@gmail.com wrote:
I get 193 documents found in my SolrDocumentList, but only 10 of them are
returned to me.. how can I remove the 10
How about programmatically? Is there some config on the server I can change
or some API call that changes the default resultset size?
On Tue, Oct 4, 2011 at 2:00 PM, Erick Erickson erickerick...@gmail.comwrote:
Set rows=200
or page through it
start=40rows=20
and on the next one
[
https://issues.apache.org/jira/browse/LUCENE-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120356#comment-13120356
]
Robert Muir commented on LUCENE-1536:
-
and current patch is missing the optimization
Add SearcherLifetimeManager, so you can retrieve the same searcher you
previously used
--
Key: LUCENE-3486
URL: https://issues.apache.org/jira/browse/LUCENE-3486
[
https://issues.apache.org/jira/browse/LUCENE-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-3486:
---
Attachment: LUCENE-3486.patch
Patch.
Add SearcherLifetimeManager,
[
https://issues.apache.org/jira/browse/SOLR-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120359#comment-13120359
]
Michael McCandless commented on SOLR-2809:
--
OK I opened LUCENE-3486 w/ my current
TestBooleanMinShouldMatch test failure
--
Key: LUCENE-3487
URL: https://issues.apache.org/jira/browse/LUCENE-3487
Project: Lucene - Java
Issue Type: Bug
Affects Versions: 4.0
Reporter:
1 - 100 of 139 matches
Mail list logo
