Romeways kafka
This is an extra package for romeways for more details access the romeways Github page.
This package use aiokafka to connect kafka server.
Configs
Queue
from dataclasses import dataclass
from romeways import GenericQueueConfig
@dataclass(slots=True, frozen=True)
class KafkaQueueConfig(GenericQueueConfig):
"""
topic: str See aiokafka.AIOKafkaConsumer doc
-> https://aiokafka.readthedocs.io/en/stable/api.html#aiokafka.AIOKafkaConsumer
group_id: str See aiokafka.AIOKafkaConsumer doc.
-> https://aiokafka.readthedocs.io/en/stable/api.html#aiokafka.AIOKafkaConsumer
"""
topic: str
group_id: str
connector_name: str
frequency: float
max_chunk_size: int
sequential: bool
Connector
from dataclasses import dataclass
from romeways import GenericConnectorConfig
@dataclass(slots=True, frozen=True)
class KafkaConnectorConfig(GenericConnectorConfig):
"""
bootstrap_server: str | list[str] See aiokafka.AIOKafkaConsumer doc
-> https://aiokafka.readthedocs.io/en/stable/api.html#aiokafka.AIOKafkaConsumer
client_id: str See aiokafka.AIOKafkaConsumer doc.
-> https://aiokafka.readthedocs.io/en/stable/api.html#aiokafka.AIOKafkaConsumer
"""
bootstrap_server: str
client_id: str
Use case
import asyncio
import romeways
# Create a queue config
config_q = romeways.KafkaQueueConfig(
topic="net_topic",
group_id="my-project",
connector_name="kafka-dev1",
frequency=1,
max_chunk_size=10,
sequential=False,
)
# Register a controller/consumer for the queue name
@romeways.queue_consumer(queue_name="queue.payment.done", config=config_q)
async def controller(message: romeways.Message):
print(message)
config_p = romeways.KafkaConnectorConfig(
connector_name="kafka-dev1",
bootstrap_server="localhost:9094",
client_id="1"
)
# Register a connector
romeways.connector_register(
connector=romeways.KafkaQueueConnector, config=config_p, spawn_process=True
)
asyncio.run(romeways.start())
Metadata
Release files for romeways_kafka_queue 0.1.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 | |
|---|---|---|---|---|
| romeways_kafka_queue-0.1.0.tar.gz | 6.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| romeways_kafka_queue-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.7 kB
Release files / romeways_kafka_queue-0.1.0.tar.gz
| Download URL | romeways_kafka_queue-0.1.0.tar.gz |
|---|---|
| Size | 6.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dc94654f6f42e9e006347d29116c1d05d7d14ba0cb52817370d4419f65c18cbb
|
|
BLAKE2b-256 checksum How to use checksums |
12a742645e0e8b16939d33f5bcc8e5133ad45deac551e837840760cf8dba69ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.7.1 CPython/3.12.0 Linux/6.1.0-13-amd64
|
Release files / romeways_kafka_queue-0.1.0-py3-none-any.whl
| Download URL | romeways_kafka_queue-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ee4ea9f6c819101ce0378b8b86fdd10315dc6963d26314d87da151046c298b54
|
|
BLAKE2b-256 checksum How to use checksums |
6c6f18d51f1c36aa78dd8c771275626a8dff48f2e081968ecd361346a680574e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.7.1 CPython/3.12.0 Linux/6.1.0-13-amd64
|
Security for romeways_kafka_queue 0.1.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.