stackabletech / stackabletech/trino-operator
Support Phoenix connector
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 63
- Forks
- 13
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 12
Description
Docs: https://trino.io/docs/current/connector/phoenix.html
Update 2024-05-24: I noticed there were some discussions around removing the Phoenix connector from Trino.
Generally is does not seem there are toooo many active users out there, so we should do further research before adding this functionality to prevent us adding it just for it to be removed a few months later.
See https://github.com/trinodb/trino/pull/20739 and https://github.com/trinodb/trino/pull/21569 for details.
Contributor guide
No contributing guide indexed for this repository
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 with the Phoenix connector documentation at trino.io/docs/current/connector/phoenix.html and review Trino pull requests #20739 and #21569. Determine whether the connector is still appropriate to support before defining the implementation scope; done requires a documented decision and, if support proceeds, a concrete plan for the operator changes.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100