Hi,
You could also consider using the JDBC Catalog implementation (via
Postgres) or building your own custom one, see
https://ci.apache.org/projects/flink/flink-docs-master/docs/dev/table/catalogs/#user-defined-catalog
Curious if that would help you out or if you need anything else.
Best regards
I don't think so. As the name tells it is stored "in-memory" which
intrinsically means transient. If you need a persistent catalog you can
use e.g. Hive or Postgres.
You can also try to implement a catalog backed by e.g. a property file.
This could potentially end up in Flink / flink-packages, but
Dawid Wysakowicz
Thanks for your reply. Will community to plan to implement this feature ?
Best,
Roc
At 2021-10-14 21:00:37, "Dawid Wysakowicz" wrote:
If I understand your question correctly, you're asking if you can somehow
persist the GenericInMemoryCatalog. I am afraid i
If I understand your question correctly, you're asking if you can
somehow persist the GenericInMemoryCatalog. I am afraid it is not
possible. The idea of the GenericInMemoryCatalog is that it is transient
and is stored purely in memory.
Best,
Dawid
On 14/10/2021 13:44, Yuepeng Pan wrote:
> Hi,
Hi,
Community.
If I want to save the catalog state after the operation based on
GenericInMemoryCatalog, which is convenient to recover the last catalog
instance when opening the session or tableEnvironment next time. Does flink
support this feature?Thank you.
Best,
Roc
