[
https://issues.apache.org/jira/browse/FLINK-14243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16966998#comment-16966998
]
Bowen Li commented on FLINK-14243:
----------------------------------
according to https://issues.apache.org/jira/browse/HIVE-16183, I think the
thread safety issues are more of Hive bugs, rather than Flink's. So instead of
making Flink deal with them, it would be better for users to make sure the
issues have been fixed in a newer Hive version, and patch their own Hive.
> flink hiveudf needs some check when it is using cache
> -----------------------------------------------------
>
> Key: FLINK-14243
> URL: https://issues.apache.org/jira/browse/FLINK-14243
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Hive, Table SQL / Planner
> Affects Versions: 1.9.0
> Reporter: jackylau
> Priority: Major
> Fix For: 1.10.0
>
> Attachments: Snipaste_2019-10-30_15-34-09.png
>
>
> Flink1.9 brings in hive connector, but it will have some problem when the
> original hive udf using cache. We konw that hive isĀ processed level parallel
> based on jvm, while flink/spark is task level parallel. If flink just calls
> the hive udf, it wll exists thread-safe problem when using cache.
> So it may need check the hive udf code and if it is not thread-safe, and set
> the flink parallize=1
--
This message was sent by Atlassian Jira
(v8.3.4#803005)