You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
They both replace Spark's physical plan with a custom plan
They both use an Intermediate Representation to encode the plan. Gluten uses substrait, and Comet uses a simpler protobuf representation that is tightly coupled to Spark.
Gluten typically delegates to Velox when used to accelerate Spark, and Comet delegates to DataFusion
The Comet project started before Gluten was an Apache project.
There are no plans to integrate Comet with Gluten as part of the Comet project.
However, there is no reason why Gluten could not add Comet/DataFusion as a backend query engine (DataFusion already supports Substrait, and Comet provides the Spark-compatible operators and expressions).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Comet and Gluten have similar architectures:
The Comet project started before Gluten was an Apache project.
There are no plans to integrate Comet with Gluten as part of the Comet project.
However, there is no reason why Gluten could not add Comet/DataFusion as a backend query engine (DataFusion already supports Substrait, and Comet provides the Spark-compatible operators and expressions).
Beta Was this translation helpful? Give feedback.
All reactions