You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Peter Wicks (JIRA)" <ji...@apache.org> on 2017/01/18 15:15:26 UTC

[jira] [Updated] (NIFI-3031) Support Multi-Statement Scripts in the PutHiveQL Processor

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

Peter Wicks updated NIFI-3031:
------------------------------
    Fix Version/s: 1.2.0

> Support Multi-Statement Scripts in the PutHiveQL Processor
> ----------------------------------------------------------
>
>                 Key: NIFI-3031
>                 URL: https://issues.apache.org/jira/browse/NIFI-3031
>             Project: Apache NiFi
>          Issue Type: Improvement
>    Affects Versions: 1.2.0
>            Reporter: Matt Burgess
>             Fix For: 1.2.0
>
>
> Trying to use the PutHiveQL processor to execute a HiveQL script that contains multiple statements.
> IE: 
> USE my_database;
> FROM my_database_src.base_table
> INSERT OVERWRITE refined_table
> SELECT *;
> -- or --
> use my_database;
> create temporary table WORKING as
> select a,b,c from RAW;
> FROM RAW
> INSERT OVERWRITE refined_table
> SELECT *;
> The current implementation doesn't even like it when you have a semicolon at the end of the single statement.
> Either use a default delimiter like a semi-colon to mark the boundaries of a statement within the file or allow them to define there own.
> This enables the building of pipelines that are testable by not embedding HiveQL into a product; rather sourcing them from files.  And the scripts can be complex.  Each statement should run in a linear manner and be part of the same JDBC session to ensure things like "temporary" tables will work.



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