# Feature request: importing/exporting index **URL:** \ **Category:** Elasticsearch\ **Created:** [October 4, 2011, 7:57pm UTC](https://discuss.elastic.co/t/feature-request-importing-exporting-index/5515 "2011-10-04T19:57:40Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Liyu](https://avatars.discourse-cdn.com/v4/letter/l/ba9def/32.png) [@Liyu](https://discuss.elastic.co/u/Liyu)\ **Post date:** [October 4, 2011, 7:57pm UTC](https://discuss.elastic.co/t/feature-request-importing-exporting-index/5515/1 "2011-10-04T19:57:40Z")
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. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [October 4, 2011, 8:29pm UTC](https://discuss.elastic.co/t/feature-request-importing-exporting-index/5515/2 "2011-10-04T20:29:07Z")
I would suggest to support this feature request : [[Feature Request] Add a river to ElasticSearch instance 路 Issue #1077 路 elastic/elasticsearch 路 GitHub](https://github.com/elasticsearch/elasticsearch/issues/1077) I think it would answer to your use case. David 馃槈 Le 4 oct. 2011 脿 21:57, Liyu [liyuyi@gmail.com](mailto: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. ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [October 4, 2011, 10:46pm UTC](https://discuss.elastic.co/t/feature-request-importing-exporting-index/5515/3 "2011-10-04T22:46:12Z")
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](mailto: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](https://github.com/elasticsearch/elasticsearch/issues/1077) > > I think it would answer to your use case. > > David 馃槈 > > Le 4 oct. 2011 脿 21:57, Liyu [liyuyi@gmail.com](mailto: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. ---
**Author:** ![Liyu](https://avatars.discourse-cdn.com/v4/letter/l/ba9def/32.png) [@Liyu](https://discuss.elastic.co/u/Liyu)\ **Post date:** [October 4, 2011, 11:39pm UTC](https://discuss.elastic.co/t/feature-request-importing-exporting-index/5515/4 "2011-10-04T23:39:44Z")
Awesome, I'll plan with this feature in :-). On Tue, Oct 4, 2011 at 3:46 PM, Shay Banon [kimchy@gmail.com](mailto: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](mailto: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](https://github.com/elasticsearch/elasticsearch/issues/1077) > > > > I think it would answer to your use case. > > > > David 馃槈 > > > > Le 4 oct. 2011 脿 21:57, Liyu [liyuyi@gmail.com](mailto: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. ---
**Author:** ![vineeth\_mohan](https://avatars.discourse-cdn.com/v4/letter/v/bc79bd/32.png) [@vineeth\_mohan](https://discuss.elastic.co/u/vineeth_mohan)\ **Post date:** [October 5, 2011, 2:58am UTC](https://discuss.elastic.co/t/feature-request-importing-exporting-index/5515/5 "2011-10-05T02:58:58Z")
Many of us are looking forward eagerly for this feature 馃檪 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](mailto: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](mailto: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](mailto: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](https://github.com/elasticsearch/elasticsearch/issues/1077) > > > > > > I think it would answer to your use case. > > > > > > David 馃槈 > > > > > > Le 4 oct. 2011 脿 21:57, Liyu [liyuyi@gmail.com](mailto: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. ---
**Author:** ![Gabriel\_Farrell](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gabriel_farrell/32/3337_2.png) [@Gabriel\_Farrell](https://discuss.elastic.co/u/Gabriel_Farrell)\ **Post date:** [October 5, 2011, 3:23am UTC](https://discuss.elastic.co/t/feature-request-importing-exporting-index/5515/6 "2011-10-05T03:23:43Z")
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](mailto:vineethmohan@algotree.com) wrote: > Many of us are looking forward eagerly for this feature 馃檪 > 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](mailto: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](mailto: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](mailto: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](https://github.com/elasticsearch/elasticsearch/issues/1077) > > > > > > > > I think it would answer to your use case. > > > > > > > > David 馃槈 > > > > > > > > Le 4 oct. 2011 脿 21:57, Liyu [liyuyi@gmail.com](mailto: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. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:52am UTC](https://discuss.elastic.co/t/feature-request-importing-exporting-index/5515/7 "2017-07-06T03:52:48Z")