falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Neethu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-982) Passing coord:nominalTime() to Hive workflow doesn't work
Date Mon, 01 Aug 2016 17:36:20 GMT

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

Neethu commented on FALCON-982:
-------------------------------

so far any updates on this issue?

> Passing coord:nominalTime() to Hive workflow doesn't work
> ---------------------------------------------------------
>
>                 Key: FALCON-982
>                 URL: https://issues.apache.org/jira/browse/FALCON-982
>             Project: Falcon
>          Issue Type: Bug
>          Components: oozie
>    Affects Versions: trunk
>            Reporter: Adam Kawa
>
> I have a Falcon process that submits a Hive workflow.
> I want to pass {{timestampStop}} property from Falcon process to hive script:
> {code:xml}
> <property name="timestampStop" value="${coord:formatTime(coord:nominalTime(), 'yyyyMMddHHmmss')}"
/>
> {code}
> Unfortunately, my Hive script fails due to ??No function is mapped to the name "coord:formatTime"??
> When using Oozie workflow (instead of Hive workflow), the property is evaluated correctly.
However, I don't want to create verbose Oozie workflow if just a Hive script would be enough.
> This functionality is needed for me when the value of timestampStop can not be extracted
from HDFS path or table partition.
> I guess that similar problem happens when submitting Pig scripts.
> According to [~shwethags]
> {quote}
> The issue is because of the way we add process properties to hive action of
> the oozie workflow. Can you create a bug for this so that its tracked?
> {quote}



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

Mime
View raw message