You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by Rishav Rohit <ri...@gmail.com> on 2015/08/05 08:45:41 UTC
Yesterday's date value in Falcon
Hello,
I want to schedule a Falcon process which invokes an oozie SSH action
workflow, the shell script need yesterday's date as a parameter and I used
below in Falcon process definition -
<properties>
<property name="source_type" value="mobile" />
<property name="feed_date" value="yesterday(0,0)" />
</properties>
but on execution this process throws below error -
UNKOWN_ERROR: Not able to execute ssh-base.sh on user@server | ErrorStream:
bash: -c: line 0: syntax error near unexpected token `(bash: -c: line 0:
`oozie-oozi/0007675-150518162055448-oozie-oozi-W/external--ssh/ssh-base.sh
FLATTEN_ARGS curl "
http://server:11000/oozie/callback?id=0007675-150518162055448-oozie-oozi-W@external&status=#status"
"--data-binary%%%@#stdout%%%--request%%%POST%%%--header%%%"content-type:text/plain""
0007675-150518162055448-oozie-oozi-W@ex
When I tried to run this process without feed_date property it executed
successfully.
Please suggest how canI pass yesterday's date to my Oozie workflow.
Regards,
Rishav
Re: Yesterday's date value in Falcon
Posted by Pallavi Rao <pa...@inmobi.com>.
Rishav,
Srikanth just pointed out that I was mistaken. Although Falcon doesn't
evaluate the property values, the EL expressions should be resolved by
Oozie itself. For this to happen, the following has to be place:
1. Oozie installation must have falcon-oozie-el-extension-*.jar under its
libext and also the WAR must have it too.
2. Oozie's oozie-site.xml must be updated with appropriate settings for the
EL expression to be resolved.
Both the jar and the sample oozie-site.xml should be available under
$FALCON_INSTALL_DIR/oozie
Can you please check if the above configuration is taken care of. I will
try this out on my dev environment, in the meanwhile.
Apologies for the confusion,
Regards,
Pallavi
On Wed, Aug 5, 2015 at 2:25 PM, Pallavi Rao <pa...@inmobi.com> wrote:
> Rishav,
> Falcon currently does NOT resolve EL expressions supplied in properties.
> The property values are not interpreted in any way by Falcon, they are just
> passed along "as is" to your oozie workflow.
>
> Seems you have a use case for the same. Please file a feature request
> against FALCON and we will evaluate and requirement and pick it up.
>
> Thanks,
> Pallavi
>
> On Wed, Aug 5, 2015 at 12:15 PM, Rishav Rohit <ri...@gmail.com>
> wrote:
>
>> Hello,
>>
>> I want to schedule a Falcon process which invokes an oozie SSH action
>> workflow, the shell script need yesterday's date as a parameter and I used
>> below in Falcon process definition -
>>
>> <properties>
>> <property name="source_type" value="mobile" />
>> <property name="feed_date" value="yesterday(0,0)" />
>> </properties>
>>
>> but on execution this process throws below error -
>> UNKOWN_ERROR: Not able to execute ssh-base.sh on user@server |
>> ErrorStream:
>> bash: -c: line 0: syntax error near unexpected token `(bash: -c: line 0:
>> `oozie-oozi/0007675-150518162055448-oozie-oozi-W/external--ssh/ssh-base.sh
>> FLATTEN_ARGS curl "
>>
>> http://server:11000/oozie/callback?id=0007675-150518162055448-oozie-oozi-W@external&status=#status
>> "
>> "--data-binary%%%@
>> #stdout%%%--request%%%POST%%%--header%%%"content-type:text/plain""
>> 0007675-150518162055448-oozie-oozi-W@ex
>>
>> When I tried to run this process without feed_date property it executed
>> successfully.
>> Please suggest how canI pass yesterday's date to my Oozie workflow.
>>
>> Regards,
>> Rishav
>>
>
>
--
_____________________________________________________________
The information contained in this communication is intended solely for the
use of the individual or entity to whom it is addressed and others
authorized to receive it. It may contain confidential or legally privileged
information. If you are not the intended recipient you are hereby notified
that any disclosure, copying, distribution or taking any action in reliance
on the contents of this information is strictly prohibited and may be
unlawful. If you have received this communication in error, please notify
us immediately by responding to this email and then delete it from your
system. The firm is neither liable for the proper and complete transmission
of the information contained in this communication nor for any delay in its
receipt.
Re: Yesterday's date value in Falcon
Posted by Pallavi Rao <pa...@inmobi.com>.
Rishav,
Falcon currently does NOT resolve EL expressions supplied in properties.
The property values are not interpreted in any way by Falcon, they are just
passed along "as is" to your oozie workflow.
Seems you have a use case for the same. Please file a feature request
against FALCON and we will evaluate and requirement and pick it up.
Thanks,
Pallavi
On Wed, Aug 5, 2015 at 12:15 PM, Rishav Rohit <ri...@gmail.com>
wrote:
> Hello,
>
> I want to schedule a Falcon process which invokes an oozie SSH action
> workflow, the shell script need yesterday's date as a parameter and I used
> below in Falcon process definition -
>
> <properties>
> <property name="source_type" value="mobile" />
> <property name="feed_date" value="yesterday(0,0)" />
> </properties>
>
> but on execution this process throws below error -
> UNKOWN_ERROR: Not able to execute ssh-base.sh on user@server |
> ErrorStream:
> bash: -c: line 0: syntax error near unexpected token `(bash: -c: line 0:
> `oozie-oozi/0007675-150518162055448-oozie-oozi-W/external--ssh/ssh-base.sh
> FLATTEN_ARGS curl "
>
> http://server:11000/oozie/callback?id=0007675-150518162055448-oozie-oozi-W@external&status=#status
> "
> "--data-binary%%%@
> #stdout%%%--request%%%POST%%%--header%%%"content-type:text/plain""
> 0007675-150518162055448-oozie-oozi-W@ex
>
> When I tried to run this process without feed_date property it executed
> successfully.
> Please suggest how canI pass yesterday's date to my Oozie workflow.
>
> Regards,
> Rishav
>
--
_____________________________________________________________
The information contained in this communication is intended solely for the
use of the individual or entity to whom it is addressed and others
authorized to receive it. It may contain confidential or legally privileged
information. If you are not the intended recipient you are hereby notified
that any disclosure, copying, distribution or taking any action in reliance
on the contents of this information is strictly prohibited and may be
unlawful. If you have received this communication in error, please notify
us immediately by responding to this email and then delete it from your
system. The firm is neither liable for the proper and complete transmission
of the information contained in this communication nor for any delay in its
receipt.