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 SOLR team,
Please may I ask for advice regarding upgrading the SOLR version (our project
currently running on solr-5.2.1) to the latest version?
What are the steps, breaking changes and potential issues ? Could this be done
as an incremental version upgrade or a direct jump to the newest
Lucene has never really supported this migration path. There’s a whole long
discussion of why, but basically you can’t upgrade an index with 100% fidelity
because the original information isn’t there. Here’s the most succinct
definition I’ve seen (from Robert Muir):
"I think the key issue here
Hi All,
We are presently using solr 5.3.0 and planning to migrate to version 8.4.1 .I
tried using index upgrader for the same .
I am able to upgrade 5.3.0->6.6.6 and 6.6.6 to 7.7.3.But when I try upgrading
7.7.3 index to 8.4.1,I keep getting following error :
This index was initially
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 Team,
We are upgrading from Solr 7.5.0 version to 8.5.2 version.
We are doing custom /createcore functionality from our web application. In
7.5.0 version we mentioned the that Filter in web.xml for create core and it is
working fine.
For 8.5.2 that customized create core filter not
ow 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
> >> docu
nts. I am badly stuck get get old document in migrated solr version.
>>>
>>> Should I do the re-indexing? If yes can you please share the way to
>> re-indexing?
>>>
>>> Can you please provide your inputs on this?
>>>
>>> Thanks,
>>>
s,
> >
> > Yogesh Chaudhari
> >
> > -Original Message-
> > From: kshitij tyagi
> > Sent: Wednesday, February 19, 2020 12:52 PM
> > To: solr-user@lucene.apache.org
> > Subject: Solr Upgrade socketTimeout issue in 8.2
> >
> > Hi,
>
inal Message-
> From: kshitij tyagi
> Sent: Wednesday, February 19, 2020 12:52 PM
> To: solr-user@lucene.apache.org
> Subject: Solr Upgrade socketTimeout issue in 8.2
>
> Hi,
>
> We have upgraded our solrCloud from version 6.6.0 to 8.2.0
>
> At the time of indexi
PM
To: solr-user@lucene.apache.org
Subject: Solr Upgrade socketTimeout issue in 8.2
Hi,
We have upgraded our solrCloud from version 6.6.0 to 8.2.0
At the time of indexing intermittently we are observing socketTimeout exception
when using Collection apis. example when we try reloading one
Hi,
We have upgraded our solrCloud from version 6.6.0 to 8.2.0
At the time of indexing intermittently we are observing socketTimeout
exception when using Collection apis. example when we try reloading one of
the collection using CloudSolrClient class.
Is there any performance degradation in
Yeah, 3.4.x upgrades were pretty strainght-forward.
The 3.5.5 upgrade was trickier, but the problems were in the
admin UI. The admin UI uses several “4 letter words” to do its
ZooKeeper reporting, and that required explicit permissions, but IIRC
that all only affected the admin UI reporting about
Thanks Eric. Also, thanks for that little pointer about the JIRA. Just to
make sure I also checked for the upgrade JIRAs for other two intermediate
Zookeeper versions 3.4.11 and 3.4.13 between Solr 7.2.1 and Solr 7.7.2 and
they didn't seem to contain any Solr code changes either.
On Thu, Feb 13,
That should be OK. There were no code changes necessary for that upgrade. see
SOLR-13363
> On Feb 12, 2020, at 5:34 PM, Rahul Goswami wrote:
>
> Hello,
> We are running a SolrCloud (7.2.1) cluster and upgrading to Solr 7.7.2. We
> run a separate multi node zookeeper ensemble which currently
Hello,
We are running a SolrCloud (7.2.1) cluster and upgrading to Solr 7.7.2. We
run a separate multi node zookeeper ensemble which currently runs
Zookeeper 3.4.10.
Is it also required to upgrade Zookeeper (to 3.4.14 as per change.txt for
Solr 7.7.2) along with Solr ?
I tried a few basic
. 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
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 upgrading over that many versions in general,
or
Oops fumble fingers. Anyway I'd recommend completely reindexing into a new
collection.
On Sun, Nov 4, 2018, 12:53 Erick Erickson Lucene does not guarantee back comparability over two major versions, so
> I'd recommend completely reinde
>
> On Sun, Nov 4, 2018, 02:02 Piyush Kumar Nayak wrote:
>
Lucene does not guarantee back comparability over two major versions, so
I'd recommend completely reinde
On Sun, Nov 4, 2018, 02:02 Piyush Kumar Nayak Hi,
>
> What is the best way to migrate cores from an old version of Solr (say
> 5.x) to a newer version (say 7.x). I did not find anything
Hi,
What is the best way to migrate cores from an old version of Solr (say 5.x) to
a newer version (say 7.x). I did not find anything pertinent to the matter in
the Solr reference guide.
Is there a tool that can do that seamlessly?
Regards,
Piyush.
IIUC the 5x->7x upgrade won't immediately fail like a 6x->8x upgrade
would, but neither is it really expected to produce the results you
expect due to differences in the index formats.
On Sat, Oct 6, 2018 at 1:31 PM Jan Høydahl wrote:
>
> Shawn, my impression is that you WILL be able to upgrade a
Shawn, my impression is that you WILL be able to upgrade a 5.x index to 6.x and
then to 7.x for use with 7.x. So your wiki page is a bit too strict here.
But if you ever want to upgrade to 8.x, that version will require the "first
created" version to be 7.0 or later, so you'll need a full
On 10/5/2018 4:41 AM, padmanabhan1616 wrote:
1. We cannot upgrade directly from 5.x to 7.x instead upgrade to 5.5 then
upgrade to 7 as there is major index format level changes taken place in 5.5
or later version.
Solr 7.x cannot read indexes from 5.5. It can only read indexes that
were
Hi Team,
We planning to upgrade SOLR from 5.2.1 to 7.x version. I just googled and
found that there is no way of upgrading from 5.x to 7.x directly
Here are the list of suggestions gathered from different sources
1. We cannot upgrade directly from 5.x to 7.x instead upgrade to 5.5 then
Hi,
We are in the process of upgrading Solr from solr 5.2.1 to solr 7.4.0 and I'm
facing below issues. Please help me in resolving.
1)HttpSolrClient tempClient = new
HttpSolrClient.Builder("http://localhost:8983/solr;).build();
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
Hi,
Hi,
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 not upgraded properly with the following
lable and how you'd want to migrate given your existing
>> environment is so far behind.
>> >
>> >
>> > Thanks
>> >
>> > Robi
>> >
>> >
>> > From: Drooy Drooy <drooy2...@gmail.com>
>> &
> >
> > Robi
> >
> >
> > From: Drooy Drooy <drooy2...@gmail.com>
> > Sent: Thursday, December 14, 2017 1:27:53 PM
> > To: solr-user@lucene.apache.org
> > Subject: Solr upgrade from 4.x to 7.1
> >
> > Hi A
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
>
given your existing
> environment is so far behind.
>
>
> Thanks
>
> Robi
>
>
> From: Drooy Drooy <drooy2...@gmail.com>
> Sent: Thursday, December 14, 2017 1:27:53 PM
> To: solr-user@lucene.apache.org
> Subject: Solr up
ough more fully with the new possibilities
available and how you'd want to migrate given your existing environment is so
far behind.
Thanks
Robi
From: Drooy Drooy <drooy2...@gmail.com>
Sent: Thursday, December 14, 2017 1:27:53 PM
To: solr-user@lucene.apache.or
Hi All,
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
7.
Thanks much
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.
Hi All,
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 index.
will optimizing the Lucene 3.3
I have made changes as listed in document ( sol.xml, core.properties, schema
changes) before i did upgrade
I am using solrcloud deployment
Doing node by node upgrade.
Almost everything work fine. Except if new upgraded node ( node which is
upgraded to 5.5) become leader than even if that node
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,
Hi all,
I currently working on upgrade sorl 1.4.1 to sorl latest stable release.
What is the latest stable release I can use?
Is there specfic things I need to look at when upgrade.
Need help
Thanks
Danesh
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
I am using following field type with solr 4.2 its working fine.
field name=latlong type=location_rpt indexed=true stored=true
required=false multiValued=false /
fieldType name=location_rpt
class=solr.SpatialRecursivePrefixTreeFieldType
distErrPct=0.025
Hi Hoss,
Thanks for your response. As pointed we are running Solr on a JVM that is
configured to use SSL Key store. We are not specifying the password while
running the JVM, we are using keystore for secured access. The issue that
we are facing now is, we are able to make few initiall
Hi All,
We recently ungraded from solr 3.5 to solr4.4 . After the upgrade we are
facing the following issue. Could anyone please suggest on what could be
done.
INFO [2013-12-13 07:54:50,149] [threadPoolTaskExecutor-2] [HttpClientUtil]
[HttpClientUtil.java:103] - Creating new http client,
: We recently ungraded from solr 3.5 to solr4.4 . After the upgrade we are
: facing the following issue. Could anyone please suggest on what could be
: done.
You are aparently running Solr code from a JVM configured to use an SSL
keystore which has a password configured on it, and you either
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,
Hi all,
We are trying to upgrade our solr instance from 1.4 to 3.6. We
use SolrJ API to fetch the data from index. We see that SolrJ 3.6 version is
not compatible with index generated with 1.4.
Is this known issue and is there a workaround for this.
Thanks,
Kalyan Manepalli
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 experience to upgrade
the version
thanks
Pawan
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
Hi,
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 2, but 1) or the data in not in 'javabin'
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
typejar/type
/dependency
Ludovic.
-
Jouve
France.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-upgrade-from-1-4-1-to-3-1-finding-AbstractSolrTestCase-binaries-help-please-tp2845011p2846223.html
Sent from the Solr - User mailing list archive
HI, all.
I'm working on upgrading from 1.4.1 to 3.1, and I'm having some troubles with
some of the unit test code for our custom Filters. We wrote the tests to
extend AbstractSolrTestCase, and I've been reading the thread about the
test-harness elements not being present in the 3.1
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
People
Is were way to upgrade existsing index from solr 1.4 to solr 4(trunk). When
I configured solr 4 and launched it complained about incorrect lucence file
version (3 instead of old 2)
Are there any procedures to convert index?
Best Regards
Alexander Aristov
65 matches
Mail list logo
