redpanda-data / redpanda-data/connect
Investigate elastic/opensearch forks
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.8k
- Forks
- 969
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 64
Description
The dust is starting to settle now since the opensearch fork so it's probably worth spending some time understanding what's needed in order to continue to support both offerings. We're currently using https://github.com/olivere/elastic which has been fantastic (more info about future direction here: https://github.com/olivere/elastic/issues/1533) but we could also consider moving to the official client libraries as we only use a small fraction of ES endpoints.
Official libraries:
Questions:
- Do we need a forked
opensearchcomponent?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the current use of olivere/elastic and comparing the official go-elasticsearch and opensearch-go libraries. Investigate whether both offerings can be supported without a forked opensearch component. Done means documenting the compatibility findings and a clear direction for continued Elasticsearch and OpenSearch support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, go
- Domain
- backend, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100