Dima Pristupa
Dima Pristupa
Got a comment from @zaychenko-sergei that it's better to use an environment variable -- no problem
**Schema-related** Since, we need to know which dataset it is and who owns it in order to display (combine) URL mapping for a dataset, a "move" from `DataQueries` to `Dataset`...
Scripts that use files from S3 directly: https://github.com/kamu-data/kamu-cli/blob/2dd34d7f75d6fda59ee57700ae4df1479aab3563/images/demo/jupyter/kamu.py#L22-L45 https://github.com/kamu-data/kamu-cli/blob/2dd34d7f75d6fda59ee57700ae4df1479aab3563/images/jupyter/kamu.py#L14-L37
Cool, tracing is the best visual way to know that optimization is needed. Yes, we knew this before, but when you can see this need on the graph, superb!
Within https://github.com/kamu-data/kamu-cli/pull/863, several E2E tests have been added that cover part of the expectations of this ticket: - Creating root & derived datasets (using predefined files) - Triggering flows manually
Task accomplished
> Please loop me into any design discussions on this topic - I'm very interested. Fixing a fact: it was decided to stay with OSO, at this point in history
Done via https://github.com/kamu-data/kamu-cli/pull/814