[
https://issues.apache.org/jira/browse/LUCENE-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761246#comment-13761246
]
Michael McCandless commented on LUCENE-5202:
Oh, sorry, I see; I indeed
[
https://issues.apache.org/jira/browse/LUCENE-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761254#comment-13761254
]
Benson Margulies commented on LUCENE-5202:
--
Yes, that's what I have and it
[
https://issues.apache.org/jira/browse/SOLR-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761259#comment-13761259
]
Tommaso Teofili commented on SOLR-5201:
---
ok good, thanks. I'll merge it to branch_4x
[
https://issues.apache.org/jira/browse/SOLR-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761260#comment-13761260
]
ASF subversion and git services commented on SOLR-5201:
---
Commit
Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-trunk/374/
1 tests failed.
REGRESSION: org.apache.lucene.index.Test2BPostings.test
Error Message:
GC overhead limit exceeded
Stack Trace:
java.lang.OutOfMemoryError: GC overhead limit exceeded
at
[
https://issues.apache.org/jira/browse/LUCENE-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761264#comment-13761264
]
Michael McCandless commented on LUCENE-5202:
bq. There's a call to peekToken
[
https://issues.apache.org/jira/browse/LUCENE-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761475#comment-13761475
]
Benson Margulies commented on LUCENE-5202:
--
OK, I see.
So I'll leave it to you
In org.apache.solr.cloud.Overseer.getShardNames of branch_4x, the second
exception message is an exact copy of the first, but probably should be
something like “shards param must specify at least one shard”:
static void getShardNames(ListString shardNames, String shards) {
if(shards ==null)
[
https://issues.apache.org/jira/browse/SOLR-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761489#comment-13761489
]
Jack Krupansky commented on SOLR-4816:
--
I was surprised to see that this high priority
[
https://issues.apache.org/jira/browse/SOLR-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761503#comment-13761503
]
Hardik Upadhyay commented on SOLR-5217:
---
Yes,over the iteration on parent entity,
[
https://issues.apache.org/jira/browse/SOLR-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761505#comment-13761505
]
Hardik Upadhyay commented on SOLR-5217:
---
CachedSqlEntityProcessor should take in
As part of a recent commit I cleaned up the comments surrounding the
clustering extension in the Solr example. As part of this I added
comments concerning configuration of clustering algorithms in the
Carrot2 framework, but also a helpers that refer to our commercial
clustering algorithm Lingo3G.
I don't think it's an issue - if it helps users to conclude how to get
it I think it's actually an improvement!
simon
On Sun, Sep 8, 2013 at 8:50 PM, Dawid Weiss
dawid.we...@cs.put.poznan.pl wrote:
As part of a recent commit I cleaned up the comments surrounding the
clustering extension in the
I think less configuration there is an improvement :)
The problem seems to be that carrot.algorithm can be any clustering
component that plugs into the Carrot2 framework -- including our
commercial algorithm (I don't think there's anything else besides
that). We suck at brand differentiation and
[
https://issues.apache.org/jira/browse/LUCENE-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761540#comment-13761540
]
Michael McCandless commented on LUCENE-5123:
{quote}
1. move write() from
[
https://issues.apache.org/jira/browse/LUCENE-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761544#comment-13761544
]
Michael McCandless commented on LUCENE-5202:
OK I'll commit this fix ...
[
https://issues.apache.org/jira/browse/LUCENE-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761545#comment-13761545
]
Benson Margulies commented on LUCENE-5202:
--
Well, it only took me about 10
[
https://issues.apache.org/jira/browse/SOLR-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761550#comment-13761550
]
Mark Miller commented on SOLR-4816:
---
bq. this high priority ... Jira ... is still listed
I see no problem with it.
- Mark
On Sun, Sep 8, 2013 at 2:50 PM, Dawid Weiss dawid.we...@cs.put.poznan.plwrote:
As part of a recent commit I cleaned up the comments surrounding the
clustering extension in the Solr example. As part of this I added
comments concerning configuration of
Mark Miller created SOLR-5221:
-
Summary: CloudSolrServer should default to 15 seconds for the zk
client timeout, just like Solr core does.
Key: SOLR-5221
URL: https://issues.apache.org/jira/browse/SOLR-5221
[
https://issues.apache.org/jira/browse/SOLR-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761592#comment-13761592
]
Mark Miller commented on SOLR-5221:
---
It currently defaults to 10 - the old core default.
[
https://issues.apache.org/jira/browse/SOLR-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761604#comment-13761604
]
Kranti Parisa commented on SOLR-4465:
-
Does any of those tickets support configurable
[
https://issues.apache.org/jira/browse/SOLR-5215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reassigned SOLR-5215:
-
Assignee: Mark Miller
Deadlock in Solr Cloud ConnectionManager
[
https://issues.apache.org/jira/browse/SOLR-5215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-5215:
--
Fix Version/s: 5.0
4.5
Deadlock in Solr Cloud ConnectionManager
[
https://issues.apache.org/jira/browse/SOLR-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761604#comment-13761604
]
Kranti Parisa edited comment on SOLR-4465 at 9/9/13 4:27 AM:
-
[
https://issues.apache.org/jira/browse/SOLR-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761604#comment-13761604
]
Kranti Parisa edited comment on SOLR-4465 at 9/9/13 4:30 AM:
-
[
https://issues.apache.org/jira/browse/SOLR-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761620#comment-13761620
]
Jack Krupansky commented on SOLR-5006:
--
The OverseerCollectionProcessor#createShard
[
https://issues.apache.org/jira/browse/SOLR-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761623#comment-13761623
]
Noble Paul commented on SOLR-5006:
--
Yes, It's an omission. Thanks for pointing it out
[
https://issues.apache.org/jira/browse/SOLR-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761625#comment-13761625
]
Noble Paul commented on SOLR-5006:
--
Let's open a separate issue for the ref guide
29 matches
Mail list logo
