We just went through this process. We simply copied the 1.2 index to the
new server (while the 1.2 server was live---responding to requests and
handling updates) and started it up with 1.3. It worked. I can't promise
that you'll have the same experience, but it's worth a try. Also, if I were
Hey,
I just want to copy over my indexes from my production server running
1.2 to another test server running 1.3. Since my Index are live I can't
just stop the it. I also have 5 GB of indexes so I do not know how long
I will need to take it down. All option I read backup the index
On Wed, Oct 1, 2008 at 10:28 PM, Michael Tedesco [EMAIL PROTECTED]wrote:
I just want to copy over my indexes from my production server running 1.2
to another test server running 1.3. Since my Index are live I can't just
stop the it. I also have 5 GB of indexes so I do not know how long I
Ok, I think I jumped the gun here. I'm not sure on this so I'll let someone
who knows more comment on this.
On Wed, Oct 1, 2008 at 11:03 PM, Shalin Shekhar Mangar
[EMAIL PROTECTED] wrote:
On Wed, Oct 1, 2008 at 10:28 PM, Michael Tedesco [EMAIL PROTECTED]wrote:
I just want to copy over my
Backup or snapshot taken by hard links are save to copy since once Lucene
creates an index file, it will not be modified.
From the 1.3.0 release notes:
The Porter snowball based stemmers in Lucene were updated (LUCENE-1142),
and are not guaranteed to be backward compatible at the index level
