mustafasrepo commented on code in PR #9346:
URL: https://github.com/apache/arrow-datafusion/pull/9346#discussion_r1504542446
##########
datafusion/physical-plan/src/lib.rs:
##########
@@ -446,6 +450,123 @@ pub trait ExecutionPlan: Debug + DisplayAs + Send + Sync {
}
}
+/// Describes the execution mode of an operator's resulting stream with respect
+/// to its size and behavior. There are three possible execution modes:
`Bounded`,
+/// `Unbounded` and `PipelineBreaking`.
+#[derive(Clone, Copy, PartialEq, Debug)]
+pub enum ExecutionMode {
+ /// Represents the mode where generated stream is bounded, e.g. finite.
+ Bounded,
+ /// Represents the mode where generated stream is unbounded, e.g. infinite.
+ /// Even though the operator generates an unbounded stream of results, it
+ /// works with bounded memory and execution can still continue
successfully.
+ Unbounded,
+ /// Represents the mode where some of the operator's input stream(s) are
+ /// unbounded; however, the operator cannot generate streaming results from
+ /// these streaming inputs. In this case, the execution mode will be
pipeline
+ /// breaking, e.g. the operator requires unbounded memory to generate
results.
+ PipelineBreaking,
Review Comment:
Some physical optimizer rules such as
`replace_with_order_preserving_variants` behaves differently for
`PipelineBreaking` and `PipelineFriendly` modes. (Such as choosing
`SortPreservingRepartition` instead of `Repartition` to resolve
`PipelineBreaking` plan).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
