datayoga
datayoga copied to clipboard
datayoga-io
streaming data pipeline platform
Instead of using it directly, return the data, so the CLI will communicate with it instead of having another dependency.
`init()` call tries to establish a connection to datasources. In some cases we need just validate `job` and their jobs without connection to anything because datasources is not available at...
1. Name the demo as dy-demo and all the containers with `dy-` prefix to avoid collisions:  ERROR: for postgres Cannot create container for service postgres: Conflict. The container name...
internal fields like opcode, msg_id should be part of the metadata. The internal result field should not be part of the payload. @zalmane, WDYT?
- Consider adding such a flag in job/runner level - Check if there's such a flag in JMESPath
better to take the default 8080 from the json schema itself so if we change it to 8081 we won't need to do it twice... This is relevant to other...
shouldn't we apply also in `relational.read` block? _Originally posted by @spicy-sauce in https://github.com/datayoga-io/datayoga/pull/303#discussion_r1172145888_
shouldn't this be a general util for producing message IDs? _Originally posted by @spicy-sauce in https://github.com/datayoga-io/datayoga/pull/297#discussion_r1165407205_