Yassin Bahri
Capabilities
Entries
An early alpha release whose README says to pin the version and test recipes against non-production data first. HANA synchronisation is snapshot-only and does not reconcile deleted rows, so a document for a row deleted in the source stays in the index. A recipe's field allow-list does not decide what the service account may read: the README states that field allow-listing does not replace SAP authorization, and that the package infers no SAP module semantics, authorization scope or safe fields from table names. Only Business Partner has a built-in recipe, every other dataset needs a `KnowledgeRecipe` written for it, and [Qdrant](external:qdrant) local mode is stated to be for development and smaller indexes.
Python library turning OData or HANA records into chunked documents
Details
History
- sap-knowledge-pipelineHanded over as a URL. Filed behind the BTP door because what it reads is an SAP OData service and [SAP HANA](artifact:sap-hana), and neither the library nor its recipes touch CAP, UI5 or ABAP; the repository's own topics are rag, rag-pipeline, sap, sap-btp and sap-hana. One edge, [retrieval-augmented generation](capability:retrieval-augmented-generation): the capability's CAP coverage says the layer above the vector, splitting long text into chunks and deciding what goes into the prompt, is hand-written in every entry there, and that layer is what this library is. [Data import and export](capability:data-import-export) was considered and left off, since that capability is about a file somebody supplies rather than records read out of a live service, and [OData](capability:odata) is about serving a model as OData rather than consuming one. The optional SAP `hdbcli` driver is named in the prose and carries no edge: SAP's Node.js driver is the artifact [@sap/hana-client](artifact:sap-hana-client), so its Python sibling belongs in the graph the same way and not as an external, which is an editorial decision rather than one for this batch.
- First entry seenDiscovered via Added by hand.
Profile
For your agent
- Ref
actor:yassinbahri- JSON
- /actors/yassinbahri.json
- MCP
- Connecting an agent