Direct copying of indices seems like a huge anti-pattern. A complete no-no.
A top "DO NOT DO THIS". Here's why I think this:
When you copy an index you leave behind all the meta-data that made the
index interesting--the analyzers, transaction log, etc. You have bypassed
all of the nice machinery that was put into place expressly to handle this
scenario, ie. replication, which is the supported way to accomplish this.
(Well, it obviously doesn't do what you want so you are trying to bend
around it).
Perhaps the elasticsearch development folks could weigh in on this. But if
they ARE going to support this scenario a lot needs to be done as you have
discovered (what about updates that happen during the copy??). Rather than
writing JIRAs saying "support automatic discovery of copied indices" I
think it makes more sense to say: don't do that.
A plugin that takes data from one index and uses the actual APIs to insert
into a new one makes sense. Did not Jorg Prante write this?
On Wed, Aug 28, 2013 at 1:01 AM, Hanish Bansal <
hanish.bansal.agarwal@gmail.com> wrote:
Hi All,
I have two indexes(lets say tweetindex, tweetindex1) with same mapping and
same index type. I am copying all shards of first index into second index
directly.
For copying shards i am copying shards directories as:(for shard 0)
elasticsearch-0.90.0.RC2/data/eshh/nodes/0/indices/tweetindex/0 -->
elasticsearch-0.90.0.RC2/data/eshh/nodes/0/indices/tweetindex1/0
After restarting elasticsearch i am able to see data in second index.
But i do not want to restart elasticsearch. I have tried to
refresh,optimize the index so that data can be seen in second index but no
data was seen through rest client after refreshing and optimizing the index.
Is it possible to see data by directly copying in other index without
restart of elasticsearch ?
--
Thanks & Regards
Hanish Bansal
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
