Oozie workflow for cleancontext #216
|
@ -17,6 +17,14 @@
|
|||
<name>shouldCleanContext</name>
|
||||
<description>true if the context have to be cleaned</description>
|
||||
</property>
|
||||
<property>
|
||||
<name>contextId</name>
|
||||
|
||||
<value>sobigdata</value>
|
||||
</property>
|
||||
<property>
|
||||
<name>verifyParam</name>
|
||||
claudio.atzori
commented
Missing description. Missing description.
miriam.baglioni
commented
Same holds as for the previous comment. Anyway if you think it is important to have the descriptions I will add them Same holds as for the previous comment. Anyway if you think it is important to have the descriptions I will add them
claudio.atzori
commented
I think it is. Again: this PR might just provide a first implementation, but the businness logic around these two parameters exists only in your head. To understand their role I'd need to open the actual job implementation and reverse engeener it. I would appreciate if you could add a description. I think it is. Again: this PR might just provide a first implementation, but the businness logic around these two parameters exists only in your head. To understand their role I'd need to open the actual job implementation and reverse engeener it. I would appreciate if you could add a description.
|
||||
<value>gcube </value>
|
||||
</property>
|
||||
|
||||
<property>
|
||||
<name>sparkDriverMemory</name>
|
||||
|
|
Loading…
Reference in New Issue
It should be better to include a description for this parameter, to explain its purpose and if it possible to include multiple contentIds, how they should be formatted.
This is just the first naive implementation of the context cleaning. I have no idea how it will be once done properly
It might be the 1st naive implementation, but looking at the oozie workflow, it is not obvious what a parameter plays when it is not accompanied by any description.
extended