Details
-
Feature
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
1.12, 1.13
-
None
Description
Current Situation
The job JobSchedulerPLSQLJobJSAdapterClass can parse the dbms output with the regex in variable_parser_reg_expr e.g. ^SET\s+([^\s])\s*IS\s(.*)$
That means that an output like
DBMS_OUTPUT.PUT_LINE('SET myParam ' || FIELD);
should create a task parameter myParam with the value of FIELD.
This task parameter should be available in the postprocession script like
{{ var 'XXX' = spooler_task.params.value( 'myParam ' );}}
The task parameter myParam is not available in the postprocessing script
This issue comes with YADE-522
Desired Behavior
When setting the output with DBMS_OUTPUT.PUT_LINE('SET myParam ' || FIELD);
to SET myParam=value the task parameter myParam should be available in the postprocessing script
Attachments
Issue Links
- relates to
-
YADE-522 YADE running in parallel tasks should not be slower than running with a single task
- Released