Feature request: importing/exporting index

Elastic Stack Elasticsearch
1

Hey, ES is a great product. It would be really nice if the importing/
exporting index feature can be added. This is critical for data
archiving.

We'll have different SLAs between current data (in 2 years) and
history data. We hope to be able to serve the history data in a
different cluster.

2

I would suggest to support this feature request : [Feature Request] Add a river to ElasticSearch instance · Issue #1077 · elastic/elasticsearch · GitHub

I think it would answer to your use case.

David :wink:

Le 4 oct. 2011 à 21:57, Liyu liyuyi@gmail.com a écrit :

Hey, ES is a great product. It would be really nice if the importing/
exporting index feature can be added. This is critical for data
archiving.

We'll have different SLAs between current data (in 2 years) and
history data. We hope to be able to serve the history data in a
different cluster.

3

I agree, a way to support that is important. Not necessarily as a river as
explained in the issue (I personally don't see it as a river type
functionality)/

On Tue, Oct 4, 2011 at 10:29 PM, David Pilato david@pilato.fr wrote:

I would suggest to support this feature request :
[Feature Request] Add a river to ElasticSearch instance · Issue #1077 · elastic/elasticsearch · GitHub

I think it would answer to your use case.

David :wink:

Le 4 oct. 2011 à 21:57, Liyu liyuyi@gmail.com a écrit :

Hey, ES is a great product. It would be really nice if the importing/
exporting index feature can be added. This is critical for data
archiving.

We'll have different SLAs between current data (in 2 years) and
history data. We hope to be able to serve the history data in a
different cluster.

4

Awesome, I'll plan with this feature in :-).

On Tue, Oct 4, 2011 at 3:46 PM, Shay Banon kimchy@gmail.com wrote:

I agree, a way to support that is important. Not necessarily as a river as
explained in the issue (I personally don't see it as a river type
functionality)/

On Tue, Oct 4, 2011 at 10:29 PM, David Pilato david@pilato.fr wrote:

I would suggest to support this feature request :
[Feature Request] Add a river to ElasticSearch instance · Issue #1077 · elastic/elasticsearch · GitHub

I think it would answer to your use case.

David :wink:

Le 4 oct. 2011 à 21:57, Liyu liyuyi@gmail.com a écrit :

Hey, ES is a great product. It would be really nice if the importing/
exporting index feature can be added. This is critical for data
archiving.

We'll have different SLAs between current data (in 2 years) and
history data. We hope to be able to serve the history data in a
different cluster.

5

Many of us are looking forward eagerly for this feature :slight_smile:
Business continuation plans and archiving plans can be easily implemented
with this feature intact.

Thanks
Vineeth

On Wed, Oct 5, 2011 at 5:09 AM, Liyu Yi liyuyi@gmail.com wrote:

Awesome, I'll plan with this feature in :-).

On Tue, Oct 4, 2011 at 3:46 PM, Shay Banon kimchy@gmail.com wrote:

I agree, a way to support that is important. Not necessarily as a river as
explained in the issue (I personally don't see it as a river type
functionality)/

On Tue, Oct 4, 2011 at 10:29 PM, David Pilato david@pilato.fr wrote:

I would suggest to support this feature request :
[Feature Request] Add a river to ElasticSearch instance · Issue #1077 · elastic/elasticsearch · GitHub

I think it would answer to your use case.

David :wink:

Le 4 oct. 2011 à 21:57, Liyu liyuyi@gmail.com a écrit :

Hey, ES is a great product. It would be really nice if the importing/
exporting index feature can be added. This is critical for data
archiving.

We'll have different SLAs between current data (in 2 years) and
history data. We hope to be able to serve the history data in a
different cluster.

6

Also, as Shay suggested in the thread mentioned in that issue, export
can be implemented at present via the scan API.

On Tue, Oct 4, 2011 at 10:58 PM, Vineeth Mohan
vineethmohan@algotree.com wrote:

Many of us are looking forward eagerly for this feature :slight_smile:
Business continuation plans and archiving plans can be easily implemented
with this feature intact.

Thanks
Vineeth

On Wed, Oct 5, 2011 at 5:09 AM, Liyu Yi liyuyi@gmail.com wrote:

Awesome, I'll plan with this feature in :-).

On Tue, Oct 4, 2011 at 3:46 PM, Shay Banon kimchy@gmail.com wrote:

I agree, a way to support that is important. Not necessarily as a river
as explained in the issue (I personally don't see it as a river type
functionality)/

On Tue, Oct 4, 2011 at 10:29 PM, David Pilato david@pilato.fr wrote:

I would suggest to support this feature request :
[Feature Request] Add a river to ElasticSearch instance · Issue #1077 · elastic/elasticsearch · GitHub

I think it would answer to your use case.

David :wink:

Le 4 oct. 2011 à 21:57, Liyu liyuyi@gmail.com a écrit :

Hey, ES is a great product. It would be really nice if the importing/
exporting index feature can be added. This is critical for data
archiving.

We'll have different SLAs between current data (in 2 years) and
history data. We hope to be able to serve the history data in a
different cluster.