You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2023. It is now read-only.
As we can see in inputContent "dstHdfsPathRegexRename", my regex pattern for "${relativeFilepath}" was removed by Conductor.
It seems to be, that Conductor treated it as "normal variable" and as this variable is not part of the workflow input it gets removed.
But that's the problem, as I need this regex pattern to be fed into the worker, so Conductor should not remove those.
Is there any way to workaround this?
The text was updated successfully, but these errors were encountered:
Hello,
I have one problem where I have a worker, which I feed some Java regex patterns via a task's input.
My workflow definition is this:
As you can see, I specified some workflow-inputs:
And also some Java Regex inputs:
Some background: my business logic is to match/rewrite some Java Regex Strings (making use of Regex groupings and so on)
I start my workflow with the following input JSON
Upon startup, Conductor's "workflow input variable substitution" generates the following "running workflow" for me:
As we can see in inputContent "dstHdfsPathRegexRename", my regex pattern for "${relativeFilepath}" was removed by Conductor.
It seems to be, that Conductor treated it as "normal variable" and as this variable is not part of the workflow input it gets removed.
But that's the problem, as I need this regex pattern to be fed into the worker, so Conductor should not remove those.
Is there any way to workaround this?
The text was updated successfully, but these errors were encountered: