-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add FS mapper #61
Add FS mapper #61
Conversation
bb4a587
to
5af8bde
Compare
95acf35
to
1e26257
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really like it! Very good code structure, very clever tests. Well done :)
I left some minor comments.
80eb7f4
to
f2b0080
Compare
@sprzedwojski I considered all the comments. I am waiting for the second round of reviews |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor comments only. Good Job @mik-laj . A lot of small improvements going in the right direction not only the FS mapper itself.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, two small wording issues.
Hello,
I implemented a FS mapper. Implantation does not support all functionalities (See: TODO notes) and it's not idempotent. This is the limitation of pig commands.
It's not tested on Oozie.
Reference:
https://oozie.apache.org/docs/5.1.0/WorkflowFunctionalSpec.html#a3.2.4_Fs_HDFS_action
Visualisation of converted DAG:
Code of converted DAG:
https://gist.github.com/mik-laj/3e1f6137153825d7a4477c70ed1ee3c8
Code of workflow XML:
https://github.com/GoogleCloudPlatform/cloud-composer/blob/fs-mapper/oozie-to-airflow/examples/fs/workflow.xml
Greets