Support Thrift over HTTP for HMS
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
No files or test paths are named; start by locating the Hive Metastore transport configuration and deployment entry points in this Rust operator, then review the Spark and Trino integration tests. Done means HTTP is disabled by default, can run instead of TCP or alongside it, and the behavior is verified with Spark and Trino.
Written by the indexing model from the issue text.
Description
Support Thrift over HTTP
Description
Some customers struggle to expose plain TCP to the outside of k8s world.
Also Kerberos is pain in the ***, and there is currently no other auth mechanism for HMS.
We should support Thrift over HTTP to solve both problems.
- HTTP can easily be exposed (such as all other HTTP services, e.g. via an Ingress)
- Users can put a basic auth / oAuth proxy / ... in front of the HTTP service
Value
Users can expose and secure stuff without Kerberos
Dependencies
None
Tasks
Acceptance Criteria
- HTTP disabled by default
- HTTP can be turned on while turning TCP off
- HTTP and TCP can be turned on at the same time (seems to be supported starting with 4.0.0 https://issues.apache.org/jira/browse/HIVE-5312)
(Information Security) Risk Assessment
This gives the option to switch from a (IMHO hard to protect - Kerberos) TCP protocol to the HTTP protocol.
This probably means Kerberos will stop working, but users can put some sort of LoadBalancer/Proxy in front to do the authentication instead of messing with Kerberos.
Accessibility Assessment
None
Quality
Tests with Spark and Trino
Release Notes
Support HTTP thrift transport mode for Hive metastore
- Dominant language
- Rust
- Stars
- 29
- Forks
- 2
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 12
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.
More from stackabletech/hive-operator
-
type/bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
stackabletech/hive-operator#757 ·
-
customer-request
Difficulty 3/5 1-2 days Newbie friendliness 65/100
stackabletech/hive-operator#717 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
stackabletech/hive-operator#678 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
stackabletech/hive-operator#630 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
stackabletech/hive-operator#573 ·
All issues in stackabletech/hive-operator
Similar issues
-
Browser (wasm) relay client cannot connect to relays whose URL has a trailing-dot FQDN hostname Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
n0-computer/iroh#4550 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
paritytech/zombienet-sdk#591 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
farion1231/cc-switch#7638 · 1 comment ·
-
onnx-ir re-exports ModelProto and GraphProto but not NodeProto, AttributeProto and AttributeType Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100