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
We should support a lot more functionality for pull queries, e.g.
pull queries where the table is not materialized
pull queries with no constraint on ROWKEY
pull queries with JOINs or GROUP BY etc.
The distinction here is that a pull query runs from the beginning of time to current offsets. For these more complex queries we should fall back to using a KS topology against the data in Kafka i.e. using materialized state stores is an optimisation.
We can then make enhancements over time to support more and more using materialized tables.
EXPLAIN <some pull query> should make it clear if a query is a 'table scan' ie reading all data from Kafka, or using a materialized table.
The text was updated successfully, but these errors were encountered:
We should support a lot more functionality for pull queries, e.g.
The distinction here is that a pull query runs from the beginning of time to current offsets. For these more complex queries we should fall back to using a KS topology against the data in Kafka i.e. using materialized state stores is an optimisation.
We can then make enhancements over time to support more and more using materialized tables.
EXPLAIN <some pull query>
should make it clear if a query is a 'table scan' ie reading all data from Kafka, or using a materialized table.The text was updated successfully, but these errors were encountered: