Apache Pinot
Self-managed or StarTree Cloud.
Access mode: Read-only
Trino connector. Queryable via Flume’s Lakehouse. This system can be accessed both through its native protocol (for metadata introspection) and via Trino federation (for data profiling and cross-system analytical queries).
Required information
| Field | Details |
|---|---|
| Controller URL | Pinot Controller endpoint for metadata. Broker URL for queries. |
| Ports | Controller: 9000. Broker: 8099. StarTree Cloud: HTTPS on 443. |
| Table(s) | Pinot tables (OFFLINE, REALTIME, or HYBRID) to access. |
| Authentication | Basic auth or token-based. StarTree Cloud: API key. |
| Access level | Read-only: query access to target tables. |
Network considerations
Self-managed: VPN or direct access. Need access to both Controller (metadata) and Broker (queries).
StarTree Cloud: HTTPS over 443. API key authentication.
Trino access: Flume’s Lakehouse queries Pinot via the Trino Pinot connector through the Broker endpoint.
Credential and auth management
Self-managed: Basic auth if enabled. Many deployments run without auth behind a VPN.
StarTree Cloud: API key from admin console. Scoped to workspace.
No fine-grained ACLs in OSS Pinot. Table-level access control available in StarTree Enterprise.
Validation checks
| Check | Method | Expected result |
|---|---|---|
| Network reachability | curl http://<controller>:9000/health | Returns OK |
| Table listing | GET /tables on Controller | Lists tables |
| Query test | POST /query/sql on Broker with SELECT * FROM <table> LIMIT 1 | Returns a row |
| Schema check | GET /schemas/<tableName> on Controller | Returns table schema |
Every connection starts from the pre-engagement checklist and goes through the universal validation protocol before production sign-off.