I have a workspace that has several WorkspaceRunners running in sequence. If the workspace in the first WorkspaceRunner writes nothing, no need to run the remaining WorkspaceRunners. But how I can pass the number of the writes of the first workspace to the parent workspace?
Question
How to pass number of writes in a workspace inside a WorkspaceRunner to the parent worpsace?
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
Hi @ag, a possible way I can think of is:
- With the first child workspace, determine if one or more features were written and save the result into a temporary file. Some transformers including the FeatureWriter and the NoFeatureTester (from Hub) could help you to do that.
- Then, set "Yes" to the "Wait for Job Complete" parameter in the first WorkspaceRunner, read the temporary file after the translation completed, and determine if features have been written.
If you added a published user parameter to the child workspace in order to receive the temporary file path, you can create a path string in the parent workspace with a TempPathnameCreator, pass it to the child workspace via the parameter through the WorkspaceRunner, and commonly use it as the temporary file path in the parent and the child .
Hope this helps.
+11- Supporter
Hi @ag, a possible way I can think of is:
- With the first child workspace, determine if one or more features were written and save the result into a temporary file. Some transformers including the FeatureWriter and the NoFeatureTester (from Hub) could help you to do that.
- Then, set "Yes" to the "Wait for Job Complete" parameter in the first WorkspaceRunner, read the temporary file after the translation completed, and determine if features have been written.
If you added a published user parameter to the child workspace in order to receive the temporary file path, you can create a path string in the parent workspace with a TempPathnameCreator, pass it to the child workspace via the parameter through the WorkspaceRunner, and commonly use it as the temporary file path in the parent and the child .
Hope this helps.
Allen