that’s an Elasticsearch limitation. You have to state the ES version the plugin is compiled against in the plugin’s descriptor file. Unfortunately, you cannot use wildcards or something similar. So, even if SG is code-compatible with a minor version upgrade of ES, we still have to change the descriptor file and provide a dedicated release.
You can find more infos about this topic directly from ES:
"Plugin release lifecycle
You will have to release a new version of the plugin for each new elasticsearch release. This version is checked when the plugin is loaded so Elasticsearch will refuse to start in the presence of plugins with the incorrect elasticsearch.version."
So, there’s nothing we can do about this from our side. Besides that, we need to test the plugin for each ES version before we release it. And last but not least, sometimes there are breaking changes even in minor version upgrades of ES.
Am Mittwoch, 1. Juni 2016 19:30:10 UTC+2 schrieb Ashu:
I would like to know that why Search Guard 2 is not backward compatible for even minor versions of Elasticsearch? Can you point some insights on it to understand better? What are the dependency out there that SG-2 cannot work with minor version changed ES?
Search Guard should consider it to support for at least minor versions of ES for backward compatible. Anyone has idea, when is Search Guard roll out a stable release for production deployment?