# Are ELK stack components from the Downloads link compatible with each other? **URL:** \ **Category:** Elasticsearch\ **Created:** [May 28, 2014, 7:06pm UTC](https://discuss.elastic.co/t/are-elk-stack-components-from-the-downloads-link-compatible-with-each-other/17789 "2014-05-28T19:06:52Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![brian\_yoder](https://avatars.discourse-cdn.com/v4/letter/b/f1d935/32.png) [@brian\_yoder](https://discuss.elastic.co/u/brian_yoder)\ **Post date:** [May 28, 2014, 7:06pm UTC](https://discuss.elastic.co/t/are-elk-stack-components-from-the-downloads-link-compatible-with-each-other/17789/1 "2014-05-28T19:06:52Z")
Are versions of the ELK stack components compatible with each other as seen by the Elasticsearch Downloads link? Or do I need to specifically regress back to the older 1.1.1 ES version? From the following Downloads site [http://www.elasticsearch.org/overview/elkdownloads/](http://www.elasticsearch.org/overview/elkdownloads/) I downloaded the most recent versions of each of the ELK stack components. As Elasticsearch had been updated (the download site pointed to ES 1.2), I upgraded my local ES instance and then updated my Java server code for my other application. And I am trying to share the same ES version with my application and with ELK (keeping ES up to date is easier if I only need to focus on one version!). Then I looked inside logstash and I see it's still assuming ES 1.1.1 and the versions of Lucene are very different between the ES 1.2 version and logstash 1.4.1 version: _$ unzip -v logstash-1.4.1.zip | grep lucene_ logstash-1.4.1/vendor/jar/elasticsearch-1.1.1/lib/lucene-analyzers-common-4.7.2.jar logstash-1.4.1/vendor/jar/elasticsearch-1.1.1/lib/lucene-codecs-4.7.2.jar logstash-1.4.1/vendor/jar/elasticsearch-1.1.1/lib/_lucene-core-4.7.2_.jar logstash-1.4.1/vendor/jar/elasticsearch-1.1.1/lib/lucene-grouping-4.7.2.jar logstash-1.4.1/vendor/jar/elasticsearch-1.1.1/lib/lucene-highlighter-4.7.2.jar logstash-1.4.1/vendor/jar/elasticsearch-1.1.1/lib/lucene-join-4.7.2.jar logstash-1.4.1/vendor/jar/elasticsearch-1.1.1/lib/lucene-memory-4.7.2.jar logstash-1.4.1/vendor/jar/elasticsearch-1.1.1/lib/lucene-misc-4.7.2.jar logstash-1.4.1/vendor/jar/elasticsearch-1.1.1/lib/lucene-queries-4.7.2.jar logstash-1.4.1/vendor/jar/elasticsearch-1.1.1/lib/lucene-queryparser-4.7.2.jar logstash-1.4.1/vendor/jar/elasticsearch-1.1.1/lib/lucene-sandbox-4.7.2.jar logstash-1.4.1/vendor/jar/elasticsearch-1.1.1/lib/lucene-spatial-4.7.2.jar logstash-1.4.1/vendor/jar/elasticsearch-1.1.1/lib/lucene-suggest-4.7.2.jar logstash-1.4.1/vendor/kibana/app/panels/query/editors/lucene.html logstash-1.4.1/vendor/kibana/app/panels/query/help/lucene.html _$ unzip -v elasticsearch-1.2.0.zip | grep lucene_ elasticsearch-1.2.0/lib/lucene-codecs-4.8.1.jar elasticsearch-1.2.0/lib/_lucene-core-4.8.1_.jar elasticsearch-1.2.0/lib/lucene-analyzers-common-4.8.1.jar elasticsearch-1.2.0/lib/lucene-queries-4.8.1.jar elasticsearch-1.2.0/lib/lucene-memory-4.8.1.jar elasticsearch-1.2.0/lib/lucene-highlighter-4.8.1.jar elasticsearch-1.2.0/lib/lucene-queryparser-4.8.1.jar elasticsearch-1.2.0/lib/lucene-sandbox-4.8.1.jar elasticsearch-1.2.0/lib/lucene-suggest-4.8.1.jar elasticsearch-1.2.0/lib/lucene-misc-4.8.1.jar elasticsearch-1.2.0/lib/lucene-join-4.8.1.jar elasticsearch-1.2.0/lib/lucene-grouping-4.8.1.jar elasticsearch-1.2.0/lib/lucene-spatial-4.8.1.jar I only ask based on my reading of this newsgroup all about the many version issues with plug-ins. Up until now, I have never used a plug-in or a river, and instead keep my own Java code up-to-date and tested with each new release of ES. That way, I stomp version issues out of existence very early. Brian -- 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/d5cd0887-cf66-431a-94b5-403cbc0a1491%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d5cd0887-cf66-431a-94b5-403cbc0a1491%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:** [May 28, 2014, 10:07pm UTC](https://discuss.elastic.co/t/are-elk-stack-components-from-the-downloads-link-compatible-with-each-other/17789/2 "2014-05-28T22:07:50Z")
With LS in particular, you are better off using the HTTP output to ES so you are not locked into version compatibility requirements. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 29 May 2014 05:06, InquiringMind [brian.from.fl@gmail.com](mailto:brian.from.fl@gmail.com) wrote: > Are versions of the ELK stack components compatible with each other as > seen by the Elasticsearch Downloads link? Or do I need to specifically > regress back to the older 1.1.1 ES version? > > From the following Downloads site > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/overview/elkdownloads/) I downloaded the most > recent versions of each of the ELK stack components. As Elasticsearch had > been updated (the download site pointed to ES 1.2), I upgraded my local ES > instance and then updated my Java server code for my other application. And > I am trying to share the same ES version with my application and with ELK > (keeping ES up to date is easier if I only need to focus on one version!). > > Then I looked inside logstash and I see it's still assuming ES 1.1.1 and > the versions of Lucene are very different between the ES 1.2 version and > logstash 1.4.1 version: > > _$ unzip -v logstash-1.4.1.zip | grep lucene_ > > logstash-1.4.1/vendor/jar/elasticsearch-1.1.1/lib/lucene-analyzers-common-4.7.2.jar > logstash-1.4.1/vendor/jar/elasticsearch-1.1.1/lib/lucene-codecs-4.7.2.jar > logstash-1.4.1/vendor/jar/elasticsearch-1.1.1/lib/_lucene-core-4.7.2_ > .jar > > logstash-1.4.1/vendor/jar/elasticsearch-1.1.1/lib/lucene-grouping-4.7.2.jar > > logstash-1.4.1/vendor/jar/elasticsearch-1.1.1/lib/lucene-highlighter-4.7.2.jar > logstash-1.4.1/vendor/jar/elasticsearch-1.1.1/lib/lucene-join-4.7.2.jar > logstash-1.4.1/vendor/jar/elasticsearch-1.1.1/lib/lucene-memory-4.7.2.jar > logstash-1.4.1/vendor/jar/elasticsearch-1.1.1/lib/lucene-misc-4.7.2.jar > > logstash-1.4.1/vendor/jar/elasticsearch-1.1.1/lib/lucene-queries-4.7.2.jar > > logstash-1.4.1/vendor/jar/elasticsearch-1.1.1/lib/lucene-queryparser-4.7.2.jar > > logstash-1.4.1/vendor/jar/elasticsearch-1.1.1/lib/lucene-sandbox-4.7.2.jar > > logstash-1.4.1/vendor/jar/elasticsearch-1.1.1/lib/lucene-spatial-4.7.2.jar > > logstash-1.4.1/vendor/jar/elasticsearch-1.1.1/lib/lucene-suggest-4.7.2.jar > logstash-1.4.1/vendor/kibana/app/panels/query/editors/lucene.html > logstash-1.4.1/vendor/kibana/app/panels/query/help/lucene.html > > _$ unzip -v elasticsearch-1.2.0.zip | grep lucene_ > elasticsearch-1.2.0/lib/lucene-codecs-4.8.1.jar > elasticsearch-1.2.0/lib/_lucene-core-4.8.1_.jar > elasticsearch-1.2.0/lib/lucene-analyzers-common-4.8.1.jar > elasticsearch-1.2.0/lib/lucene-queries-4.8.1.jar > elasticsearch-1.2.0/lib/lucene-memory-4.8.1.jar > elasticsearch-1.2.0/lib/lucene-highlighter-4.8.1.jar > elasticsearch-1.2.0/lib/lucene-queryparser-4.8.1.jar > elasticsearch-1.2.0/lib/lucene-sandbox-4.8.1.jar > elasticsearch-1.2.0/lib/lucene-suggest-4.8.1.jar > elasticsearch-1.2.0/lib/lucene-misc-4.8.1.jar > elasticsearch-1.2.0/lib/lucene-join-4.8.1.jar > elasticsearch-1.2.0/lib/lucene-grouping-4.8.1.jar > elasticsearch-1.2.0/lib/lucene-spatial-4.8.1.jar > > I only ask based on my reading of this newsgroup all about the many > version issues with plug-ins. Up until now, I have never used a plug-in or > a river, and instead keep my own Java code up-to-date and tested with each > new release of ES. That way, I stomp version issues out of existence very > early. > > Brian > > -- > 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/d5cd0887-cf66-431a-94b5-403cbc0a1491%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d5cd0887-cf66-431a-94b5-403cbc0a1491%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/d5cd0887-cf66-431a-94b5-403cbc0a1491%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/d5cd0887-cf66-431a-94b5-403cbc0a1491%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/CAEM624YZ-F4gfUt8wBz\_ZLciiE4kSF-sZWE7UE7kUig%2BfO9oAg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624YZ-F4gfUt8wBz_ZLciiE4kSF-sZWE7UE7kUig%2BfO9oAg%40mail.gmail.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, 1:26am UTC](https://discuss.elastic.co/t/are-elk-stack-components-from-the-downloads-link-compatible-with-each-other/17789/3 "2017-07-06T01:26:15Z")