Graph, spatial and document data
Storing and querying data that is not plain rows, such as a network of relationships, a geometry or a JSON document, in the database that already holds the rows instead of in a separate store per model. Free-text search over entities is searchSearchFree-text search across an entity and its compositions, pushed into the database rather than filtered in the service. Declared search, database similarity search and filtering in application code are often lumped together.SAP and community, unassessed; similarity over embeddings is retrieval-augmented generationRetrieval-augmented generationGrounding a model's answer in data retrieved at question time: text split into chunks, each chunk embedded as a vector, and the chunks nearest to the question placed into the prompt. Semantic search is the same retrieval with a person reading the matches, and fine-tuning changes the model's weights, not its input.SAP and community, unassessed.
Overview
Storing and querying data that is not plain rows, such as a network of relationships, a geometry or a JSON document, in the database that already holds the rows instead of in a separate store per model. Free-text search over entities is searchSearchFree-text search across an entity and its compositions, pushed into the database rather than filtered in the service. Declared search, database similarity search and filtering in application code are often lumped together.SAP and community, unassessed; similarity over embeddings is RAG on CDSRetrieval-augmented generationGrounding a model's answer in data retrieved at question time: text split into chunks, each chunk embedded as a vector, and the chunks nearest to the question placed into the prompt. Semantic search is the same retrieval with a person reading the matches, and fine-tuning changes the model's weights, not its input.SAP and community, unassessed.
SAP HANA CloudSAP HANA CloudThe managed database under most of this: CAP's default target, the store Datasphere and Analytics Cloud sit on, and a service with plans and components.sap official, btp holds JSON documents in a document store queried with SQL functions such as JSON_TABLE, defines a graph over existing tables as a graph workspace deployed as an hdbgraphworkspace artifact, and computes on geometries with spatial methods such as ST_Distance, deployed through HDI from the same project as the relational tables.
Not covered: At HANA SQL. Each model is reached through HANA's own SQL functions, HDI artifacts and procedures, so none of it carries over to another database.
The three repositories answering this in the batch are SAP-samples examples and hands-ons, which demonstrate rather than provide, so core-only reads what SAP HANA CloudSAP HANA CloudThe managed database under most of this: CAP's default target, the store Datasphere and Analytics Cloud sit on, and a service with plans and components.sap official, btp ships. where_it_stops is a assessment of those sources, which show every model through HANA-specific SQL; no page was checked that states it.
No community artifact is documented here.
Artifacts
Nothing is mapped here yet.
Content
Show 4 more
Seen working
Details
Coverage
For your agent
- Ref
capability:multi-model-data- JSON
- /capabilities/multi-model-data.json
- MCP
- Connecting an agent