i generally will only upgrade every other release. since i started with
1.4, went to 3->5->7.X, and never EVER a .0 or an even .X release,
On Fri, Feb 12, 2021 at 12:01 PM Ishan Chattopadhyaya <
ichattopadhy...@gmail.com> wrote:
> Just avoid 8.8.0 for the moment, until 8.8.1 is released. 8.7.x
Just avoid 8.8.0 for the moment, until 8.8.1 is released. 8.7.x should be
fine.
On Fri, Feb 12, 2021 at 10:28 PM Alessandro Benedetti
wrote:
> Hi,
> following up on Charlie's detailed response I would recommend carefully
> assess the code you are using to interact with Apache Solr (on top of
Hi,
following up on Charlie's detailed response I would recommend carefully
assess the code you are using to interact with Apache Solr (on top of the
Solr changes themselves).
Assuming you are using some sort of client, it's extremely important to
fully understand both the syntax and semantic of
Hi Lulu,
I'm afraid you're going to have to recognise that Solr 5.2.1 is very
out-of-date and the changes between this version and the current 8.x
releases are significant. A direct jump is I think the only sensible
option.
Although you could take the current configuration and attempt to
Hi,
There is no enough information in your email for any of us to help you.
Sounds like your company has created some custom integrations and perhaps
servlet filters.
We do not know anything about your custom «createcore» functionality, so we
cannot know why it does not work.
I’d recommend you
Hi Erick,
Thanks for the response.
1. We have started from zero documents and are observing socketTimeout
intermittently while indexing also.
2. We are not using schemaless as we are aware of the drawbacks and have a
well defined schema.
3. We have tried async but it does not help.
4. We
Yogesh:
Please do not hijack threads. The original poster requested information about
socket timeouts. True “upgrade” was mentioned, but it was a completely
different issue.
Kshitij:
There’s not much information to go on here. It’s possible you were running
close to the timeout limit before and
Hi,
Any information on socket timeout issue when using collection apis? I am
observing increased response time when using Collection APis in upgraded
version
On Wed, Feb 19, 2020 at 2:22 PM Jörn Franke wrote:
> Yes you need to reindex.
> Update solrconfig, schemas to leverage the later feature
Yes you need to reindex.
Update solrconfig, schemas to leverage the later feature of the version (some
datatypes are now more optimal others are deprecated.
Update Solrconfig.xml and schema to leverage the latest datatypes , features
etc..
Create new collection based on newest config.
Use
Hi,
Could you please share me the steps to upgrade SOlr?
Now I am using Solr cloud 5.2.1 on production and wanted to upgrade to
SOlr7.7.2. I am doing this in 2 spteps SOlr 5.2.1 to SOlr 6.6.6 then SOlr 7.7.2.
I have upgraded to Solr but getting issue for indexing of old documents. I am
badly
. margo.br...@indi.nl
W. www.indi.nl
-Original Message-
From: Erick Erickson
Sent: vrijdag 5 juli 2019 17:37
To: solr-user@lucene.apache.org
Subject: Re: Solr upgrade question
There are a _lot_ of changes since 4.8.1.
1> plan on re-indexing the entire corpus. This is required when jumping m
On 05/07/2019 14:49, Margo Breäs | INDI wrote:
Hi all,
At the moment we are working with Solr version 4.8.1 in combination
with an older version of Intershop.
We have recently migrated our entire shop to a new party, and so there
is room for improvements.
Are there any known issues with
There are a _lot_ of changes since 4.8.1.
1> plan on re-indexing the entire corpus. This is required when jumping more
than one major version.
2> Treat it as a green-field application. In particular do not just copy your
schema and config files into 8x and start running. Instead, identify any
On 6/20/2018 12:35 PM, Yunee Lee wrote:
> I have two questions.
>
> 1. solr index on verion 4.6.0 and there are multiple date fields as the type
> DateField in schema.xml
> When I upgraded to version 5.2.1 with new data type Trie* for integer, float,
> string and date.
> Only date fields are
What advantage do you see in TLOG and/or PULL replicas? The TLOG and
PULL replica types are for some pretty specific use cases,
particularly high-indexing-throughput cases where you can't afford to
index each doc on every node in your cluster. If you can afford the
CPU cycles to index on every
Hi Erick/Robi,
Thanks for your replies! one more question, if I go with solrcloud and
having PULL/TLOG replication mixed in the cluster, by the documentation,
this would have Master/Slave mode benefit as well, does that seem feasible
to you? are there any projects adopting this new feature in
On 12/14/2017 2:27 PM, Drooy Drooy wrote:
> We have an in-house project running in Solr 4.7 with Master/Slave mode for
> a few years, what is it going to take to upgrade it to SolrCloud with
> TLOG/PULL replica mode ?
>
> I read the upgrade guides, none of them talking about the jump from 4.x to
>
Completely agree with Robert. I'd also add that you should _not_ copy
your configs from 4x. Start with the 7x configs and add any
customizations but don't change things like luceneMatchVersion and the
like.
If you simply _cannot_ reindex, take a look at
>From what I have read, you can only upgrade to the next major version number
>without using a tool to convert the indexes to the newer version. But that is
>still perilous due to deprications etc
So I think best advice out there is to spin up a new farm on 7.1 (especially
from 4.x), make a
Thanks Erick and Shawn for the input. it makes more sense to move to SOLR
5.x but we would like to get there in few iterations gradually making
incremental changes to have a smooth cut over.
our index size is 3TB (10 shards of 300G each), i was looking for a
alternate route which would save me
On 4/12/2016 6:10 AM, abhi Abhishek wrote:
> I have SOLR 3.6 running currently, i am planning to upgrade this to
> SOLR 4.10. Below were the thoughts we could come up with.
>
> 1. in place upgrade
>I would be making the SOLR 4.10 slave of 3.6 and copy the indexes,
> and optimize this
I would always re-index if possible, it's more certain than upgrading
the indexes. It's "not possible" when it takes very long
And why go for 4.10 rather than 5.5 (Note, 5.5.1 will be out Real Soon
Now). If you can re-index, I'd really think about upgrading to 5.5.1
and going from there.
Did you look at the rest of this thread? There are some comments there.
The CHANGES.txt file will guide you through each intermediate step.
There's nothing going straight from 1.4 to 4.x. You could go from 1.4 - 3.x
then 3.x-4.x, but frankly I'd just start with a stock 4.x distro and
transfer
Hi,
Currently I am using SOLR 1.4.1 and want to migrate to SOLR 4.9.
Is there any manual or link for 1.4 to 4.9? Which can guide step by step on
1. solrconfig.xml changes
2. schema.xml changes
3. changes required in version 1.4.1 queries.
Thanks
Vivek
On Tue, Sep 23, 2014 at 9:19 AM,
4.10.1 out shortly is a good bet.
No idea about the upgrade specifically, but I would probably do some
reading of recent solrconfig.xml to get a hint of new features. Also,
schema.xml has a version number at the top. The default changed which
is controlled by that version number. So, it is
Thanks Alex and Erick for quick response,
This is really helpful.
On Tue, Sep 23, 2014 at 1:19 AM, Erick Erickson erickerick...@gmail.com
wrote:
Probably go for 4.9.1. There'll be a 4.10.1 out in the not-too-distant
future that you can upgrade to if you wish. 4.9.1 - 4.10.1 should be
quite
Chantal,
Thanks for the reply. I will try it out.
Thanks,
Kalyan Manepalli
-Original Message-
From: Chantal Ackermann [mailto:c.ackerm...@it-agenten.com]
Sent: Wednesday, August 01, 2012 3:55 AM
To: solr-user@lucene.apache.org
Subject: Re: Solr upgrade from 1.4 to 3.6
Hi
Hi Kalyan,
that is becouse SolrJ uses javabin as format which has class version numbers
in the serialized objects that do not match. Set the format to XML (wt
parameter) and it will work (maybe JSON would, as well).
Chantal
Am 31.07.2012 um 20:50 schrieb Manepalli, Kalyan:
Hi all,
Everything you need to know about upgrading is listed in CHANGES.txt
On Wednesday 31 August 2011 18:14:11 Pawan Darira wrote:
Hi
I want to upgrade my solr version 1.4 to 3.1. Please suggest the steps
what challenges might occur.
I have started using solr from 1.4 this is my 1st
On 8/16/2011 4:16 AM, olivier sallou wrote:
I just migrated to solr 3.3 from 1.4.1.
My index is still in 1.4.1 format (will be migrated soon).
I have an error when I use sharding with the new version:
org.apache.solr.common.SolrException: java.lang.RuntimeException: Invalid
version (expected
There is a jar for the tests in solr.
I added this dependency in my pom.xml :
dependency
groupIdorg.apache.solr/groupId
artifactIdsolr-core/artifactId
version3.1-SNAPSHOT/version
classifiertests/classifier
scopetest/scope
Didn't get any responses.
But I tried luke 1.0.1 and it did the magic. I run optimization and after
that solr got up.
Best Regards
Alexander Aristov
On 30 March 2011 15:47, Alexander Aristov alexander.aris...@gmail.comwrote:
People
Is were way to upgrade existsing index from solr 1.4 to
Hi Alexander,
I have posted same question a few month ago. The only solution that came up
was to regenerate the index files using the new version. How did you do
this exactly with
luke 1.0.1 ? Would you mind sharing some of that magic ?
Best,
Johannes
2011/3/31 Alexander Aristov
33 matches
Mail list logo
