Live data from Hacker News

Official Elasticsearch Python library no longer works with open-source forks

github.com

141–144 of 144 posts

Re: Official Elasticsearch Python library no longer works with open-source forks

#141
post #131

Earlier quoted context omitted.

> Copy-left inhibits commercial exploitation It doesn't.

Perhaps exploitation is too negative and it is not true for some cases, but most companies do not employ it or use it as a component because of the restrictive licence.

It depends in usage and license. Not all business models suffer from requirement to provide source code to users. Even AGPL can be fine for company (e.g. MongoDB in AWS), if it sells service. And number of companies using Linux kernel licensed under GPL and even making their products based on it is countless.

Re: Official Elasticsearch Python library no longer works with open-source forks

#142
post #141

Earlier quoted context omitted.

Perhaps exploitation is too negative and it is not true for some cases, but most companies do not employ it or use it as a component because of the restrictive licence.

It depends in usage and license. Not all business models suffer from requirement to provide source code to users. Even AGPL can be fine for company (e.g. MongoDB in AWS), if it sells service. And number of companies using Linux kernel licensed under GPL and even making their products based on it is countless.

In that case I agree and kudos to those companies that embrace it and give back. I think it is a way many more companies could embrace if they modified their business strategy a bit.

Re: Official Elasticsearch Python library no longer works with open-source forks

#143
post #4

I use to be a huge proponent of Elastic.co for search. I paid for their Elastic Cloud Enterprise product to offer an internally hosted Elastic as a Service. We ran a proof of concept with the the open source Elastic Stack before requesting the funding to get commercial support and the extra management features. I'm not sure I can recommend them anymore. The company doesn't seem to understand their customer's journey…

Basically, they make it clear their library doesn’t work with a different data store and thereby avoiding people reporting bugs due to incompatiblities between the two? It seems very reasonable.

As a minor version change that will break software currently running without problems? Not very reasonable if you ask me - especially since wire protocol is checked on the client side.

Re: Official Elasticsearch Python library no longer works with open-source forks

#144
post #4

I use to be a huge proponent of Elastic.co for search. I paid for their Elastic Cloud Enterprise product to offer an internally hosted Elastic as a Service. We ran a proof of concept with the the open source Elastic Stack before requesting the funding to get commercial support and the extra management features. I'm not sure I can recommend them anymore. The company doesn't seem to understand their customer's journey…

It is easy to judge another’s actions from afar when it’s their meal and roof they’re working for. It’s okay for Amazon (a trillion dollar company) to make money off of their work but not themselves? Imho, the problem isn’t “well it’s not open source anymore then.” The problem is people who give more weight to a religion/philosophy than sustainability. Who cares if it’s open source if the people developing it can’t s…

A lof of people care. Not all choose opensource because of religion/beliefs. It's the most sane choice when you want to ensure business continuity as the company who owns it can do whatever they want with the product/service including sunsetting it. When it's open you at least have a choice.
Post reply on HN