You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/04/17 12:12:00 UTC

[jira] [Commented] (FLINK-8366) Use Row instead of String as key when process upsert results

    [ https://issues.apache.org/jira/browse/FLINK-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440795#comment-16440795 ] 

ASF GitHub Bot commented on FLINK-8366:
---------------------------------------

Github user fhueske commented on the issue:

    https://github.com/apache/flink/pull/5244
  
    Thanks for the fix @hequn8128!
    +1 to merge


> Use Row instead of String as key when process upsert results
> ------------------------------------------------------------
>
>                 Key: FLINK-8366
>                 URL: https://issues.apache.org/jira/browse/FLINK-8366
>             Project: Flink
>          Issue Type: Bug
>          Components: Table API &amp; SQL
>            Reporter: Hequn Cheng
>            Assignee: Hequn Cheng
>            Priority: Major
>
> In {{TableSinkITCase.upsertResults()}} function, we use String as key to upsert results. This will make (1,11) and (11,1) have the same key (i.e., 111).
> This bugfix use Row instead of String to avoid the String problem.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)