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

Posted to issues@kylin.apache.org by "kangkaisen (JIRA)" <ji...@apache.org> on 2017/01/07 11:24:58 UTC

[jira] [Updated] (KYLIN-2357) Make ERROR_RECORD_LOG_THRESHOLD configurable

     [ https://issues.apache.org/jira/browse/KYLIN-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

kangkaisen updated KYLIN-2357:
------------------------------
    Attachment: KYLIN-2357.patch

This is the patch.

> Make ERROR_RECORD_LOG_THRESHOLD configurable
> --------------------------------------------
>
>                 Key: KYLIN-2357
>                 URL: https://issues.apache.org/jira/browse/KYLIN-2357
>             Project: Kylin
>          Issue Type: Bug
>          Components: Job Engine
>    Affects Versions: v1.6.0
>            Reporter: kangkaisen
>            Assignee: kangkaisen
>            Priority: Minor
>         Attachments: KYLIN-2357.patch
>
>
> currently, the {{BatchConstants.ERROR_RECORD_LOG_THRESHOLD}} is hardcode to 100.I wonder why we accept the error record. 
> Normally, the cubing should have zero error record.Besides, even if only have one error record, the query results will be different from Hive or Presto.
> So. I think we could make the ERROR_RECORD_LOG_THRESHOLD configurable and the default value is 0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)