Skip to content
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

Create new flow step that defines local variables #55

Closed
paulhoule opened this issue Oct 14, 2013 · 0 comments
Closed

Create new flow step that defines local variables #55

paulhoule opened this issue Oct 14, 2013 · 0 comments
Milestone

Comments

@paulhoule
Copy link
Owner

Commonly a filename occurs two or three times in a flow because it as used as an output, then used as an input, and then we delete it if we don't need it anymore.

Repeating the code that generates filenames is asking for trouble, so it should be possible to make a step that writes a computed value into a local variable.

An easy way to implement local variables would be to add a Map<String,Object> to the context object, so you could write something like

local['tmpfile']

to access the value.

paulhoule pushed a commit that referenced this issue Oct 17, 2013
…uent syntax. The way we test will need to change when basekbNowFlow is rewritten so I'm capturing this moment where it all works right
paulhoule pushed a commit that referenced this issue Oct 19, 2013
… way. unit tests for the parts that do the actual work are still lacking
paulhoule pushed a commit that referenced this issue Oct 20, 2013
…o unit tests yet for command line hadoop yet but this is good for the weekly batch job
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant