Improved Search Performance in SAP BTP Core, SAP Cloud Application Programming Model, Node.js Runtime
Explains CDS version 5's @cds.search annotation, which lets a service declare which elements a search query covers, and states that only String-typed elements are searched by default so the generated SQL stays simple. Covers two further changes to @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's Node.js runtime: metadata about which elements are searchable is now cached, and search over localized text can resolve at query time instead of through a compiled view, avoiding a coalesce function that blocks filter push-down on SAP HANA. Also describes an experimental toggle, cds.env.features.optimized_search, that lets the runtime choose the CONTAINS predicate over LIKE for large data sets.
Where it sits
Who is behind it
In the atlas: contributes to 9, wrote 1@arleytmauthor
Properties
About this work
For search
Details
Graph
Source
History
- explains → applies_to on capability:search (cap)Door scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).
- Entered the atlasDiscovered via SAP Community · cap-tag.
For your agent
- Ref
content:improved-search-performance-in-sap-btp-core-sap-cloud-application-programming-mo- JSON
- /content/improved-search-performance-in-sap-btp-core-sap-cloud-application-programming-mo.json
- MCP
- Connecting an agent