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

Posted to issues@kylin.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/08/23 10:00:00 UTC

[jira] [Commented] (KYLIN-4671) Avoid FetchRunner printing too many logs due to NPE

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

ASF GitHub Bot commented on KYLIN-4671:
---------------------------------------

hit-lacus commented on pull request #1335:
URL: https://github.com/apache/kylin/pull/1335#issuecomment-678754255


   LGTM


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Avoid FetchRunner printing too many logs due to NPE
> ---------------------------------------------------
>
>                 Key: KYLIN-4671
>                 URL: https://issues.apache.org/jira/browse/KYLIN-4671
>             Project: Kylin
>          Issue Type: Improvement
>            Reporter: chuxiao
>            Priority: Minor
>         Attachments: D-Chat_20200729164446.png
>
>
> See pcitcure. 
> When there are some dirty metadatas, NPE exceptions will continue to be log. Abnormal skip, dirty data can be cleaned up when cleaning up historical job information. So adjust the log level to debug。



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