[
https://issues.apache.org/jira/browse/FLINK-6968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581093#comment-16581093
]
ASF GitHub Bot commented on FLINK-6968:
---------------------------------------
alpinegizmo commented on issue #6434: [FLINK-6968] [table] Add Queryable table
sink.
URL: https://github.com/apache/flink/pull/6434#issuecomment-413203702
The documentation is pretty thin. It would be nice to explain that the
queryable table sink can only be used in retract mode, and include a better
example. I only understood what's going on after reading the test -- I found
Row.of("jeff") much easier to understand than Row.of(1).
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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
> 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
(v7.6.3#76005)
