Yeah,got it~. So the QueryResult.segmentTerminatedEarly maybe a boolean,
instead of Boolean, is better, right?
Mikhail Khludnev 于2018年9月3日周一 下午1:36写道:
> It's neither, it's on purpose. By default result.segmentTerminatedEarly is
> null, hence it doesn't appear in result output. see
> ResponseBu
Thanks !
In fact, if the data reaches the PB level, or higher. It is not realistic to
increase the memory.
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
It's neither, it's on purpose. By default result.segmentTerminatedEarly is
null, hence it doesn't appear in result output. see
ResponseBuilder.setResult(QueryResult).
So, if cmd requests early termination, it sets false by default, enabling
"false" output even it won't be the case. And later it mi
Thanks Erick. Suppose I have 5 hosts h1,h2,h3,h4,h5 and want to create a
5X2 solr cloud of 5 shards, 2 replicas per shard. On each host I will run
two solr JVMs, each hosts a single solr core. Solr's default 'snitch'
provide a 'host' tag, so I wonder if I can use it to prevent any host from
have t
You need to provide a "snitch" and define a rule appropriately. This
is a variant of "rack awareness".
Solr considers two JVMs running on the same physical host as
completely separate Solr instances, so to get replicas on different
hosts you need a snitch etc.
Best,
Erick
On Sun, Sep 2, 2018 at 4
Hi all,
I saw the code like following:
QueryResult result = new QueryResult();
cmd.setSegmentTerminateEarly(params.getBool(CommonParams.SEGMENT_TERMINATE_EARLY,
CommonParams.SEGMENT_TERMINATE_EARLY_DEFAULT));
if (cmd.getSegmentTerminateEarly()) {
result.setSegmentTerminatedEarly(Boolean.FAL
Hi,
In rule based replica placement, how to ensure there are no more than one
replica for any shard on the same host? In the documentation there is an
example rule
shard:*,replica:<2,node:*
Does 'node' refer to solr instance or actual physical host? Is there an
example for defining t
Hmmm, please raise a JIRA and, if possible, attach a patch that works
for you. Most of us don't have Windows machines readily available
which hobbles testing, so it's very helpful of someone can test in a
real environment.
Best,
Erick
On Sun, Sep 2, 2018 at 1:47 PM wrote:
>
> Hi,
>
> please notic
Hi,
please notice the following lines added (among others) to "solr.cmd" by commit
https://github.com/apache/lucene-solr/commit/b36c68b16e67ae701cefce052a4fdbaac88fb65c
for https://issues.apache.org/jira/browse/SOLR-6833 about 4 years ago:
set TMP=!SOLR_HOME:%EXAMPLE_DIR%=!
IF NOT "%TMP%"==
Which are you using? schema.xml of managed-schema? You must be using
one or the other, but not both.
It's likely you're using managed-schema, that's where changes need to be made.
Best,
Erick
On Sun, Sep 2, 2018 at 11:55 AM Bineesh wrote:
>
> Hi Govind,
>
> Thanks for the reply. Pleasee below th
Hi Govind,
Thanks for the reply. Pleasee below the chema.xml and managed.schema
1: schema.xml
int, float, long, date, double, including the "Trie" variants.
2 : managed.schema
- For maximum indexing performance, use the ConcurrentUpdateSolrServer
Thanks Shawn. I wrote my own filter. I attached my jar in hear.
I found your answer in hear:
http://lucene.472066.n3.nabble.com/How-to-load-plugins-with-Solr-4-9-and-SolrCloud-td4312113.html
Based on your answer, is it possible that blob Api does not work for my own
filter jar?
norm.jar
Please metion the schema definition of date.
If you edit solr schema manually, you need to reload the solr core.
On Sat, Sep 1, 2018 at 3:38 AM kunhu0...@gmail.com
wrote:
> Hello Team,
>
> Need suggestions on Solr Indexing. We are using Solr-6.6.3 and Nutch 1.14.
>
> I see unknown field 'cache
13 matches
Mail list logo