Josh,
These variables are exposed to user. The convention is:
falcon_${input_feed_name}_partition_filter_pig
falcon_${input_feed_name}_partition_filter_hive
falcon_${input_feed_name}_partition_filter_java
falcon_${input_feed_name}_datain_partitions_hive
You should be able to use any of these.
If you are having issues with oozie starting the jobs, its good to look at
oozie.log and see if there an error with any EL.
Thanks!
On Wed, Jul 9, 2014 at 12:57 PM, Srikanth Sundarrajan <[email protected]>
wrote:
> In general it is not a good practice to refer to Falcon internal
> variables, but this might be a public one. Will let @Venkatesh confirm
> this. If it is indeed public, this ought to work, but this may also lead to
> the possibility of cyclic referencing of properties. A peek into the Oozie
> logs might give ideas on what might be the reason for coord not starting.
>
> Regards
> Srikanth Sundarrajan
>
>
> ----------------------------------------
> > From: [email protected]
> > Date: Tue, 8 Jul 2014 15:47:10 -0400
> > Subject: Using properties in processes
> > To: [email protected]
> >
> > Hi,
> >
> > Is it possible to reference properties like
> falcon_input_partition_filter_hive
> > inside of the process xml definition itself?
> >
> > For instance:
> >
> > <properties>
> > ...
> > <property name="indexSelect" value="Select .... where
> > ${falcon_input_partition_filter_hive}" />
> >
> > ...
> >
> > </properties>
> >
> >
> > When I try to do this, I don't get any errors, but my process never
> starts
> > up either. Looked in the falcon logs with no luck. Ideas?
> >
> > Thanks,
> > Josh
>
>
--
Regards,
Venkatesh
“Perfection (in design) is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.”
- Antoine de Saint-Exupéry
