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

Posted to issues@flink.apache.org by "Bowen Li (Jira)" <ji...@apache.org> on 2020/01/15 22:40:00 UTC

[jira] [Updated] (FLINK-15607) throw exception when users trying to use Hive aggregate functions in streaming mode

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

Bowen Li updated FLINK-15607:
-----------------------------
    Description: 
Due to that Hive functions are all built for batch processing, aggregate functions in Hive that implement UDAF and GenericUDAFResolver2 interfaces may have unpredictable behaviors when used in streaming mode in Flink. We advice users to only use Hive aggregate functions interfaces in batch mode.

 

Seems need to distinguish execution mode in FunctionCatalogOperatorTable, which is not achievable yet.

  was:Seems need to distinguish execution mode in FunctionCatalogOperatorTable, which is not achievable yet.


> throw exception when users trying to use Hive aggregate functions in streaming mode
> -----------------------------------------------------------------------------------
>
>                 Key: FLINK-15607
>                 URL: https://issues.apache.org/jira/browse/FLINK-15607
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / Hive, Table SQL / API
>            Reporter: Bowen Li
>            Priority: Major
>
> Due to that Hive functions are all built for batch processing, aggregate functions in Hive that implement UDAF and GenericUDAFResolver2 interfaces may have unpredictable behaviors when used in streaming mode in Flink. We advice users to only use Hive aggregate functions interfaces in batch mode.
>  
> Seems need to distinguish execution mode in FunctionCatalogOperatorTable, which is not achievable yet.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)