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 to communicate between them
Hope it helps, gp On Thu, Jun 21, 2018 at 9:00 PM Sowjanya Kakarala <sowja...@agrible.com> wrote: > 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 after completing one after other till given end date, > when the sqoop command is getting generated at that point I wanted to call > oozie and run that until the shell script hits end date. > > I saw examples the other way, but it is not what i wanted. > > Is it possible? any suggestions will help. > > Thanks > Sowjanya > -- *Peter Cseh *| Software Engineer cloudera.com <https://www.cloudera.com> [image: Cloudera] <https://www.cloudera.com/> [image: Cloudera on Twitter] <https://twitter.com/cloudera> [image: Cloudera on Facebook] <https://www.facebook.com/cloudera> [image: Cloudera on LinkedIn] <https://www.linkedin.com/company/cloudera> ------------------------------
