Add template fields to ProduceToTopicOperator #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change enables Jinja templating for
ProduceToTopicOperator
. It's useful when the producer function needs access to execution context, e.g. date interval, or when it depends on the upstream result, e.g. XCom variable. Otherwise, you have to write a customPythonOperator
and use the Hook/Producer directly.Example 1 - dynamically route messages to a topic based on upstream status:
Example 2 - access the context variables, e.g. DagRun or TaskInstance, from
producer_function
:Tested this manually. Unfortunately, I don't know how to write a unit test for this.