You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Rui Li (Jira)" <ji...@apache.org> on 2020/05/14 07:10:00 UTC

[jira] [Commented] (FLINK-17682) HiveModuleTest.testConstantReturnValue didn't finish

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

Rui Li commented on FLINK-17682:
--------------------------------

I think {{HiveModuleTest.testConstantReturnValue}} is unlikely to be the root cause of the issue. The case is to test {{str_to_map}} function in hive which is simple and returns a constant value. And it seems we're not stuck at any hive connector code according to the thread dump.

I can update this test case to directly invoke the function, instead of submitting a query. That should simplify the test and improve stability, but then it might also hide the real problem here. [~pnowojski] what do you think?

> HiveModuleTest.testConstantReturnValue didn't finish
> ----------------------------------------------------
>
>                 Key: FLINK-17682
>                 URL: https://issues.apache.org/jira/browse/FLINK-17682
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Hive
>            Reporter: Piotr Nowojski
>            Priority: Major
>              Labels: test-stability
>             Fix For: 1.11.0
>
>
> While testing a PR for FLINK-17663, HiveModuleTest.testConstantReturnValue didn't finish
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=1205&view=logs&j=fc5181b0-e452-5c8f-68de-1097947f6483&t=6b04ca5f-0b52-511d-19c9-52bf0d9fbdfa
> I've looped the code 2000 times on my local machine and it didn't happen again. Thread dump doesn't suggest any actual dead lock, more like something has crashed and didn't notify CLI (as there were very few active threads from Flink). It doesn't look like it was caused by FLINK-17663, but there is that possibility. 



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