apache/pinot

No way to configure base path/url for Pinot UI

Open

#13125 opened on May 10, 2024

View on GitHub
 (4 comments) (0 reactions) (1 assignee)Java (4,937 stars) (1,234 forks)batch import
featurehelp wantedui

Description

No config value which allows a change to the base path of the Pinot UI.

If there is a basic ingress configuration that includes a path as opposed to exclusively a host this causes the UI to fail in Kubernetes.

Contributor guide

Tech stack
None
Domain
frontenddevops
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic knowledge of Apache PinotFamiliarity with Java and web application configurations
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate how the Pinot UI is currently served and where the base path is hardcoded. Look at the configuration files (e.g., application configs) and the code responsible for serving the UI (likely in a controller or web server setup). Review any existing discussions in the comments or linked PRs. Consider adding a new configuration property and updating the UI's routing logic to use it.