Using #option('AllowedCluster'... action is different in HPCC 5 and Legacy
Field Tab
Administrator use only
Field Tab
Administrator use only
Environment
Linux
Description
In Legacy ECL Watch and IDE, if you use the #option('allowedClusters','thor400_20,thor400_30'), a drop down box to select an alternative cluster becomes available. In 5.0.10 there is never a drop down box created to select which cluster to run on if the job is in blocked mode.
Jim Defabia now has an example.
Conclusion
None
100% Done
Activity
Show:
Richard Chapman July 27, 2015 at 9:23 AM
The box cannot be populated until the workunit has compiled, since it is the compiler that process the #option
Jim DeFabia July 20, 2015 at 4:02 PM
It may be that the list of clusters doesn't appear until after the job completes.
Users need the list when it is queued, so they can select a different cluster and resubmit it.
Jim DeFabia July 20, 2015 at 12:53 PM
I submitted a trivial example using:
And I get a drop-list for Cluster in the workunit details page as expected.
Michael Gould July 20, 2015 at 12:21 PM
In testing, it appears that only the current server being run on is showing in the drop down, not all of the servers in the AllowedCluster option.
Miguel Vazquez May 12, 2015 at 2:10 PM
Edited
Please target this for 5.2.4
Fixed
Pinned fields
Click on the next to a field label to start pinning.
In Legacy ECL Watch and IDE, if you use the
#option('allowedClusters','thor400_20,thor400_30'), a drop down box to select an alternative cluster becomes available. In 5.0.10 there is never a drop down box created to select which cluster to run on if the job is in blocked mode.
Jim Defabia now has an example.