Thank you.
Great presentation about the high-level translation process.
Regards,
Pedro
--
View this message in context:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Flink-SQL-Stream-Parser-based-on-calcite-tp9592p9608.html
Sent from the Apache Flink User Mailing List arc
The translation is done in multiple stages.
1. Parsing (syntax check)
2. Validation (semantic check)
3. Query optimization (rule and cost based)
4. Generation of physical plan, incl. code generation (DataStream program)
The final translation happens in the DataStream nodes, e.g., DataStreamCalc
[
Thank you for the response.
I'm not understanding where does something like this,
/SELECT * WHERE action='denied' /
gets translated to something similar in the Flink Stream API,
/filter.(new FilterFunction() {
public boolean filter(Event event) {
Hi Pedro,
The sql() method calls the Calcite parser in line 129.
Best, Fabian
2016-10-17 16:43 GMT+02:00 PedroMrChaves :
> Hello,
>
> I am pretty new to Apache Flink.
>
> I am trying to figure out how does Flink parses an Apache Calcite sql query
> to its own Streaming API in order to maybe ext
