Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: jaga_india [mailto:jaga@gmail.com]
> Sent: Thursday, January 22, 2015 7:20 AM
> To: java-user@lucene.apache.org
> Subject: Re: Upgrade Lucene to
Hi Sai,
hopes you have successfully migrated to 4.0
we also migrating from 2.4 to 4.10, but after updating to 4.10 it is taking
more time than 2.4.
I have posted a query , below is the link... help me.
http://lucene.472066.n3.nabble.com/Multiple-CFS-files-are-generated-in-lucene-4-10-2-td417633
NRT search (http://wiki.apache.org/lucene-java/NearRealtimeSearch)
On Sat, Jan 12, 2013 at 6:50 AM, saisantoshi wrote:
> I was just going through compiling our sources against 4.0 and it seems
> there
> are quite some API changes. Any major functionality changes from 2.4 - 4.0?
> with respect to
I was just going through compiling our sources against 4.0 and it seems there
are quite some API changes. Any major functionality changes from 2.4 - 4.0?
with respect to indexing/searching.
Thanks,
Sai.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Upgrade-Lucene-to-lates
Thanks for all the responses.
Apart from the API changes, is there any major functionality change from
2.4.0 -> 4.x version. I know we need to modify the API to the latest version
but just curious if we need to be aware of any functional changes so as to
do more thorough testing?
Thanks,
Sai.
Of course you're free to do as you like - who will stop you? :)
The problem is the lack of a single place to look for detailed guidance on
handling a long-distance upgrade like that.
But it's difficult to generalize here: the possible range in the level of
difficulty involved is vast, depending
I am in the process of upgrading LuSql from 2.x to 4.x and I am first
going to 3.6 as the jump to 4.x was too big.
I would suggest this to you. I think it is less work.
Of course I am also able to offer LuSql to 3.6 users, so this is
slightly different from your case.
-Glen
On Wed, Jan 9, 2013 a
Are there any best practices that we can follow? We want to get to the latest
version and am thinking if we can directly go from 2.4.0 to 4.x (as supposed
to 2.x - 3.x and 3.x - 4.x)? so that it will not only save time but also
testing cycle at each migration hop.
Are there any limitations in dire
as mentioned before -- I'm not an expert on Lucene (far from it) -- but
it seems to me like each migration version will take almost equal amount
of work so if I were you I'd rethink this plan and consider migration to 4.0
Igal
On 1/9/2013 1:08 PM, saisantoshi wrote:
Is there any migration g
I don't think there is a migration guide from 2.X to 3.X, other than the
specific information in the release notes.
If you start reading CHANGES.txt at version 3.0.0, and then each later
release's notes after that, especially the sections "Changes in backwards
compatibility policy", e.g. for 3.
Is there any migration guide from 2.x to 3.x? ( as per the suggestion, i
would like to upgrade first from 2.4.0 to 2.9.0 and from 2.9.0 to 3.6) and
later we decide if we want to upgrade from 3.6 to 4.x version?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Upgrade-Lucene-t
Sai,
For the transition from 2.X to 3.X, I recommend compiling your code against the
latest 2.9.X version (2.9.4), looking at the deprecation messages, and making
changes until these are all addressed and compilation no longer produces
deprecation messages. Once that's done, your code should c
is only a thought, because I haven't upgraded to 4.0 yet.
-Paul
> -Original Message-
> From: Igal Sapir [mailto:i...@getrailo.org]
> Sent: Wednesday, January 09, 2013 11:42 AM
> To: java-user@lucene.apache.org
> Subject: Re: Upgrade Lucene to latest version (4.0) from 2.4.0
I can not elaborate much myself add there are many changes and I'm not an
expert on License.
I can tell you though that many signatures have changed as well as package
names.
There were many API changes even between 3.6 and 4.0
--
typos, misspels, and other weird words brought to you courtesy of
Thanks. Could you please elaborate on what is needed other than replacing the
jars? Are the jars listed is the only jars or any additional jars required?
Is the API not backward compatible? I mean to say whatever the API calls we
are using in 2.4.0 is not supported by 4.0? Has the signature modifi
We recently went through the same process. We upgraded our indexing service
from 1.9.1 to 3.6.1. Unfortunately, the process is not as easy as you
thought. Besides replacing the jar files. You also need to change your code
to adopt to the new API. There are many changes, the most import parts are
in
the API has changed much over time so I suspect that it will take more
than replacing the jars.
On 1/9/2013 11:04 AM, saisantoshi wrote:
We have an existing application which uses Lucene 2.4.0 version. We are
thinking of upgrading it to alatest version (4.0). I am not sure the process
involved
17 matches
Mail list logo
