On Sun, Sep 27, 2009 at 1:50 AM, Chris Hostetter
hossman_luc...@fucit.orgwrote:
FWIW: adding the whitespaces makes these key names inconcsistant with
every other stat name in solr ... none of them use whitespace
In cases where the lack of spaces makes things hard to read other mbeans
use _
On Sun, Sep 27, 2009 at 9:41 AM, Mark Miller markrmil...@gmail.com wrote:
DebugLogger has the following code:
public DebugInfo(String name, int type, DebugInfo parent) {
this.name = name;
this.type = type;
this.parent = parent;
lst = new NamedList();
if (parent
[
https://issues.apache.org/jira/browse/SOLR-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12759992#action_12759992
]
Shalin Shekhar Mangar commented on SOLR-1466:
-
Yep, there is a leak alright.
init-forrest-entities:
[mkdir] Created dir: /tmp/apache-solr-nightly/build
[mkdir] Created dir: /tmp/apache-solr-nightly/build/web
compile-solrj:
[mkdir] Created dir: /tmp/apache-solr-nightly/build/solrj
[javac] Compiling 86 source files to /tmp/apache-solr-nightly/build/solrj
See http://hudson.zones.apache.org/hudson/job/Solr-trunk/937/changes
[
https://issues.apache.org/jira/browse/SOLR-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-1466.
---
Resolution: Fixed
Assignee: Mark Miller
Thanks for the review!
Fix File descriptor leak in
[
https://issues.apache.org/jira/browse/SOLR-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-1221.
---
Resolution: Fixed
Change Solr Highlighting to use the SpanScorer with MultiTerm expansion by
[
https://issues.apache.org/jira/browse/SOLR-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stanislaw Osinski updated SOLR-1314:
Attachment: SOLR-1314.patch
Hi Grant,
I've built Carrot2 3.1.0 binaries and tested them
Also make both options default to true.
If so, isn't this line (from HighlightComponent) needed to be
also true by default?
boolean rewrite =
!(Boolean.valueOf(req.getParams().get(HighlightParams.USE_PHRASE_HIGHLIGHTER))
Thank you Koji!
Indeed - those need to default true now.
Nice eyes, and thanks for looking over!
Koji Sekiguchi wrote:
Also make both options default to true.
If so, isn't this line (from HighlightComponent) needed to be
also true by default?
boolean rewrite =
Turned up a bug to boot ...
Mark Miller wrote:
Thank you Koji!
Indeed - those need to default true now.
Nice eyes, and thanks for looking over!
Koji Sekiguchi wrote:
Also make both options default to true.
If so, isn't this line (from HighlightComponent) needed to be
also
[
https://issues.apache.org/jira/browse/SOLR-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reopened SOLR-1221:
---
There is a bug to take care of, and a missing piece that Koji pointed out.
Change Solr Highlighting to
[
https://issues.apache.org/jira/browse/SOLR-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12760048#action_12760048
]
Mark Miller commented on SOLR-1221:
---
Grrr ... darn it. Its at the Lucene level.
Right now, if I see something funny (like an exception that doesn't
cause a test failure) in a big junit test report, it's hard to tell
what test it was in - the output for each test is simply catenated,
with no separator.
Is there a way to get junit to print this info, or do we need to do
[
https://issues.apache.org/jira/browse/SOLR-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12760057#action_12760057
]
Mark Miller commented on SOLR-1221:
---
Easy enough to side step this bug in Lucene for now -
: Right now, if I see something funny (like an exception that doesn't
: cause a test failure) in a big junit test report, it's hard to tell
: what test it was in - the output for each test is simply catenated,
: with no separator.
what do you mean by output? System.out? System.err? messages
On Sun, Sep 27, 2009 at 1:13 PM, Chris Hostetter
hossman_luc...@fucit.org wrote:
: Right now, if I see something funny (like an exception that doesn't
: cause a test failure) in a big junit test report, it's hard to tell
: what test it was in - the output for each test is simply catenated,
:
[
https://issues.apache.org/jira/browse/SOLR-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12760078#action_12760078
]
Mark Miller commented on SOLR-1221:
---
What do people thing about putting in an updated
[
https://issues.apache.org/jira/browse/SOLR-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12760079#action_12760079
]
Yonik Seeley commented on SOLR-1221:
bq. What do people thing about putting in an
[
https://issues.apache.org/jira/browse/SOLR-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12760080#action_12760080
]
Mark Miller commented on SOLR-1221:
---
I don't see one -
ugly options I can think of -
1.
: 3. use an overridden version of NumericQuery in Solr that returns a
placeholder term from getTerm
on the surface that doesn't sound too horrific. just make it final and
deprecated and open an issue to remove it when upgrading to Lucene 3.0.
-Hoss
Chris Hostetter wrote:
: 3. use an overridden version of NumericQuery in Solr that returns a
placeholder term from getTerm
on the surface that doesn't sound too horrific. just make it final and
deprecated and open an issue to remove it when upgrading to Lucene 3.0.
-Hoss
Yeah, your
[
https://issues.apache.org/jira/browse/SOLR-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12760082#action_12760082
]
Yonik Seeley commented on SOLR-1221:
How can one reproduce this bug? The query parser
[
https://issues.apache.org/jira/browse/SOLR-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12760083#action_12760083
]
Mark Miller edited comment on SOLR-1221 at 9/27/09 11:54 AM:
-
[
https://issues.apache.org/jira/browse/SOLR-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12760083#action_12760083
]
Mark Miller commented on SOLR-1221:
---
Sorry - should have been more clear.
The bug is
: On S-1294, the SolrJS patch, I yet again have concerns about even including
: this, given the lack of activity (from Matthias, the original author and
...
: true for others too. At a minimum, I think S-1294 should be pushed to 1.5.
: Next up, I think we consider pulling SolrJS from
[
https://issues.apache.org/jira/browse/SOLR-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1221:
--
Attachment: SOLR-1221.patch
this patch needs to be applied to finish the issue - but for now it will
[
https://issues.apache.org/jira/browse/SOLR-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12760087#action_12760087
]
Mark Miller commented on SOLR-1221:
---
bq. The query parser produces a normal term query for
[
https://issues.apache.org/jira/browse/SOLR-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12760083#action_12760083
]
Mark Miller edited comment on SOLR-1221 at 9/27/09 12:36 PM:
-
[
https://issues.apache.org/jira/browse/SOLR-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar reopened SOLR-1447:
-
Re-opening because the mergeScheduler and mergePolicy specified in the
indexDefaults
[
https://issues.apache.org/jira/browse/SOLR-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-1447:
Attachment: SOLR-1447-indexDefault-test.patch
Here's a test case which fails.
[
https://issues.apache.org/jira/browse/SOLR-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-1447:
Attachment: SOLR-1447-indexDefault-test.patch
Fix which passes the test case posted
[
https://issues.apache.org/jira/browse/SOLR-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar resolved SOLR-1447.
-
Resolution: Fixed
Committed revision 819401.
Simple property injection
SolrJ XML parser errors on null names in a NamedList
Key: SOLR-1467
URL: https://issues.apache.org/jira/browse/SOLR-1467
Project: Solr
Issue Type: Bug
Components: clients - java
Solrj bug when using facet.missing
--
Key: SOLR-1468
URL: https://issues.apache.org/jira/browse/SOLR-1468
Project: Solr
Issue Type: Bug
Components: clients - java
Affects Versions: 1.3
[
https://issues.apache.org/jira/browse/SOLR-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley deleted SOLR-1467:
---
SolrJ XML parser errors on null names in a NamedList
[
https://issues.apache.org/jira/browse/SOLR-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-1468.
Resolution: Fixed
I just committed a patch for this... thanks for the bug report!
Solrj bug when
[
https://issues.apache.org/jira/browse/SOLR-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-1449:
---
Attachment: SOLR-1449.patch
checkpoint patch, new additions...
1. updated TestConfig to also assert that the
[
https://issues.apache.org/jira/browse/SOLR-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12760107#action_12760107
]
Yonik Seeley commented on SOLR-1449:
bq. lib dir=../../dist/
As you say, layout is a
I've switched ant test to use the plain formatter rather than the
XML formatter - I think this is a lot more sane for humans looking at
the output. XML escaped failing assertions are no fun to read. And
of course there is the buffering bug too - running any really large
test that prodoces output
[
https://issues.apache.org/jira/browse/SOLR-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12760112#action_12760112
]
Mark Miller commented on SOLR-1221:
---
bq. deprec ConstantScoreRangeQuery (if ever used in
[
https://issues.apache.org/jira/browse/SOLR-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12760114#action_12760114
]
Uwe Schindler commented on SOLR-1221:
-
Does RangeQuery really need to be highlighted? It
[
https://issues.apache.org/jira/browse/SOLR-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-1449:
---
Attachment: SOLR-1449.patch
minor update to the previous patch...
1) the patch command didn't like the empty
[
https://issues.apache.org/jira/browse/SOLR-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12760124#action_12760124
]
Hoss Man commented on SOLR-1449:
bq. should we reference the libs in contrib (where they are
[
https://issues.apache.org/jira/browse/SOLR-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man reassigned SOLR-1449:
--
Assignee: Hoss Man
solrconfig.xml syntax to add classpath elements from outside of instanceDir
[
https://issues.apache.org/jira/browse/SOLR-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12760127#action_12760127
]
Mark Miller commented on SOLR-1221:
---
bq. In Lucene, the fix would only be needed for
: I've switched ant test to use the plain formatter rather than the
: XML formatter - I think this is a lot more sane for humans looking at
: the output. XML escaped failing assertions are no fun to read. And
...although if you use ant test-reports you're going to want to add
TestReplicationHandler failure
--
Key: SOLR-1469
URL: https://issues.apache.org/jira/browse/SOLR-1469
Project: Solr
Issue Type: Bug
Reporter: Yonik Seeley
TestReplicationHandler seems to fail often.
[
https://issues.apache.org/jira/browse/SOLR-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1469:
---
Attachment: TestReplicationHandler.FAILED.210743
Attaching one particular worrying failure.
Hey, it seems like the compound file format is always being used
now... even in the example, when the config says not to.
Anyone notice when this started?
-Yonik
http://www.lucidimagination.com
[
https://issues.apache.org/jira/browse/SOLR-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12760134#action_12760134
]
Mark Miller commented on SOLR-1469:
---
Are you using Windows? Havn't gotten it to fail on
index formats always compound
-
Key: SOLR-1470
URL: https://issues.apache.org/jira/browse/SOLR-1470
Project: Solr
Issue Type: Bug
Reporter: Yonik Seeley
Fix For: 1.4
Seems like the
Mark Miller wrote:
Yonik Seeley wrote:
Hey, it seems like the compound file format is always being used
now... even in the example, when the config says not to.
Anyone notice when this started?
-Yonik
http://www.lucidimagination.com
Its being set correctly. Something with the
[
https://issues.apache.org/jira/browse/SOLR-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1470:
--
Attachment: SOLR-1470.patch
I think this will fix it
index formats always compound
Yonik Seeley wrote:
Hey, it seems like the compound file format is always being used
now... even in the example, when the config says not to.
Anyone notice when this started?
-Yonik
http://www.lucidimagination.com
Its being set correctly. Something with the mergepolicy?
--
- Mark
[
https://issues.apache.org/jira/browse/SOLR-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12760139#action_12760139
]
Mark Miller commented on SOLR-1470:
---
You know, it says that only works with LogMergePolicy
[
https://issues.apache.org/jira/browse/SOLR-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12760146#action_12760146
]
Yonik Seeley commented on SOLR-1469:
OK, I think this particular one might be a bug in
57 matches
Mail list logo
