You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2020/10/23 09:53:00 UTC

[jira] [Closed] (FLINK-6968) Store streaming, updating tables with unique key in queryable state

     [ https://issues.apache.org/jira/browse/FLINK-6968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann closed FLINK-6968.
--------------------------------
    Resolution: Abandoned

Closing this issue for inactivity. Please re-open this issue if you disagree.

> Store streaming, updating tables with unique key in queryable state
> -------------------------------------------------------------------
>
>                 Key: FLINK-6968
>                 URL: https://issues.apache.org/jira/browse/FLINK-6968
>             Project: Flink
>          Issue Type: New Feature
>          Components: Runtime / Queryable State, Table SQL / API
>            Reporter: Fabian Hueske
>            Assignee: Renjie Liu
>            Priority: Major
>              Labels: pull-request-available
>
> Streaming tables with unique key are continuously updated. For example queries with a non-windowed aggregation generate such tables. Commonly, such updating tables are emitted via an upsert table sink to an external datastore (k-v store, database) to make it accessible to applications.
> This issue is about adding a feature to store and maintain such a table as queryable state in Flink. By storing the table in Flnk's queryable state, we do not need an external data store to access the results of the query but can query the results directly from Flink.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)