cap-embedding-function
A CAP service that computes a note's Vector(768) embedding in its own handlers, selecting 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's vector_embedding as a column from a Dummy entity.
Notes carries a Vector(768) element and is projected to the service without it; before-CREATE and before-UPDATE handlers fill it from vector_embedding(${text}, 'DOCUMENT', 'SAP_NEB.20240715'), selected as a column from the Dummy entity at id: 1. The similaritySearch function embeds the search word the same way and returns three notes with their cosine_similarity against to_real_vector of that embedding, ordered descending. cap-vector-hccap-vector-hcA sample that declares VECTOR_EMBEDDING in a CDS entity: an FAQ model whose embedding column HANA Cloud generates and stores, then answers questions by similarity search.independent, cap declares the embedding on the element and lets HANA Cloud generate and store it; here the handler owns both the write and the query. The project sets cds.requires to db: hana and auth: dummy, depends on @cap-js/hana@cap-js/hanaThe HANA database service — the production default, on the same streamlined architecture as the SQLite and PostgreSQL services.sap official, cap, and its README is the CAP scaffold's own getting-started text.
Facts
Where it sits
Who is behind it
In the atlas: maintains 47, contributes to 47, wrote 10@miyasutamaintainer
What it declares
Every artifact
- Type
- Sample
- Origin
- Independently maintained
- Use as
- A reference
- Runtime
- Node.js
- Runs on
- Cloud Foundry
As a sample
- Declared for
- ^8
- Form
- does not say
Connections
Grounding a model's answer in data retrieved at question time
SAP HANA database service for CAP
Managed SAP HANA database service on BTP
Download
README
quoted from miyasuta/cap-embedding-function, readGetting Started
Welcome to your new project.
It contains these folders and files, following our recommended project layout:
| File or Folder | Purpose |
|---|---|
app/ | content for UI frontends goes here |
db/ | your domain models and data go here |
srv/ | your service models and code go here |
package.json | project metadata and configuration |
readme.md | this getting started guide |
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
History in the atlas
- First seen.
For your agent
- Ref
artifact:miyasuta-cap-embedding-function- JSON
- /artifacts/miyasuta-cap-embedding-function.json
- MCP
- Connecting an agent