-
Notifications
You must be signed in to change notification settings - Fork 1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: build materializations from the physical plan (#3494)
* feat: build materializations from the physical plan This patch changes up how we build materializations to use the physical plan instead of building from the logical plan. A materialization is the data in the state store with some additional transformations applied. These transformations should be the same as those applied by the steps in the physical plan following the aggregation step. This patch builds up the transformation as we build the streams app from the physical plan. Transformations are described in MaterializationInfo, and accumulated by a Builder class. A transformation allows mapping a key/row pair to an optional row. The row is optional to support filters. We currently support 3 types of transformations: - aggregate result map: mapping the results of complex aggregates (e.g. avg) - projection - filter Finally, the materialization code has been moved to the ksql-streams module so that it can be used by the streams app builder. * Review feedback
- Loading branch information
Showing
66 changed files
with
816 additions
and
527 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
110 changes: 0 additions & 110 deletions
110
ksql-engine/src/main/java/io/confluent/ksql/materialization/MaterializationInfo.java
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.