The new product version check rejects oss distributions?

[RTodorov]

💬 Questions and Help

@delvedor Is there a reason why the new product version check introduced in 7.14.0 doesn't accept distributions with oss as flavor?

https://github.com/elastic/elasticsearch-js/blob/master/lib/Transport.js#L591-L595

          if (result.body.version.build_flavor !== 'default') {
            debug('Bad build_flavor')
            this[kProductCheck] = 4
            return productCheckEmitter.emit('product-check', null, false)
          }

[dlocke-rheaply]

This issue is a breaking change for us. IMO a minor version update (7.13 -> 7.14) should not introduce a change like this, it should only be included in a major version update.

[philkra]

With the 7.11 release of Elasticsearch, we will no longer be releasing oss-only distributions, as stated in the FAQ on license change. The recommendation is to upgrade to the latest default distribution of Elasticsearch, which is free to use under Elastic License v2.

Please review the client's compatibility that states the forward compatibility. The recommendation is to upgrade the server first, then the client. If you are blocked to upgrade the cluster, we're happy to help you unblock the situation or please pin the client to an <7.14 version according to your cluster.

[RTodorov]

IMHO this breaking change shouldn't happen in a minor release although I'm well aware of all the political situation involved here. Some people simply do not have the choice of not using AWS' flavor and you're intentionally hurting them with this.

A much more user-friendly approach would be for this check to be a warning stating that compatibility is not guaranteed with non-Elastic flavors instead of a fatal error that for sure caused lots of critical incidents around the world for ES users, at least until 8.0.0.

[jo3n]

We're also having this issue. It is a breaking change.

[dlocke-rheaply]

@jo3n Apparently there are no plans to fix this in 7.14, so the solution is to pin your dependency on 7.13.

[xfournet]

It look likes we should move to new clients of OpenSearch that should be available soon.
See https://aws.amazon.com/blogs/opensource/keeping-clients-of-opensearch-and-elasticsearch-compatible-with-open-source/

[futin]

I can also confirm that downgrading to 7.13 fixed this issue. But really disappointing that minor update broke our whole production. Everyone should definitely look for an alternative since this was a very unpleasant experience.

[Dmitry1987]

But Elastic Cloud is trash, low quality service, we had outage for 3 days with no support, and in a few months another outage for 1 day with no support - it's impossible to reach their teams when there are outages... I even called their office back then and they do not pick up the phone

[falnyr]

Just an update in case anyone starts looking for options, OpenSearch client is now released: https://www.npmjs.com/package/@opensearch-project/opensearch

[MomentQYC]

Since you're supposedly re-embracing open source, you should just ditch this restriction.