# Downgrading from 1.4 to1.3 **URL:** \ **Category:** Elasticsearch\ **Created:** [December 3, 2014, 8:53pm UTC](https://discuss.elastic.co/t/downgrading-from-1-4-to1-3/21069 "2014-12-03T20:53:02Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![Jack\_Judge](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jack_judge/32/85499_2.png) [@Jack\_Judge](https://discuss.elastic.co/u/Jack_Judge)\ **Post date:** [December 3, 2014, 8:53pm UTC](https://discuss.elastic.co/t/downgrading-from-1-4-to1-3/21069/1 "2014-12-03T20:53:02Z")
"Upgrading" to 1.4 has been a clusterfuck for us. It's broken pretty much everything we rely on. I need to go back to 1.3, can I use the snapshot feature? Will a snapshot taken on a 1.4 cluster restore to a separate 1.3 cluster ? I'm really just interested in the data, I'd like to reapply my own mappings as the data is ingested into 1.3 Should I be looking at a third party script or will the snapshot/restore features of elastic search be adequate ? -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/cd99a5a2-d9a0-4bdf-ae4f-efe054ba8ebd%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/cd99a5a2-d9a0-4bdf-ae4f-efe054ba8ebd%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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:** [December 3, 2014, 8:56pm UTC](https://discuss.elastic.co/t/downgrading-from-1-4-to1-3/21069/2 "2014-12-03T20:56:20Z")
No. A snapshot done on 1.4 won’t work in 1.3. It might work only if no other indexation operation happened and no merge. But that said, what is your concern with 1.4? -- David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > Le 3 déc. 2014 à 21:53, Jack Judge [jackjudge01@gmail.com](mailto:jackjudge01@gmail.com) a écrit : > > "Upgrading" to 1.4 has been a clusterfuck for us. It's broken pretty much everything we rely on. I need to go back to 1.3, can I use the snapshot feature? > Will a snapshot taken on a 1.4 cluster restore to a separate 1.3 cluster ? > > I'm really just interested in the data, I'd like to reapply my own mappings as the data is ingested into 1.3 > Should I be looking at a third party script or will the snapshot/restore features of Elasticsearch be adequate ? > > -- > 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](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/cd99a5a2-d9a0-4bdf-ae4f-efe054ba8ebd%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/cd99a5a2-d9a0-4bdf-ae4f-efe054ba8ebd%40googlegroups.com). > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/F009E6E5-4056-497C-B414-DA02D4CC1993%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/F009E6E5-4056-497C-B414-DA02D4CC1993%40pilato.fr). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\ **Post date:** [December 3, 2014, 8:56pm UTC](https://discuss.elastic.co/t/downgrading-from-1-4-to1-3/21069/3 "2014-12-03T20:56:31Z")
I'm pretty sure you can't due to different Lucene versions. I wouldn't even try - just export and re-index. I will be more than happy to hear about what went wrong for you with upgrading? -- Itamar Syn-Hershko [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko) Freelance Developer & Consultant Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/) On Wed, Dec 3, 2014 at 10:53 PM, Jack Judge [jackjudge01@gmail.com](mailto:jackjudge01@gmail.com) wrote: > "Upgrading" to 1.4 has been a clusterfuck for us. It's broken pretty much > everything we rely on. I need to go back to 1.3, can I use the snapshot > feature? > Will a snapshot taken on a 1.4 cluster restore to a separate 1.3 cluster ? > > I'm really just interested in the data, I'd like to reapply my own > mappings as the data is ingested into 1.3 > Should I be looking at a third party script or will the snapshot/restore > features of Elasticsearch be adequate ? > > -- > 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](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/cd99a5a2-d9a0-4bdf-ae4f-efe054ba8ebd%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/cd99a5a2-d9a0-4bdf-ae4f-efe054ba8ebd%40googlegroups.com) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZtKDnvjrv9sU0aAJdab5tTtBP08jB%2BJ9fOiRgtyHbYf9A%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZtKDnvjrv9sU0aAJdab5tTtBP08jB%2BJ9fOiRgtyHbYf9A%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Jack\_Judge](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jack_judge/32/85499_2.png) [@Jack\_Judge](https://discuss.elastic.co/u/Jack_Judge)\ **Post date:** [December 3, 2014, 10:12pm UTC](https://discuss.elastic.co/t/downgrading-from-1-4-to1-3/21069/4 "2014-12-03T22:12:19Z")
> I will be more than happy to hear about what went wrong for you with > upgrading? Well Kibana 4 is unusable for us, the lack of auto refresh killed it for us. Most of the time K4 simply doesn't work even for browsing small sets, I'd say 2 times in 3 we get the 300000 ms timeout error, is there a solution to this yet ? And when we finally do get any results it's as slow as a pig on crutches. I need to go back to my old K3 dashboards, but after fighting thru the CORS "features", I find they're all blank. There's no errors, just no data and I desperately need them. I also need my old Packetbeat dashboards. From my googling I think the quickest way to get them back is to downgrade ES from 1.4 to 1.3, or am I wrong ? So, I need a way to export the data from the indices to a new cluster. My systems are in a secure environment, I can't use anything that needs to connect out to the interrnet during compile / install time, so the node.js / npm stuff is locked out for me. I tried the knapsack plugin but it doesn't seem to work installed into an ES 1.4 cluster. -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/3b3ba0ec-d84e-4a90-920c-997bce89c847%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/3b3ba0ec-d84e-4a90-920c-997bce89c847%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\ **Post date:** [December 3, 2014, 10:17pm UTC](https://discuss.elastic.co/t/downgrading-from-1-4-to1-3/21069/5 "2014-12-03T22:17:29Z")
I'm a bit confused. Are you downgrading just because of Kibana compat issues? seems to me like killing a fly with a bazooka. Enabling CORS and using K3 dashboards seem like the better solution to me, for now. K4 isn't even officially released yet. As for data disappearing, I'm sure it wasn't and a relaxed debugging session can help you find that. As for export-import - yes, knapsack is a great option but it does make sense Joerg hasn't updated it yet as its not officially maintained. Writing your own export-import tool is an easy option; I'd also look at [GitHub - elastic/stream2es: Stream data into ES (Wikipedia, Twitter, stdin, or other ESes)](https://github.com/elasticsearch/stream2es) , [GitHub - elasticsearch-dump/elasticsearch-dump: Import and export tools for elasticsearch & opensearch](https://github.com/taskrabbit/elasticsearch-dump) -- Itamar Syn-Hershko [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko) Freelance Developer & Consultant Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/) On Thu, Dec 4, 2014 at 12:12 AM, Jack Judge [jackjudge01@gmail.com](mailto:jackjudge01@gmail.com) wrote: > > I will be more than happy to hear about what went wrong for you with > > upgrading? > > Well Kibana 4 is unusable for us, the lack of auto refresh killed it for > us. > Most of the time K4 simply doesn't work even for browsing small sets, I'd > say 2 times in 3 we get the 300000 ms timeout error, is there a solution to > this yet ? > And when we finally do get any results it's as slow as a pig on crutches. > > I need to go back to my old K3 dashboards, but after fighting thru the > CORS "features", I find they're all blank. There's no errors, just no data > and I desperately need them. > I also need my old Packetbeat dashboards. > > From my googling I think the quickest way to get them back is to downgrade > ES from 1.4 to 1.3, or am I wrong ? > > So, I need a way to export the data from the indices to a new cluster. My > systems are in a secure environment, I can't use anything that needs to > connect out to the interrnet during compile / install time, so the node.js > / npm stuff is locked out for me. > I tried the knapsack plugin but it doesn't seem to work installed into an > ES 1.4 cluster. > > -- > 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](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/3b3ba0ec-d84e-4a90-920c-997bce89c847%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/3b3ba0ec-d84e-4a90-920c-997bce89c847%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/3b3ba0ec-d84e-4a90-920c-997bce89c847%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/3b3ba0ec-d84e-4a90-920c-997bce89c847%40googlegroups.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAHTr4Zt-r2XQVGhDQ%2Bthqnt6hxavObpTcM%3DUkj-j27JLeRA\_3A%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHTr4Zt-r2XQVGhDQ%2Bthqnt6hxavObpTcM%3DUkj-j27JLeRA_3A%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Jack\_Judge](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jack_judge/32/85499_2.png) [@Jack\_Judge](https://discuss.elastic.co/u/Jack_Judge)\ **Post date:** [December 3, 2014, 11:44pm UTC](https://discuss.elastic.co/t/downgrading-from-1-4-to1-3/21069/6 "2014-12-03T23:44:45Z")
Well you say "just", but at the moment Kibana is our only view into the ES cluster, so yes it's a dealbreaker for us. After enabling CORS, and what an unexpected knock about of pure fun that was, I still can't use the K3 dashboards, they're blank, no data, no errors just empty dashboards ☹ Data isn't disappearing, I can still see it via the "head" plugin So what's the quickest way of being able to see my data via the K3 boards ? Is it exporting out into a new cluster ? Or is there a way to make them work with the ES 1.4 cluster ? JJ .On Wednesday, 3 December 2014 14:17:39 UTC-8, Itamar Syn-Hershko wrote: > I'm a bit confused. Are you downgrading just because of Kibana compat > issues? seems to me like killing a fly with a bazooka. > > Enabling CORS and using K3 dashboards seem like the better solution to me, > for now. K4 isn't even officially released yet. As for data disappearing, > I'm sure it wasn't and a relaxed debugging session can help you find that. > > As for export-import - yes, knapsack is a great option but it does make > sense Joerg hasn't updated it yet as its not officially maintained. Writing > your own export-import tool is an easy option; I'd also look at > [GitHub - elastic/stream2es: Stream data into ES (Wikipedia, Twitter, stdin, or other ESes)](https://github.com/elasticsearch/stream2es) , > [GitHub - elasticsearch-dump/elasticsearch-dump: Import and export tools for elasticsearch & opensearch](https://github.com/taskrabbit/elasticsearch-dump) > > -- > > Itamar Syn-Hershko > [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko) > Freelance Developer & Consultant > Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/) > > On Thu, Dec 4, 2014 at 12:12 AM, Jack Judge \<[jackj...@gmail.com](mailto:jackj...@gmail.com) > \\> wrote: > > > > I will be more than happy to hear about what went wrong for you with > > > upgrading? > > > > Well Kibana 4 is unusable for us, the lack of auto refresh killed it for > > us. > > Most of the time K4 simply doesn't work even for browsing small sets, I'd > > say 2 times in 3 we get the 300000 ms timeout error, is there a solution to > > this yet ? > > And when we finally do get any results it's as slow as a pig on crutches. > > > > I need to go back to my old K3 dashboards, but after fighting thru the > > CORS "features", I find they're all blank. There's no errors, just no data > > and I desperately need them. > > I also need my old Packetbeat dashboards. > > > > From my googling I think the quickest way to get them back is to > > downgrade ES from 1.4 to 1.3, or am I wrong ? > > > > So, I need a way to export the data from the indices to a new cluster. My > > systems are in a secure environment, I can't use anything that needs to > > connect out to the interrnet during compile / install time, so the node.js > > / npm stuff is locked out for me. > > I tried the knapsack plugin but it doesn't seem to work installed into an > > ES 1.4 cluster. > > > > -- > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/3b3ba0ec-d84e-4a90-920c-997bce89c847%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/3b3ba0ec-d84e-4a90-920c-997bce89c847%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/3b3ba0ec-d84e-4a90-920c-997bce89c847%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/3b3ba0ec-d84e-4a90-920c-997bce89c847%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/803bd821-95e8-4e29-8f0a-b2df813e204f%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/803bd821-95e8-4e29-8f0a-b2df813e204f%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\ **Post date:** [December 3, 2014, 11:48pm UTC](https://discuss.elastic.co/t/downgrading-from-1-4-to1-3/21069/7 "2014-12-03T23:48:22Z")
I'm not aware of compat issues with K3 and ES 1.4 other than [Kibana 3 & Elasticsearch 1.4.0 beta 1 · Issue #1637 · elastic/kibana · GitHub](https://github.com/elasticsearch/kibana/issues/1637) . I'd check for javascript errors, and try to see what's going on under the hood, really. When you have more data about this, you can either quickly resolve, or open a concrete bug 🙂 -- Itamar Syn-Hershko [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko) Freelance Developer & Consultant Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/) On Thu, Dec 4, 2014 at 1:44 AM, Jack Judge [jackjudge01@gmail.com](mailto:jackjudge01@gmail.com) wrote: > Well you say "just", but at the moment Kibana is our only view into the ES > cluster, so yes it's a dealbreaker for us. > > After enabling CORS, and what an unexpected knock about of pure fun that > was, I still can't use the K3 dashboards, they're blank, no data, no errors > just empty dashboards ☹ > Data isn't disappearing, I can still see it via the "head" plugin > > So what's the quickest way of being able to see my data via the K3 boards > ? Is it exporting out into a new cluster ? Or is there a way to make them > work with the ES 1.4 cluster ? > > JJ > > .On Wednesday, 3 December 2014 14:17:39 UTC-8, Itamar Syn-Hershko wrote: > > > I'm a bit confused. Are you downgrading just because of Kibana compat > > issues? seems to me like killing a fly with a bazooka. > > > > Enabling CORS and using K3 dashboards seem like the better solution to > > me, for now. K4 isn't even officially released yet. As for data > > disappearing, I'm sure it wasn't and a relaxed debugging session can help > > you find that. > > > > As for export-import - yes, knapsack is a great option but it does make > > sense Joerg hasn't updated it yet as its not officially maintained. Writing > > your own export-import tool is an easy option; I'd also look at > > [GitHub - elastic/stream2es: Stream data into ES (Wikipedia, Twitter, stdin, or other ESes)](https://github.com/elasticsearch/stream2es) , [https://github.com/](https://github.com/) > > taskrabbit/elasticsearch-dump > > > > -- > > > > Itamar Syn-Hershko > > [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko) > > Freelance Developer & Consultant > > Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/) > > > > On Thu, Dec 4, 2014 at 12:12 AM, Jack Judge [jackj...@gmail.com](mailto:jackj...@gmail.com) wrote: > > > > > > I will be more than happy to hear about what went wrong for you with > > > > upgrading? > > > > > > Well Kibana 4 is unusable for us, the lack of auto refresh killed it for > > > us. > > > Most of the time K4 simply doesn't work even for browsing small sets, > > > I'd say 2 times in 3 we get the 300000 ms timeout error, is there a > > > solution to this yet ? > > > And when we finally do get any results it's as slow as a pig on crutches. > > > > > > I need to go back to my old K3 dashboards, but after fighting thru the > > > CORS "features", I find they're all blank. There's no errors, just no data > > > and I desperately need them. > > > I also need my old Packetbeat dashboards. > > > > > > From my googling I think the quickest way to get them back is to > > > downgrade ES from 1.4 to 1.3, or am I wrong ? > > > > > > So, I need a way to export the data from the indices to a new cluster. > > > My systems are in a secure environment, I can't use anything that needs to > > > connect out to the interrnet during compile / install time, so the node.js > > > / npm stuff is locked out for me. > > > I tried the knapsack plugin but it doesn't seem to work installed into > > > an ES 1.4 cluster. > > > > > > -- > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > msgid/elasticsearch/3b3ba0ec-d84e-4a90-920c-997bce89c847% > > > [40googlegroups.com](http://40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/3b3ba0ec-d84e-4a90-920c-997bce89c847%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/3b3ba0ec-d84e-4a90-920c-997bce89c847%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > 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](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/803bd821-95e8-4e29-8f0a-b2df813e204f%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/803bd821-95e8-4e29-8f0a-b2df813e204f%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/803bd821-95e8-4e29-8f0a-b2df813e204f%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/803bd821-95e8-4e29-8f0a-b2df813e204f%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZuOEEn\_5\_AQt9SKk3JAFmTnjq1afA9PAkP77aDmOLgLCg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZuOEEn_5_AQt9SKk3JAFmTnjq1afA9PAkP77aDmOLgLCg%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Jack\_Judge](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jack_judge/32/85499_2.png) [@Jack\_Judge](https://discuss.elastic.co/u/Jack_Judge)\ **Post date:** [December 4, 2014, 1:20am UTC](https://discuss.elastic.co/t/downgrading-from-1-4-to1-3/21069/8 "2014-12-04T01:20:25Z")
Well you're right there's JS errors, CORS related; XMLHttpRequest cannot load [http://10.5.41.120:9200/logstash-2014.12.04/\_search](http://10.5.41.120:9200/logstash-2014.12.04/_search). Request header field Content-Type is not allowed by Access-Control-Allow-Headers. In my elasticsearch.yml I've got this on all nodes, http.cors.allow-origin: "/.\*/" http.cors.enabled: true Which google leads me to believe should open it up for anything. K3 is fronted by apache and a bit more googling prompted me to add this to the section of httpd.conf Header set Access-Control-Allow-Origin "\*" Still getting the same errors ☹ I'm at a loss to know what else to do now. On Wednesday, 3 December 2014 15:48:28 UTC-8, Itamar Syn-Hershko wrote: > I'm not aware of compat issues with K3 and ES 1.4 other than > [Kibana 3 & Elasticsearch 1.4.0 beta 1 · Issue #1637 · elastic/kibana · GitHub](https://github.com/elasticsearch/kibana/issues/1637) . I'd check for > javascript errors, and try to see what's going on under the hood, really. > When you have more data about this, you can either quickly resolve, or open > a concrete bug 🙂 -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/19d57d39-b764-493c-bd60-c8ae3aff087a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/19d57d39-b764-493c-bd60-c8ae3aff087a%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\ **Post date:** [December 4, 2014, 3:40pm UTC](https://discuss.elastic.co/t/downgrading-from-1-4-to1-3/21069/9 "2014-12-04T15:40:36Z")
Classic CORS error - maybe \* is blocked by ES. Haven't had to deal with this myself (yet) so can't help you here. All in all just a small rough edge to smooth, not a clusterfuck. A quick solution would be to install K3 as a site plugin and use it internally (don't expose it to the web) -- Itamar Syn-Hershko [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko) Freelance Developer & Consultant Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/) On Thu, Dec 4, 2014 at 3:20 AM, Jack Judge [jackjudge01@gmail.com](mailto:jackjudge01@gmail.com) wrote: > Well you're right there's JS errors, CORS related; > > XMLHttpRequest cannot load > [http://10.5.41.120:9200/logstash-2014.12.04/\_search](http://10.5.41.120:9200/logstash-2014.12.04/_search). Request header field > Content-Type is not allowed by Access-Control-Allow-Headers. > > In my elasticsearch.yml I've got this on all nodes, > > http.cors.allow-origin: "/.\*/" > http.cors.enabled: true > > Which google leads me to believe should open it up for anything. K3 is > fronted by apache and a bit more googling prompted me to add this to the > section of httpd.conf > > Header set Access-Control-Allow-Origin "\*" > > Still getting the same errors ☹ > I'm at a loss to know what else to do now. > > On Wednesday, 3 December 2014 15:48:28 UTC-8, Itamar Syn-Hershko wrote: > > > I'm not aware of compat issues with K3 and ES 1.4 other than > > [Kibana 3 & Elasticsearch 1.4.0 beta 1 · Issue #1637 · elastic/kibana · GitHub](https://github.com/elasticsearch/kibana/issues/1637) . I'd check for > > javascript errors, and try to see what's going on under the hood, really. > > When you have more data about this, you can either quickly resolve, or open > > a concrete bug 🙂 > > > > -- > > 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](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/19d57d39-b764-493c-bd60-c8ae3aff087a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/19d57d39-b764-493c-bd60-c8ae3aff087a%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/19d57d39-b764-493c-bd60-c8ae3aff087a%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/19d57d39-b764-493c-bd60-c8ae3aff087a%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZsXoVG%3DqYm8\_0RC0H1%3DtWQfBtXhOScv6bjwKN9winF4cQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZsXoVG%3DqYm8_0RC0H1%3DtWQfBtXhOScv6bjwKN9winF4cQ%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Jack\_Judge](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jack_judge/32/85499_2.png) [@Jack\_Judge](https://discuss.elastic.co/u/Jack_Judge)\ **Post date:** [December 4, 2014, 10:29pm UTC](https://discuss.elastic.co/t/downgrading-from-1-4-to1-3/21069/10 "2014-12-04T22:29:45Z")
Wrong in every fundamental aspect. This was a clusterfuck and still is. The K3 dashboards are used by our devs, network guys and management for a variety of tasks. When they stopped working we lost sight of large parts of our operation. Because of the lack of documentation and the time pressure, I don't have the luxury of sitting down, picking up a coffee and learning all about CORS, so yeah we've downgraded back to 1.3 Unless you know how to fix it, which I don't, then this is a clusterfuck, it rendered our system useless to us. On Thursday, 4 December 2014 07:40:47 UTC-8, Itamar Syn-Hershko wrote: > Classic CORS error - maybe \* is blocked by ES. Haven't had to deal with > this myself (yet) so can't help you here. All in all just a small rough > edge to smooth, not a clusterfuck. > > A quick solution would be to install K3 as a site plugin and use it > internally (don't expose it to the web) > > -- > > Itamar Syn-Hershko > [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko) > Freelance Developer & Consultant > Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/) > > On Thu, Dec 4, 2014 at 3:20 AM, Jack Judge \<[jackj...@gmail.com](mailto:jackj...@gmail.com) > \\> wrote: > > > Well you're right there's JS errors, CORS related; > > > > XMLHttpRequest cannot load > > [http://10.5.41.120:9200/logstash-2014.12.04/\_search](http://10.5.41.120:9200/logstash-2014.12.04/_search). Request header > > field Content-Type is not allowed by Access-Control-Allow-Headers. > > > > In my elasticsearch.yml I've got this on all nodes, > > > > http.cors.allow-origin: "/.\*/" > > http.cors.enabled: true > > > > Which google leads me to believe should open it up for anything. K3 is > > fronted by apache and a bit more googling prompted me to add this to the > > section of httpd.conf > > > > Header set Access-Control-Allow-Origin "\*" > > > > Still getting the same errors ☹ > > I'm at a loss to know what else to do now. > > > > On Wednesday, 3 December 2014 15:48:28 UTC-8, Itamar Syn-Hershko wrote: > > > > > I'm not aware of compat issues with K3 and ES 1.4 other than > > > [Kibana 3 & Elasticsearch 1.4.0 beta 1 · Issue #1637 · elastic/kibana · GitHub](https://github.com/elasticsearch/kibana/issues/1637) . I'd check for > > > javascript errors, and try to see what's going on under the hood, really. > > > When you have more data about this, you can either quickly resolve, or open > > > a concrete bug 🙂 > > > > > > -- > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/19d57d39-b764-493c-bd60-c8ae3aff087a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/19d57d39-b764-493c-bd60-c8ae3aff087a%40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/19d57d39-b764-493c-bd60-c8ae3aff087a%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/19d57d39-b764-493c-bd60-c8ae3aff087a%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/feb498f7-b7aa-424b-b839-66445019d204%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/feb498f7-b7aa-424b-b839-66445019d204%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [December 5, 2014, 12:23am UTC](https://discuss.elastic.co/t/downgrading-from-1-4-to1-3/21069/11 "2014-12-05T00:23:40Z")
This is why it's good to test before rolling out to critical platforms. On 5 December 2014 at 09:29, Jack Judge [jackjudge01@gmail.com](mailto:jackjudge01@gmail.com) wrote: > Wrong in every fundamental aspect. > > This was a clusterfuck and still is. The K3 dashboards are used by our > devs, network guys and management for a variety of tasks. When they stopped > working we lost sight of large parts of our operation. > Because of the lack of documentation and the time pressure, I don't have > the luxury of sitting down, picking up a coffee and learning all about > CORS, so yeah we've downgraded back to 1.3 > > Unless you know how to fix it, which I don't, then this is a clusterfuck, > it rendered our system useless to us. > > On Thursday, 4 December 2014 07:40:47 UTC-8, Itamar Syn-Hershko wrote: > > > Classic CORS error - maybe \* is blocked by ES. Haven't had to deal with > > this myself (yet) so can't help you here. All in all just a small rough > > edge to smooth, not a clusterfuck. > > > > A quick solution would be to install K3 as a site plugin and use it > > internally (don't expose it to the web) > > > > -- > > > > Itamar Syn-Hershko > > [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko) > > Freelance Developer & Consultant > > Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/) > > > > On Thu, Dec 4, 2014 at 3:20 AM, Jack Judge [jackj...@gmail.com](mailto:jackj...@gmail.com) wrote: > > > > > Well you're right there's JS errors, CORS related; > > > > > > XMLHttpRequest cannot load [http://10.5.41.120:9200/](http://10.5.41.120:9200/) > > > logstash-2014.12.04/\_search. Request header field Content-Type is not > > > allowed by Access-Control-Allow-Headers. > > > > > > In my elasticsearch.yml I've got this on all nodes, > > > > > > http.cors.allow-origin: "/.\*/" > > > http.cors.enabled: true > > > > > > Which google leads me to believe should open it up for anything. K3 is > > > fronted by apache and a bit more googling prompted me to add this to the > > > section of httpd.conf > > > > > > Header set Access-Control-Allow-Origin "\*" > > > > > > Still getting the same errors ☹ > > > I'm at a loss to know what else to do now. > > > > > > On Wednesday, 3 December 2014 15:48:28 UTC-8, Itamar Syn-Hershko wrote: > > > > > > > I'm not aware of compat issues with K3 and ES 1.4 other than > > > > [Kibana 3 & Elasticsearch 1.4.0 beta 1 · Issue #1637 · elastic/kibana · GitHub](https://github.com/elasticsearch/kibana/issues/1637) . I'd check for > > > > javascript errors, and try to see what's going on under the hood, really. > > > > When you have more data about this, you can either quickly resolve, or open > > > > a concrete bug 🙂 > > > > > > > > -- > > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > > msgid/elasticsearch/19d57d39-b764-493c-bd60-c8ae3aff087a% > > > > [40googlegroups.com](http://40googlegroups.com) > > > > [https://groups.google.com/d/msgid/elasticsearch/19d57d39-b764-493c-bd60-c8ae3aff087a%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/19d57d39-b764-493c-bd60-c8ae3aff087a%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > . > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > 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](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/feb498f7-b7aa-424b-b839-66445019d204%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/feb498f7-b7aa-424b-b839-66445019d204%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/feb498f7-b7aa-424b-b839-66445019d204%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/feb498f7-b7aa-424b-b839-66445019d204%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8SAOhM8NC4b0vR1njMKai4hwKethKnj267yhySoaK6Xw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8SAOhM8NC4b0vR1njMKai4hwKethKnj267yhySoaK6Xw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Jack\_Judge](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jack_judge/32/85499_2.png) [@Jack\_Judge](https://discuss.elastic.co/u/Jack_Judge)\ **Post date:** [December 5, 2014, 9:43pm UTC](https://discuss.elastic.co/t/downgrading-from-1-4-to1-3/21069/12 "2014-12-05T21:43:45Z")
I know, I'm kicking myself for this. TBH my thinking was along the lines of "new dashboards! - new kibana but that's okay it's works on it's own server, K3 dashboards will still work - oh, ES update required, well new kibana index needed so that explains that - oh fuck...what the hell is CORS ? can i back out ? why the fuck wasn't this highlighted in the release notes, i mean in big glowing letters as in THIS WILL BREAK YOUR EXISTING SETUP Those were my thoughts, more or less. On Thursday, 4 December 2014 16:24:09 UTC-8, Mark Walkom wrote: > This is why it's good to test before rolling out to critical platforms. > > On 5 December 2014 at 09:29, Jack Judge \<[jackj...@gmail.com](mailto:jackj...@gmail.com) \\> > wrote: > > > Wrong in every fundamental aspect. > > > > This was a clusterfuck and still is. The K3 dashboards are used by our > > devs, network guys and management for a variety of tasks. When they stopped > > working we lost sight of large parts of our operation. > > Because of the lack of documentation and the time pressure, I don't have > > the luxury of sitting down, picking up a coffee and learning all about > > CORS, so yeah we've downgraded back to 1.3 > > > > Unless you know how to fix it, which I don't, then this is a clusterfuck, > > it rendered our system useless to us. > > > > On Thursday, 4 December 2014 07:40:47 UTC-8, Itamar Syn-Hershko wrote: > > > > > Classic CORS error - maybe \* is blocked by ES. Haven't had to deal with > > > this myself (yet) so can't help you here. All in all just a small rough > > > edge to smooth, not a clusterfuck. > > > > > > A quick solution would be to install K3 as a site plugin and use it > > > internally (don't expose it to the web) > > > > > > -- > > > > > > Itamar Syn-Hershko > > > [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko) > > > Freelance Developer & Consultant > > > Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/) > > > > > > On Thu, Dec 4, 2014 at 3:20 AM, Jack Judge [jackj...@gmail.com](mailto:jackj...@gmail.com) wrote: > > > > > > > Well you're right there's JS errors, CORS related; > > > > > > > > XMLHttpRequest cannot load [http://10.5.41.120:9200/](http://10.5.41.120:9200/) > > > > logstash-2014.12.04/\_search. Request header field Content-Type is not > > > > allowed by Access-Control-Allow-Headers. > > > > > > > > In my elasticsearch.yml I've got this on all nodes, > > > > > > > > http.cors.allow-origin: "/.\*/" > > > > http.cors.enabled: true > > > > > > > > Which google leads me to believe should open it up for anything. K3 is > > > > fronted by apache and a bit more googling prompted me to add this to the > > > > section of httpd.conf > > > > > > > > Header set Access-Control-Allow-Origin "\*" > > > > > > > > Still getting the same errors ☹ > > > > I'm at a loss to know what else to do now. > > > > > > > > On Wednesday, 3 December 2014 15:48:28 UTC-8, Itamar Syn-Hershko wrote: > > > > > > > > > I'm not aware of compat issues with K3 and ES 1.4 other than > > > > > [Kibana 3 & Elasticsearch 1.4.0 beta 1 · Issue #1637 · elastic/kibana · GitHub](https://github.com/elasticsearch/kibana/issues/1637) . I'd check for > > > > > javascript errors, and try to see what's going on under the hood, really. > > > > > When you have more data about this, you can either quickly resolve, or open > > > > > a concrete bug 🙂 > > > > > > > > > > -- > > > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > > > msgid/elasticsearch/19d57d39-b764-493c-bd60-c8ae3aff087a% > > > > > [40googlegroups.com](http://40googlegroups.com) > > > > > [https://groups.google.com/d/msgid/elasticsearch/19d57d39-b764-493c-bd60-c8ae3aff087a%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/19d57d39-b764-493c-bd60-c8ae3aff087a%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > > . > > > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > -- > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/feb498f7-b7aa-424b-b839-66445019d204%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/feb498f7-b7aa-424b-b839-66445019d204%40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/feb498f7-b7aa-424b-b839-66445019d204%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/feb498f7-b7aa-424b-b839-66445019d204%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/bad37880-3d7d-4a7b-ba0d-eddff3a36fe9%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/bad37880-3d7d-4a7b-ba0d-eddff3a36fe9%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 12:45am UTC](https://discuss.elastic.co/t/downgrading-from-1-4-to1-3/21069/13 "2017-07-06T00:45:24Z")