Analytical queries
Grouped, aggregated and filtered reads for analytical clients — the query shapes an analytical UI issues, answered by the database rather than in memory. Named for the query and not for the field: this is what a CAP service does when a chart asks it something, and it is not the analytics estate — Datasphere, Analytics Cloud, BW and the modelling that happens in them are a different concern on a different door.
Overview
Not covered: It stops at the transformations capire's table marks n/a for both runtimes: topcount, toppercent and topsum with their bottom counterparts, expand, groupby with rollup or $all, and custom aggregation methods; search and compute inside $apply are answered by CAP Java and not by @sap/cds@sap/cdsThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, cap. The hierarchy transformations TopLevels, ancestors and descendants are there only to support requests from the UI5 Tree Table, and concat has to end the pipeline and rules out every other system query option.
No community artifact is documented here.
Artifacts
Content
Show 6 more
Seen working
Neither the package manifest nor the repository tree declares a licence.
Neither the package manifest nor the repository tree declares a licence.
Neither the package manifest nor the repository tree declares a licence.
Details
Coverage
For your agent
- Ref
capability:analytical-queries- JSON
- /capabilities/analytical-queries.json
- MCP
- Connecting an agent