[
https://issues.apache.org/jira/browse/FLINK-10192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593493#comment-16593493
]
ASF GitHub Bot commented on FLINK-10192:
----------------------------------------
twalthr opened a new pull request #6617: [FLINK-10192] [sql-client] Fix SQL
Client table visualization mode
URL: https://github.com/apache/flink/pull/6617
## What is the purpose of the change
This PR fixes the wrong materialization for the debugging visualization in
table mode.
## Brief change log
- Rework the caching mechanism in `MaterializedCollectStreamResult`.
## Verifying this change
- Unit test added in `MaterializedCollectStreamResultTest`.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): no
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: no
- The serializers: no
- The runtime per-record code paths (performance sensitive): no
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Yarn/Mesos, ZooKeeper: no
- The S3 file system connector: no
## Documentation
- Does this pull request introduce a new feature? no
- If yes, how is the feature documented? not applicable
----------------------------------------------------------------
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:
[email protected]
> SQL Client table visualization mode does not update correctly
> -------------------------------------------------------------
>
> Key: FLINK-10192
> URL: https://issues.apache.org/jira/browse/FLINK-10192
> Project: Flink
> Issue Type: Bug
> Components: Table API & SQL
> Affects Versions: 1.6.0
> Reporter: Fabian Hueske
> Assignee: Timo Walther
> Priority: Major
> Labels: pull-request-available
>
> The table visualization modes does not seem to update correctly.
> When I run a query that groups and aggregates on a few (6) distinct keys, the
> client visualizes some keys multiple times. Also the aggregated values do not
> seem to be correct.
> Due to the small number of keys, these get frequently updated.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
