In January ElasticSearch made what it calls “an incredibly hard decision” — to change the licensing on its scalable data-search solution. They called this an effort to “stand up to” Amazon’s AWS for offering ElasticSearch functionality as a service “without collaborating with us… after years of what we believe to be Amazon/AWS misleading and confusing the community.” Amazon then forked ElasticSearch, releasing a new “OpenSearch” product under the original Apache 2.0 licensing. Last month AWS’s fork reached General Availability/1.0 status.
Now Mike Melanson’s “This Week in Programming” column reports that ElasticSearch is “making further attempts at closing off access to ElasticSearch and shutting out AWS — while AWS is fighting back:
AWS says that “OpenSearch aims to provide wire compatibility with open source distributions of Elasticsearch 7.10.2, the software from which it was derived,” making it easy to migrate to OpenSearch. While Elastic can’t do anything about that, they can make changes to some open source client libraries that are commonly used. “Over the past few weeks, Elastic added new logic to several of these clients that rejects connections to OpenSearch clusters or to clusters running open source distributions of Elasticsearch 7, even those provided by Elastic themselves,” AWS writes. “While the client libraries remain open source, they now only let applications connect to Elastic’s commercial offerings…”
AWS is again coming out as the savior of open source in this scenario, it would seem, this time promising to offer “a set of new open source clients that make it easy to connect applications to any OpenSearch or Elasticsearch cluster” that “will be derived from the last compatible versions of corresponding Elastic-maintained clients before product checks were added.”
“In the spirit of openness and interoperability, we will make reasonable efforts to maintain compatibility with all Elasticsearch distributions, even those produced by Elastic,” they write. In the meantime, while the OpenSearch community works on creating the replacement libraries, AWS recommends that users do not update to the latest version of any Elastic-maintained clients, lest their applications potentially cease functioning.
“It’s disappointing to see this,” reads a comment (upvoted 35 times) on the ElasticSearch repository announcing the change in late June. “You’re forcing us as bystanders in a battle to choose sides.” And Amazon responded with its own take on the situation in their AWS press release this week. “Our experience at AWS is that developers find it painful to update their already-deployed applications to use new versions of server software, so backward compatibility for clients and APIs weighs heavily in our designs…”
The press release also calls ElasticSearch’s changes “disruptive,” adding “The most broadly adopted open source projects generally emphasize flexibility, inclusion, and avoidance of lock-in…”
Read more of this story at Slashdot.