cmem-plugin-querycatalog
Use queries from the Corporate Memory query catalog in workflows.
This is a plugin for eccenca Corporate Memory. You can install it with the cmemc command line client like this:
cmemc admin workspace python install cmem-plugin-querycatalog
Tasks
This plugin adds three workflow tasks, all of which work on a query catalog rather than on a query pasted into the workflow.
- List Catalog Queries emits one entity per query a catalog holds, describing it: the catalog graph, the query IRI, label, description, type, the query text as stored and the names of the placeholders it contains.
- Get Catalog Query emits the same description for a single query, chosen on the task or named by an incoming entity.
- Execute Catalog Query runs a stored query. A SELECT produces one entity per result row, an ASK a single answer, a CONSTRUCT or DESCRIBE its statements as quad entities, and an update query produces nothing and reports what it wrote.
A query that contains {{placeholder}} holes turns their names into input fields on
Execute Catalog Query, and runs once per incoming entity.
The catalog graph is picked from a list that groups the registered query catalogs first, then the shape catalogs, then any other graph that happens to hold queries.
Known limitations
The whole result of a query is held in memory. Corporate Memory sends it in a single response, so a query returning very many rows is limited by what the DataIntegration process can hold.
Execute Catalog Query derives its input port from the placeholders of the stored
query, and DataIntegration caches that port on the task. After upgrading this plugin
to a version that changes the shape of a port, reload the projects that use it -
cmemc project reload <project>, or the reload action in the workspace. Until then an
existing task keeps the ports it was created with, and a workflow built on it can fail
with an error naming a schema the current version no longer uses. Saving the task
again has the same effect, and tasks created after the upgrade are unaffected.
Metadata
Release files for cmem-plugin-querycatalog 0.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| cmem_plugin_querycatalog-0.5.0.tar.gz | 26.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cmem_plugin_querycatalog-0.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 58.8 kB
Release files / cmem_plugin_querycatalog-0.5.0.tar.gz
| Download URL | cmem_plugin_querycatalog-0.5.0.tar.gz |
|---|---|
| Size | 26.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4a2c652442dd8e829bf482adba1e7fe62bbe83796d7fa53e3737ba21ad0f02ca
|
|
BLAKE2b-256 checksum How to use checksums |
e047b12bf9188d971bd4b93dd3ce97d65841b224f910daf71adaa3ec7977c771
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.3.4 CPython/3.13.13 Linux/6.1.0-53-amd64
|
Release files / cmem_plugin_querycatalog-0.5.0-py3-none-any.whl
| Download URL | cmem_plugin_querycatalog-0.5.0-py3-none-any.whl |
|---|---|
| Size | 32.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fd90903176e3667b62a754a77c8341685391ef2cc4f27ddd3182032527c96130
|
|
BLAKE2b-256 checksum How to use checksums |
80c8aa3a90d49f7f318590d8b947b95088074287e79fc2299ca06db6c1f0ced7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.3.4 CPython/3.13.13 Linux/6.1.0-53-amd64
|
Security for cmem-plugin-querycatalog 0.5.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.