Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.startree.ai/llms.txt

Use this file to discover all available pages before exploring further.

Beta feature — Query Analyzer is disabled by default and available on demand. Contact your StarTree account team to have it enabled for your environment.
Query Analyzer is built into the StarTree Data Portal Query Console. No setup is required — open the console, write your query, and run an analysis.

​
Running Static Analysis

Static analysis catches issues before your query runs.
  1. Navigate to Data Portal → Query Console
  2. Write or paste your SQL query
  3. Select Analyze → Static Analysis
Query Analyzer fetches table metadata automatically and returns results within seconds.

​
Running Runtime Analysis

Runtime analysis identifies issues after your query runs, using real execution statistics. Each risk flag includes the operator metrics and any correctness alerts relevant to that finding.
  1. Write your SQL query in the Query Console
  2. Select Analyze → Runtime Analysis
Runtime analysis executes your query against your Pinot cluster. For very large or expensive queries, run static analysis first to catch structural issues before proceeding.

​
Acting on Recommendations

Index additions — Apply through Data Portal → Table Management. Index changes require a segment reload to take effect on existing data. Query rewrites — Apply directly in the Query Console editor. The recommendation shows a before/after diff. Query hints — Added inline to your SQL using /*+ ... */ syntax. Take effect immediately without schema changes.
Start with rank 1 recommendations. If any risk flag carries a correctness alert, address it first — incomplete results affect how you should interpret the rest of the analysis.
For a full breakdown of what each output field and recommendation type means, see Understanding Your Results.

​
Tips

  • Use real queries: Query Analyzer uses column cardinality and table size to produce accurate recommendations. Simplified test queries produce weaker results.
  • Static first, runtime second: Static analysis is faster. Use runtime analysis for your most important or problematic queries.
  • Read the tradeoffs: Every recommendation includes tradeoffs, for example, an index that helps one query pattern may not justify the storage cost.