On 4/26/2019 9:23 AM, Marko Babic wrote:
Apologies for bumping my own post but I'm just wondering if it'd be more
appropriate for me to cut a ticket at this point rather than ask the mailing
list.
No, the mailing list is the correct location. If the discussion
determines that there is a bug
Eureka! Exactly what I needed. Thanks a lot.
I am upgrading from 7.2.0 to 7.7. 0
- I modified the collection to increase the max shards
- Added the replicas
- shutdown one node and everything still worked.
- did my updates
- brought the downed node back up
Thanks again
-Original Message---
OpenSearch is a bad standard. It was written at Amazon and published as a
“standard” with no consultation or committee. It was just “hey folks, we’re
Amazon, so give us results the way we want them."
One example of badness is the “language” parameter, which says the search
client desires search
None. See: https://issues.apache.org/jira/browse/SOLR-2143 and
https://issues.apache.org/jira/browse/SOLR-2419 for the last times I know of
that any consideration was given for supporting it and the reason why not.
Best,
Erick
> On Apr 25, 2019, at 1:02 PM, DESDCS wrote:
>
> What version of O
The benefit falls off fairly rapidly as the batch size increases. I did some
crude benchmarking here:
https://lucidworks.com/2015/10/05/really-batch-updates-solr-2/
If I were going to pick a number, I’d say 100 docs _per shard_. So if you have
10 shards, batch 1,000 docs if possible.
Note, the
Apologies for bumping my own post but I'm just wondering if it'd be more
appropriate for me to cut a ticket at this point rather than ask the mailing
list.
FWIW we've had no reoccurrences of the issue.
On 4/15/19, 11:56 AM, "Marko Babic" wrote:
Hi everyone, I ran into a situation in whic
On 4/26/2019 6:14 AM, Sadiki Latty wrote:
What you're saying makes sense but is it achievable without downtime? i.e: Is
it achievable to change the replication factor to 2 as you suggest, and Solr
puts the sharded documents back together then replicate?
Just changing the replicationFactor par
Hi,
Your plan is not possible. You can compare it to a RAID0 or RAID1. RAID0
is 2 shards/1replica. You have it stripped, not mirrored.
You just can update both solr at the same time (don't forget to backup
your data).
Another way would be to to increase the replicafactor to 2, so you have
Hi Shawn,
What you're saying makes sense but is it achievable without downtime? i.e: Is
it achievable to change the replication factor to 2 as you suggest, and Solr
puts the sharded documents back together then replicate?
Thanks,
Sid
-Original Message-
From: Shawn Heisey
Sent: Thursd
I don't have any replicas the 2 Solr instances are both leaders and are split
between the two.
-Original Message-
From: Jörn Franke
Sent: Thursday, April 25, 2019 5:15 PM
To: solr-user@lucene.apache.org
Subject: Re: Solr Cloud configuration
Are the replicas on the other node?
> Am 25.
Though one can insert an UpdateRequestProcessor to convert any date format.
See solrconfig.xml for how it is setup (as part of 'schemaless' parsing).
Regards,
Alex
On Fri, Apr 26, 2019, 3:57 AM Nicolas Franck,
wrote:
> Dates need to be send in UTC format:
>
> -mm-ddTHH:MM:SSZ
>
> or i
Dates need to be send in UTC format:
-mm-ddTHH:MM:SSZ
or if you want fractional seconds too:
-mm-ddTHH:MM:SS.NNNZ
See
https://lucene.apache.org/solr/guide/6_6/working-with-dates.html#WorkingwithDates-DateFormatting
There is no automatic conversion for dates
On 26 Apr 2019, at 09:50,
Dear SOLR Team,
I am using SOLR 6.6.0 version for indexing data stored in the POSTGRESQL
database. I am facing an issue and needs your help
Below is the snapshot of the table i am trying to index: -
Steps followed for indexing DATETIMELOG field in above table: -
1) First i created field of t
13 matches
Mail list logo
