Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Elasticsearch is open source, again

elastic.co

Post reply on HN
Print view View original

11–20 of 473 posts

Re: Elasticsearch is open source, again

#11

Post by vineyardmike »

orra wrote: post #8
foxyv wrote: post #4

Earlier quoted context omitted.

It was so that AWS would create their own name for their fork: > we changed the license, knowing it would result in a fork of Elasticsearch with a different name and a different trajectory. It’s a long story. I think the name of the fork is now OpenSearch.

I don't understand why they didn't treat Amazon's previous offering as a trademark infringement.

If I sell my Toyota car on the side of the road I can call it a Toyota. If I sell you ElasticSearch(tm) Service which is the actual ES code base, what’s the infringement?

Re: Elasticsearch is open source, again

#13

Post by foxyv »

Raed667 wrote: post #5
foxyv wrote: post #4

Earlier quoted context omitted.

It was so that AWS would create their own name for their fork: > we changed the license, knowing it would result in a fork of Elasticsearch with a different name and a different trajectory. It’s a long story. I think the name of the fork is now OpenSearch.

what is preventing AWS from dropping OpenSearch and going back to just selling Elastic ?

To be honest, the OpenSearch brand has more value now than Elastic.

Re: Elasticsearch is open source, again

#14

Post by reducesuffering »

If Amazon's OpenSearch plateaus, and everyone wants to host ElasticSearch, but on their existing AWS infra/sales business inertia, this issue will fundamentally reoccur. Nothing actually changed except Elastic thinks Amazon will commit to their own fork. If Amazon doesn't, we're back to square one: Amazon hosts open source ElasticSearch, Elastic changes their license, another fork.

"Amazon is fully invested in their fork." Amazon is a cutthroat business that will change strategy if their investment isn't paying off.

That this scenario isn't addressed at the very top of your "addressing the trolls" doesn't bode well at all.

Re: Elasticsearch is open source, again

#16

Post by everfrustrated »

Too late, the community all moved over to OpenSearch.

I'll never forgive Elastic for locking basic security features behind their paid licence. Over the years probably millions of people had their data compromised due to that (due to people inadvertently leaving instances on the public internet - having auth enabled by default would have helped a lot)

Re: Elasticsearch is open source, again

#17

Post by orra »

vineyardmike wrote: post #11
orra wrote: post #8

Earlier quoted context omitted.

I don't understand why they didn't treat Amazon's previous offering as a trademark infringement.

If I sell my Toyota car on the side of the road I can call it a Toyota. If I sell you ElasticSearch(tm) Service which is the actual ES code base, what’s the infringement?

The service is more than the code base: it's who is offering it, who supports it.

Besides, I'd be shocked if that analogy is how the law works. Perhaps if you'd bought an individual license then sure, you could resell it with the brand name, just like the car. But wholesale is a completely different situation.

Re: Elasticsearch is open source, again

#18

Post by voxic11 »

orra wrote: post #8
foxyv wrote: post #4

Earlier quoted context omitted.

It was so that AWS would create their own name for their fork: > we changed the license, knowing it would result in a fork of Elasticsearch with a different name and a different trajectory. It’s a long story. I think the name of the fork is now OpenSearch.

I don't understand why they didn't treat Amazon's previous offering as a trademark infringement.

They did https://www.elastic.co/blog/elastic-and-amazon-reach-agreeme...

Re: Elasticsearch is open source, again

#19

Post by DominoTree »

unethical_ban wrote: post #10

Okay, cool. No notes, that's neat. Are there any SMEs that have worked with both OpenSearch (the fork) and ElasticSearch? Are there significant differences? I know the AWS fork had the big difference back then of having RBAC built into their Kibana portion.

I've found OpenSearch to be a bit flaky but I haven't worked with it very seriously compared to ElasticSearch

(and before OpenSearch, the AWS-managed ElasticSearch absolutely hurt the ElasticSearch brand because of all of the issues Amazon created - it couldn't even rebalance shards, let alone add new nodes or switch to larger nodes without a blue-green deployment)

Re: Elasticsearch is open source, again

#20

Post by beachy »

Raed667 wrote: post #5
foxyv wrote: post #4

Earlier quoted context omitted.

It was so that AWS would create their own name for their fork: > we changed the license, knowing it would result in a fork of Elasticsearch with a different name and a different trajectory. It’s a long story. I think the name of the fork is now OpenSearch.

what is preventing AWS from dropping OpenSearch and going back to just selling Elastic ?

Large tech companies care about their reputation. If they dropped their own fork and went back and started again from Elastic that would be admitting their own incompetence. So not happening.
Post reply on HN