You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2019/08/28 11:50:00 UTC

[jira] [Closed] (FLINK-13789) Transactional Id Generation fails due to user code impacting formatting string

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

Chesnay Schepler closed FLINK-13789.
------------------------------------
    Fix Version/s:     (was: 1.8.1)
                       (was: 1.7.2)
                       (was: 1.8.0)
                   1.9.1
                   1.10.0
                   1.8.2
         Assignee: Hao Dang
       Resolution: Fixed

master: c038b92a1c90aec0e466e37858a78472ef1f0f10
1.9: c1716b0ed45baf132b2c1eccfe834c996bc0c6ec 
1.8: d22e15cce1b9098244c800b551e80632c0f5c346 

> Transactional Id Generation fails due to user code impacting formatting string
> ------------------------------------------------------------------------------
>
>                 Key: FLINK-13789
>                 URL: https://issues.apache.org/jira/browse/FLINK-13789
>             Project: Flink
>          Issue Type: Bug
>            Reporter: Hao Dang
>            Assignee: Hao Dang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.8.2, 1.10.0, 1.9.1
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> In [TransactionalIdsGenerator.java|#L94]], prefix contains taskName of the particular task which could ultimately contain user code.  In some cases, user code contains conversion specifiers like %, the string formatting could fail.
> For example, in Flink SQL code, user could have a LIKE statement with a % wildcard, the % wildcard will end up in the prefix and get mistreated during formatting, causing task to fail.
> Think we should move prefix out of the string formatting.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)