[
https://issues.apache.org/jira/browse/FLINK-6968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16490567#comment-16490567
]
ASF GitHub Bot commented on FLINK-6968:
---------------------------------------
Github user liurenjie1024 commented on the issue:
https://github.com/apache/flink/pull/5688
@twalthr I store each column separately to avoid encoding and schema
management problems, also to reduce unnecessary data transfer when querying
data. Issue multiple requests for multiple fields is one of the drawbacks.
> 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: Table API & SQL
> Reporter: Fabian Hueske
> Assignee: Renjie Liu
> Priority: Major
>
> 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
(v7.6.3#76005)
