[jira] [Created] (FLINK-12919) flink-connector-hive compilation error in travis
leesf created FLINK-12919: - Summary: flink-connector-hive compilation error in travis Key: FLINK-12919 URL: https://issues.apache.org/jira/browse/FLINK-12919 Project: Flink Issue Type: Bug Components: Connectors / Hive Reporter: leesf [https://api.travis-ci.org/v3/job/548270362/log.txt] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLINK-12914) Remove legacy InstanceListener
leesf created FLINK-12914: - Summary: Remove legacy InstanceListener Key: FLINK-12914 URL: https://issues.apache.org/jira/browse/FLINK-12914 Project: Flink Issue Type: Sub-task Components: Runtime / Coordination Reporter: leesf Assignee: leesf Fix For: 1.9.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLINK-12913) Remove legacy InstanceManager and InstanceManagerTest
leesf created FLINK-12913: - Summary: Remove legacy InstanceManager and InstanceManagerTest Key: FLINK-12913 URL: https://issues.apache.org/jira/browse/FLINK-12913 Project: Flink Issue Type: Sub-task Components: Runtime / Coordination Reporter: leesf Assignee: leesf Fix For: 1.9.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLINK-12800) Harden Tests when availableProcessors is 1
leesf created FLINK-12800: - Summary: Harden Tests when availableProcessors is 1 Key: FLINK-12800 URL: https://issues.apache.org/jira/browse/FLINK-12800 Project: Flink Issue Type: Bug Components: Tests Affects Versions: 1.8.0 Reporter: leesf Assignee: leesf Fix For: 1.9.0 Some tests failed when Runtime.getRuntime().availableProcessors() is 1. The source vertex and other vertex may chained, thus make test failed. such as AsyncWaitOperatorTest#testOperatorChainWithProcessingTime StreamingJobGraphGeneratorTest#testChainStartEndSetting StreamOperatorChainingTest#testMultiChainingWithObjectReuse StreamOperatorChainingTest#testMultiChainingWithoutObjectReuse So we would specify parallelism of vertex directly to let its not chained with source . -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLINK-12268) Port SharedSlotsTest to new code base
leesf created FLINK-12268: - Summary: Port SharedSlotsTest to new code base Key: FLINK-12268 URL: https://issues.apache.org/jira/browse/FLINK-12268 Project: Flink Issue Type: Sub-task Components: Runtime / Coordination Reporter: leesf Assignee: leesf Fix For: 1.9.0 Get rid of Instance. Port SchedulerTestUtils#getRandomInstance to new code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLINK-12267) Port SimpleSlotTest to new code base
leesf created FLINK-12267: - Summary: Port SimpleSlotTest to new code base Key: FLINK-12267 URL: https://issues.apache.org/jira/browse/FLINK-12267 Project: Flink Issue Type: Sub-task Components: Runtime / Coordination, Tests Reporter: leesf Assignee: leesf Fix For: 1.9.0 Mainly get rid of `Instance` -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLINK-12264) Port ExecutionGraphTestUtils to new code base
leesf created FLINK-12264: - Summary: Port ExecutionGraphTestUtils to new code base Key: FLINK-12264 URL: https://issues.apache.org/jira/browse/FLINK-12264 Project: Flink Issue Type: Sub-task Components: Tests Reporter: leesf Assignee: leesf Fix For: 1.9.0 Mainly get rid of Instance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLINK-12158) Update Java / Scala StatefulJobWBroadcastStateMigrationITCase for 1.7
leesf created FLINK-12158: - Summary: Update Java / Scala StatefulJobWBroadcastStateMigrationITCase for 1.7 Key: FLINK-12158 URL: https://issues.apache.org/jira/browse/FLINK-12158 Project: Flink Issue Type: Sub-task Components: Tests Reporter: leesf Assignee: leesf Fix For: 1.9.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLINK-12148) Give precedence to specified local jar when same mainClass is included in both lib and specified jar
leesf created FLINK-12148: - Summary: Give precedence to specified local jar when same mainClass is included in both lib and specified jar Key: FLINK-12148 URL: https://issues.apache.org/jira/browse/FLINK-12148 Project: Flink Issue Type: Bug Components: Command Line Client Affects Versions: 1.8.0 Reporter: leesf Assignee: leesf Fix For: 1.9.0 When submitting the flink job with ./flink run -c mainClass localJar. If the main class is included in the $FLINK_HOME/lib directory and the specified jar package, then the mainClass in the $FLINK_HOME/lib directory is executed instead of the specified localJar. For example, There is flink-examples-streaming_2.11-1.9-SNAPSHOT.jar in lib directory that contains the org.apache.flink.streaming.examples.wordcount.WordCount class, and LocalWordCount.jar also contains org.apache.flink.streaming.examples.wordcount The .WordCount class, then use ./flink run -c org.apache.flink.streaming.examples.wordcount.WordCount /tmp/LocalWordCount.jar to submit job, the WordCount class in flink-examples-streaming_2.11-1.9-SNAPSHOT.jar is executed in instead of LocalWordCount.jar. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLINK-11272) Support for parsing multiple --yarnship parameters
leesf created FLINK-11272: - Summary: Support for parsing multiple --yarnship parameters Key: FLINK-11272 URL: https://issues.apache.org/jira/browse/FLINK-11272 Project: Flink Issue Type: Improvement Components: Job-Submission, YARN Affects Versions: 1.7.1 Reporter: leesf Assignee: leesf Fix For: 1.7.2 When using flink run -m yarn-cluster ** command to submit application to yarn, flink only supports parsing one --yarnship parameter now, which might not be suitable for the following scenarios: Application submitted to yarn depends on jars which are divided into common jars and application-specific jars, the common jars are the same to all applications while application-specific jars are different according to different applications. The current processing way in flink is to put all jars in one directory and specify the directory with --yarnship. There is no problem when submit job in sequence (put application-specific jar and common jars into one directory dynamicly), but it is not so efficient. It can be improved by parsing multiple --yarnship parameters that place the application-specific jars in a different directory from other common jars, then we can submit job concurrently. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLINK-11217) Back to top button is missing in the Joining document and is not properly placed in the Process Function document
leesf created FLINK-11217: - Summary: Back to top button is missing in the Joining document and is not properly placed in the Process Function document Key: FLINK-11217 URL: https://issues.apache.org/jira/browse/FLINK-11217 Project: Flink Issue Type: Improvement Components: Documentation Affects Versions: 1.7.0 Reporter: leesf Assignee: leesf Fix For: 1.7.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLINK-11216) Back to top button is missing in the Joining document and is not properly placed in the Process Function document
leesf created FLINK-11216: - Summary: Back to top button is missing in the Joining document and is not properly placed in the Process Function document Key: FLINK-11216 URL: https://issues.apache.org/jira/browse/FLINK-11216 Project: Flink Issue Type: Improvement Components: Documentation Affects Versions: 1.7.0 Reporter: leesf Assignee: leesf Fix For: 1.7.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
