opendistro-build
cloki-go-legacy
| opendistro-build | cloki-go-legacy | |
|---|---|---|
| 2 | 2 | |
| 347 | 33 | |
| - | - | |
| 2.9 | 1.4 | |
| about 2 years ago | about 2 years ago | |
| Shell | Go | |
| Apache License 2.0 | GNU Affero General Public License v3.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
opendistro-build
-
Amazon: Not OK – why we had to change Elastic licensing
You should consider opening an issue on their github [0]?
AWS, from what I know, takes security seriously, and given they themselves use OpenDistro internally, this should become a top priority for them.
[0] https://github.com/opendistro-for-elasticsearch/opendistro-b...
-
Elasticsearch is dead, long live Open Distro for Elasticsearch
By fork they mean: a binary build straight from the unmodified elastic source code using the elastic build file that creates the OSS build bundled with a handful of plugins and components to add alternatives some of the things elastic bundles. They don't even build it themselves and it gets downloaded in binary form straight from Elastic's servers.
If you don't believe me, this is the line in the code where they 'fork' in their build script: https://github.com/opendistro-for-elasticsearch/opendistro-b...
It will be interesting to see if opendistro actually starts contributing to Lucene or adding value to the elastic code base or whether this 'fork' is effectively frozen in time and doomed to go nowhere due to a lack of actual development on the core product.
I seriously doubt that they are going to put any effort whatsoever in that. Because in two years of pretending they have a fork, there has been no serious code contributions from their side at all that I'm aware off. Correct me if I'm wrong.
If you want to back an OSS version of related technology, maybe use something like Apache Solr, which continues to provide many of the same features and is part of the same ecosystem of users and developers that work on Lucene, which also powers Elasticsearch and which of course continues to contribute a lot to Lucene; unlike Amazon.
cloki-go-legacy
-
ClickHouse as an alternative to Elasticsearch for log storage and analysis
I just there was a foss loki-like solution built on ch - that was stable and used in production.
I know there's a few projects (see below) - but I'm not aware of anything mature..
https://github.com/QXIP/cloki-go
https://github.com/lmangani/cloki
-
Elasticsearch is dead, long live Open Distro for Elasticsearch
There's also Cloki, which offers the same Loki APIs but stores data in ClickHouse. It looks interesting.
https://github.com/qxip/cloki-go
Disclaimer: I work on ClickHouse at Altinity.
What are some alternatives?
Elasticsearch - Free and Open, Distributed, RESTful Search Engine
clickhousedb_fdw - PostgreSQL's Foreign Data Wrapper For ClickHouse
bleve - A modern text/numeric/geo-spatial/vector indexing library for go
tidyquery - Query R data frames with SQL
duckdf - 🦆 SQL for R dataframes, with ducks
ClickHouse - ClickHouse® is a free analytics DBMS for big data
meilisearch-js-plugins - The search client to use Meilisearch with InstantSearch.