Milinda> Samza's streaming query planning phase Can you clarify a bit? If I understand right, you aim to "wire Samza's operators in an optimized way and execute it as usual Samza's chain", don't you? In that case, it looks like you need planner only.
In case you want to stream Samza's results through java.sql.ResultSet, then Enumerable/Bindable question makes sense. Milinda> Does this convention effect the query planning decisions other than transformations like LogicalTableScan to BindableTableScan It does not. Juilan> if people want to execute queries using just core Anybody out there wanting to execute queries using just core? Can we have some requirements before we implement one more executor? In 584 the discussion is regarding "being able to use Calcite core as planner only". Juilan> It will also make core smaller and simpler. It won't be simpler. Support of interpreter would take time. Let's better have separation of modules like "planner" and "executor". At least it would be a proof of ability to plug executor without changing "hard-coded rules in the planner". Juilan> Most people find it easier to implement a bindable convention Please, do not mix API vs convention. It does not require a new convention to process Scannable. Vladimir
