Adding elastiknn as an extension in the Elastic cloud fails with releases 8.4.2.1 and 8.4.3.0 about elastiknn HOT 4 CLOSED

I'm closing the issue because the problem is with the Elastic Cloud Extension UI, which is not currently able to parse version specifications like: java.version=17.

from elastiknn.

Very interesting! In case it helps further debug, here's the code that generates the properties file: https://github.com/alexklibisz/elastiknn/blob/main/project/ElasticsearchPluginPlugin.scala#L56-L64

I don't remember exactly, but I feel like I copied the java.version bit from their own gradle plugin: https://github.com/elastic/elasticsearch/blob/main/build-tools/src/main/java/org/elasticsearch/gradle/plugin/GeneratePluginPropertiesTask.java#L98

from elastiknn.

The support engineers of Elastic admitted that it was a bug on their side. I will try to manually set the value of java.version to 1.8 and repackage the plugin, to see if I can get it to work while waiting for a fix on their side.

The version policy of Elastic Cloud is very restrictive, it only allows deploying the latest patch release of a minor branch, so I can no longer deploy 8.4.2 while waiting for a fix to the java.version issue. Hopefully, setting java.version to 1.8 will work as a workaround.

from elastiknn.

For reference, the problem is due to an issue of the Elastic Cloud extensions UI in reading the size of the zip containing the extension. The workaround is to unzip the archive and re-zip it with the command line zip tool (tried in MacOS). So there was something that changed in the way the zip file is generated in version 8.4.2.1 that exposed this issue with Elastic Cloud.

from elastiknn.