Eclipse Collections VS Elasticsearch

eclipse-collections for Java.

Each year when I do the Advent of Code challenge I use it as an opportunity to learn a new language or tool chain. This year I am writing in Java 17 (I have not used Java since Java 8), along with Eclipse Collections, and using VS Code as my IDE.

If you want design like that, you can just use Eclipse Collections (https://www.eclipse.org/collections/). But do note that that design has its own problems if you are after perfection.

Eclipse-Collections

You were a little wrong, surely you can see that? And for Collections that don't autobox, you want to use something like https://github.com/eclipse/eclipse-collections

You could check out their GitHub and see what is going on https://github.com/elastic/elasticsearch/issues

Link to GitHub -->

I believe the 1024 limit has been upped in recent versions of Elasticsearch

https://github.com/elastic/elasticsearch/issues/92458

Elasticsearch is written in Java and its source code is available on Github.

I don't think the murmur3 hash implementation has changed since it was added as the default in version 2.0 (see the [changes](https://github.com/elastic/elasticsearch/commits/main/server/src/main/java/org/elasticsearch/cluster/routing/Murmur3HashFunction.java)). The plugin itself has seen [more changes](https://github.com/elastic/elasticsearch/commits/main/plugins/mapper-murmur3) but that's IMO because of internals and not visible changes in the calculations.

Mysql is not as open source as postgres (long story). And you can see how open elasticsearch is by just having access to the bugs database https://github.com/elastic/elasticsearch/issue