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 IndexWriter, IndexReader, and IndexSearcher classes.


Regards
--
Bin Lan
Software Developer
Perimeter E-Security
O - (203)541-3412

Follow Us on Twitter: www.twitter.com/PerimeterNews
Read Our Blog: security.perimeterusa.com/blog





On Wed, Jan 9, 2013 at 2:04 PM, saisantoshi <saisantosh...@gmail.com> 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 in upgrading to latest version. Is it just copying of the jars? If
> yes, what are all the jars that we need to copy over. Will it be backward
> compatible? Any additional measures we need to take care of?
>
> With version 2.4.0, we have the following jars:
> lucene-core-2.4.0.jar
> lucene-analyzers-2.4.0.jar
>
> With 4.0:
> lucene-analyzers-common-4.0.0.jar
> lucene-analyzers-icu-4.0.0.jar
> lucene-core-4.0.0.jar
>
> Any advise on this is much appreciated?
>
> Thanks,
> Sai.
>
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Upgrade-Lucene-to-latest-version-4-0-from-2-4-0-tp4031956.html
> Sent from the Lucene - Java Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> For additional commands, e-mail: java-user-h...@lucene.apache.org
>
>




This message is for the sole use of the intended recipient(s) and may contain 
confidential and/or privileged information of Perimeter Internetworking Corp.  
Any unauthorized review, use, copying, disclosure, or distribution is 
prohibited.  If you are not the intended recipient, please immediately contact 
the sender by reply email and delete all copies of the original message.



--
 The sender of this email subscribes to Perimeter E-Security's email
 anti-virus service. This email has been scanned for malicious code and is
 believed to be virus free. For more information on email security please
 visit: http://www.perimeterusa.com/services/messaging
 This communication is confidential, intended only for the named recipient(s)
 above and may contain trade secrets or other information that is exempt from
 disclosure under applicable law. Any use, dissemination, distribution or
 copying of this communication by anyone other than the named recipient(s) is
 strictly prohibited. If you have received this communication in error, please
 delete the email and immediately notify our Command Center at 203-541-3444.

Reply via email to