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

Posted to dev@apex.apache.org by "Ananth (JIRA)" <ji...@apache.org> on 2017/09/25 20:29:00 UTC

[jira] [Updated] (APEXMALHAR-2545) Implement few improvements in the Kudu Implementation

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

Ananth updated APEXMALHAR-2545:
-------------------------------
    Summary: Implement few improvements in the Kudu Implementation  (was: Implement a few improvements in the Kudu Implementation)

> Implement few improvements in the Kudu Implementation
> -----------------------------------------------------
>
>                 Key: APEXMALHAR-2545
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2545
>             Project: Apache Apex Malhar
>          Issue Type: Bug
>            Reporter: Ananth
>            Assignee: Ananth
>
> There are some minor improvements that need to be done as per the Kudu operator review. 
> - Ensure logging is not ERROR level for some of the parser logic wrappers. For example, in the unit tests, we are seeing error logs and it is not necessary they are errors given we send all erraneous SQL expressions to an error port. i.e. the operator is continuing as if it were not an error
> - Ensure that the operator properties are configurable per environment using the configuration object
> - Optimise the setters logic for a given query.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)