Polypheny-Prism-API
The definition files for the Polypheny Prism API, a multi-model, multi-language query interface.
The Prism Interface uses Protocol Buffer (protobuf) messages to define it's services. To keep things clear and well-organized, the message definitions are grouped into several files. This simplifies finding specific messages, based on what they do or what part of the system they relate to. The files itself are grouped in categories. Those are expressed in the file names. Two kinds of categories exist:
Request Response Category
The category type contains messages that are used in communication adhering to a request, response scheme. Here the client sends a request message to the server upon which the server sends back a response message.
-
Requests File: This file contains all messages that are sent from the client to the server. The file name adheres to the following pattern:
[category]_requests.proto. For example, all the request messages for making or managing connections would be inconnection_requests.proto. -
Responses File: This is the partner file to Requests. It contains all the messages the server sends back to the client. Following the naming pattern, these files end with
_responses.proto. The response messages related to connections would thus be inconnection_responses.proto.
Other Category
The other kind of category contains messages that are not directly used as a response to a request. An example therefore would be messages representing a specific datatype supported by the DBMS.
This category always contains only one file. The filename adheres to the pattern [category].proto.
Doc Generator
Detailed Documentation of the proto files their messages and enums and much more can automatically be created using the doc generator included in this repo. For this to work, the protobuf compiler must be installed. It's current version can be downloaded here.
To run the doc generator, execute the file generator.py in the doc-generator directory.
This creates a directory called docs containing the generated documentation.
Generate Python files
Generate the Python code:
python -m grpc_tools.protoc -I . --python_out . org/polypheny/prism/*.proto
Metadata
Release files for polypheny-prism-api 2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| polypheny-prism-api-2.1.tar.gz | 17.7 kB | Details |
Release files / polypheny-prism-api-2.1.tar.gz
| Download URL | polypheny-prism-api-2.1.tar.gz |
|---|---|
| Size | 17.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6357feed95d40ce9d2665dfae66c423984f9b9d36975d6840d59ffb55e1a4c5e
|
|
BLAKE2b-256 checksum How to use checksums |
5463c9f9849afa6ea219bf89eaa08273037bf4d58f800f285b1f3bd2def82315
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 28, 2024.
Transparency log