Thanks to Dawid for initiating the discussion. Overall, I agree with Timo
that for 1.9 we should have some quick and simple solution, leaving time
for more thorough discussions for 1.10.

In particular, I'm not fully with solution #1. For one thing, it seems
proposing storing all temporary objects in a memory map in CatalogManager,
and the memory map duplicates the functionality of the in-memory catalog,
which also store temporary objects. For another, as pointed out by the
google doc, different db may handle the temporary tables differently, and
accordingly it may make more sense to let each catalog to handle its
temporary objects.

Therefore, postponing the fix buys us time to flush out all the details.

Thanks,
Xuefu

On Mon, Jul 22, 2019 at 7:19 AM Timo Walther <twal...@apache.org> wrote:

> Thanks for summarizing our offline discussion Dawid! Even though I would
> prefer solution 1 instead of releasing half-baked features, I also
> understand that the Table API should not further block the next release.
> Therefore, I would be fine with solution 3 but introduce the new
> user-facing `createTemporaryTable` methods as synonyms of the existing
> ones already. This allows us to deprecate the methods with undefined
> behavior as early as possible.
>
> Thanks,
> Timo
>
>
> Am 22.07.19 um 16:13 schrieb Dawid Wysakowicz:
> > Hi all,
> >
> > When working on FLINK-13279[1] we realized we could benefit from a
> > better temporary objects support in the Catalog API/Table API.
> > Unfortunately we are already long past the feature freeze that's why I
> > wanted to get some opinions from the community how should we proceed
> > with this topic. I tried to prepare a summary of the current state and 3
> > different suggested approaches that we could take. Please see the
> > attached document[2]
> >
> > I will appreciate your thoughts!
> >
> >
> > [1] https://issues.apache.org/jira/browse/FLINK-13279
> >
> > [2]
> >
> https://docs.google.com/document/d/1RxLj4tDB9GXVjF5qrkM38SKUPkvJt_BSefGYTQ-cVX4/edit?usp=sharing
> >
> >
>
>

Reply via email to