Time, order, and limits

Time buckets turn timestamps into periods. Ordering chooses result priority. Limits keep response size and compute bounded.

Time buckets#

Supported buckets are:

• minute
• hour
• day
• week
• month

Apply a bucket to a timestamp dimension. The bucketed output is a warehouse-neutral datetime column and can become the x-axis for line or area charts.

Ordering#

Order entries reference result-compatible fields or aliases and use asc or desc.

Examples:

• day ascending for a chronological time series;
• count descending for the top categories;
• average duration descending to identify slow groups.

Grouped ordering is supported across registered warehouse types. Choose aliases clearly so the intended output key is unambiguous.

Definition limit#

The saved definition can set a maximum row count. A runtime request can ask for a lower supported limit, but it cannot use request input to escape server, binding, or definition safeguards. The effective result limit is the lowest positive value among the request, saved definition, destination binding max_rows, and ReportPlane's 100,000-row server safety ceiling.

Destination bindings also carry max_rows, and Elasticsearch/OpenSearch composite aggregation applies a 100,000-bucket safety ceiling before metric ordering. Exceeding the safety boundary returns an explicit error rather than consuming unbounded resources.

Practical guidance#

• Use chronological order for time-series displays.
• Use metric-descending order with a small limit for top-N categories.
• Avoid high-cardinality dimensions without a meaningful limit.
• Keep public defaults small and raise limits only for a demonstrated need.