ingsongLee
--
From:Felipe Gutierrez
Send Time:2019年6月26日(星期三) 20:58
To:JingsongLee
Cc:user
Subject:Re: Hello-world example of Flink Table API using a edited Calcite rule
Hi JingsongLee,
it is still not very clear to me. I imagine that I can create an
InMemoryExternalCatalog and insert some tuples there (
apache/flink/table/descriptors/OldCsv.scala
>
> Best, JingsongLee
>
> --
> From:Felipe Gutierrez
> Send Time:2019年6月26日(星期三) 20:58
> To:JingsongLee
> Cc:user
> Subject:Re: Hello-world example of Flink Table API using a edited Calcite
>
ngLee
--
From:Felipe Gutierrez
Send Time:2019年6月26日(星期三) 20:58
To:JingsongLee
Cc:user
Subject:Re: Hello-world example of Flink Table API using a edited Calcite rule
Hi JingsongLee,
it is still not very clear to me. I imagine that I can create an
InMemoryExternalCatalog and i
Hi JingsongLee,
it is still not very clear to me. I imagine that I can create an
InMemoryExternalCatalog and insert some tuples there (which will be in
memory). Then I can use Calcite to use the values of my
InMemoryExternalCatalog and change my plan. Is that correct?
Do you have an example of ho
Hi Felipe:
I think your approach is absolutely right. You can try to do some plan test
just like [1].
You can find more CalciteConfigBuilder API test in [2].
1.https://github.com/apache/flink/blob/release-1.8/flink-table/flink-table-planner/src/test/scala/org/apache/flink/table/api/batch/table/Co
Hi,
does someone have a simple example using Table API and a Calcite rule which
change/optimize the query execution plan of a query in Flink?
>From the official documentation, I know that I have to create a
CalciteConfig object [1]. Then, I based my firsts tests on this
stackoverflow post [2] and
