Hi Peter,
Thanks for your reply and great suggestions.
But, for my usecase I dont think coodinator can help because I am doing
some logistics in the shellscript.
So my usecase is:
I have a shell script which takes config file and table names from postgres
and hive. and this script generates sqoop
Hey,
I don't think I understand the whole picture, but in general:
- try to use sqoop action for executing sqoop commands
- for date-related scheduling, use coordinators. They can handle catch-up
and other stuff for you
- try to split your shell script to atomic steps and use the action-data
field
Hi Guys,
I am trying to build a workflow, which should get commands from a shell
script and oozie job has to complete that sqoop command and then take the
other command from same shell script.
for example:
my shell script have sqoop command and automatically looped over, from
start date within it
