Hi Samrat,
Thanks for your advice.
> 1. The createCatalog method does not mention any exceptions being thrown.
CreateCatalog will throw CatalogException like registerCatalog. As
CatalogException is a RuntimeException,
there is no explicit declaration of throwing Exceptions in CatalogManager
and
lincoln lee created FLINK-32249:
---
Summary: A Java string should be used instead of a Calcite
NlsString to construct the table and column comment attributes of CatalogTable
Key: FLINK-32249
URL: https://issues.apache
Hi, Jane.
Thanks for you input. I think we can add the auxiliary command show procedures
in this FLIP.
Following the syntax for show functions proposed in FLIP-297.
The syntax will be
SHOW PROCEDURES [ ( FROM | IN ) [catalog_name.]database_name ] [ [NOT] (LIKE |
ILIKE) ].
I have updated to this
Hi, Jark
Thanks for your feedback, according to my initial assessment, the work
effort is relatively large.
Moreover, I will add a test result of all queries to the FLIP.
Best,
Ron
Jark Wu 于2023年6月1日周四 20:45写道:
> Hi Ron,
>
> Thanks a lot for the great proposal. The FLIP looks good to me in ge
Hi Ron
OFGC looks like an exciting optimization, looking forward to its completion
in Flink!
A small question, do we consider adding a benchmark for the operators to
intuitively understand the improvement brought by each improvement?
In addition, for the implementation plan, mentioned in the FLIP
Hi Jing,
> what is the difference between the RPC call or query you mentioned
and the lookup in a very
general way
I think the RPC call or query service is quite similar to the lookup join.
But lookup join should work
with `LookupTableSource`.
Let's see how we can perform an async RPC call w
Rui Fan created FLINK-32250:
---
Summary: Revert the Field name of BUFFER_TIMEOUT to improve
compatibility
Key: FLINK-32250
URL: https://issues.apache.org/jira/browse/FLINK-32250
Project: Flink
Issue
Hi Ron,
I think this FLIP would help to improve the performance, looking forward to its
completion in Flink!
For the state compatibility session, it seems that the checkpoint compatibility
would be broken just like [1] did. Could FLIP-190 [2] still be helpful in this
case for SQL version upgra
> For the state compatibility session, it seems that the checkpoint
> compatibility would be broken just like [1] did. Could FLIP-190 [2] still be
> helpful in this case for SQL version upgrades?
I guess this is only for batch processing. Streaming should be another story?
Best,
Jingsong
On Mo
melin created FLINK-32251:
-
Summary: flink jdbc catalog cannot add parameters to url
Key: FLINK-32251
URL: https://issues.apache.org/jira/browse/FLINK-32251
Project: Flink
Issue Type: New Feature
Thanks Ron for initiating this discussion, the OFGC sounds a cool
optimization.
I also agree with above comments about the benchmark result, it is
important for performance improvements.
And I thing Yun and Jingsong has raised a very interesting topic about the
support for streaming. It's worth m
11 matches
Mail list logo