it’s “sequential”, run the paragraphs one
at a time, in the order they’re defined. If parallel, run using current scheme
(as many at the same time as the threadpool permits)
Simpler and covers all cases, imo
From: Polyakov Valeriy mailto:v.polja...@tinkoff.
e. If it's "sequential", run the paragraphs one
at a time, in the order they're defined. If parallel, run using current scheme
(as many at the same time as the threadpool permits)
Simpler and covers all cases, imo
________
From: Polyakov Valeriy mailt
Let me try to summarize the discussion. Evidently, current behavior of running
notes does not meet actual requirements. The most important thing that we need
is the ability of sequential running. However, at the same time we want to keep
functionality of parallel running. We discussed that the m
This can cover most of typical parallel-use cases. Other cases could be
transformed to this type of case with some increase of full running time.
Building of high-grade DAG dependencies will be much more complicated and looks
like functionality of visual-based platform of data transformation (e.
I suppose there is a fairly simple solution to the problem. We can use flag on
paragraph which means “this paragraph should be run in parallel with previous”.
Such a logic could help to create sequential-parallel running. It does not
implement full-DAG capabilities, but it’s easy to understand a
Hello, Team!
What do you think about implementation of high-grade metadata browser for JDBC
interpreter? As it is done in any popular SQL development tools, for example,
DataGrip. I'm talking about new detailed panel which will contain metadata info
of all included in note interpreters. I've fo
