[
https://issues.apache.org/jira/browse/MRQL-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625833#comment-14625833
]
Leonidas Fegaras edited comment on MRQL-74 at 7/14/15 5:16 AM:
---------------------------------------------------------------
I run the tests on your patch using
{code}
mvn -Dyarn -DskipTests=false clean install
{code}
but they didn't pass. The problem is that Flink 0.9.0 prints extra tracing
info, such as:
{code}
07/14/2015 08:00:32 Job execution switched to status RUNNING.
{code}
This doesn't look to be log4j INFO message. These messages confuse the testing
because it expects only results.
Is there a switch off these messages in Flink?
was (Author: fegaras):
I run the tests on your patch using {{{mvn -Dyarn -DskipTests=false clean
install}}}, but they didn't pass.
The problem is that Flink 0.9.0 prints extra tracing info, such as:
{code}
07/14/2015 08:00:32 Job execution switched to status RUNNING.
{code}
This doesn't look to be log4j INFO message. These messages confuse the testing
because it expects only results.
Is there a switch off these messages in Flink?
> Update Flink version to 0.9.0
> -----------------------------
>
> Key: MRQL-74
> URL: https://issues.apache.org/jira/browse/MRQL-74
> Project: MRQL
> Issue Type: Improvement
> Components: Run-Time/Flink
> Reporter: Chiwan Park
> Assignee: Chiwan Park
>
> Flink team released 0.9.0 version in previous week. There are some API
> changes so we need some modification in FlinkEvaluator and FlinkStreaming.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
