potiuk commented on issue #22810:
URL: https://github.com/apache/airflow/issues/22810#issuecomment-1097322156
Indeed, it's reproducible.
It seems that the rason is that the sensor has a serious bug. It tries to
create an operator with the same task id - which makes no sense:
```
class JiraSensor(BaseSensorOperator):
"""
Monitors a jira ticket for any change.
:param jira_conn_id: reference to a pre-defined Jira Connection
:param method_name: method name from jira-python-sdk to be execute
:param method_params: parameters for the method method_name
:param result_processor: function that return boolean and act as a
sensor response
"""
def __init__(
self,
*,
method_name: str,
jira_conn_id: str = 'jira_default',
method_params: Optional[dict] = None,
result_processor: Optional[Callable] = None,
**kwargs,
) -> None:
super().__init__(**kwargs)
self.jira_conn_id = jira_conn_id
self.result_processor = None
if result_processor is not None:
self.result_processor = result_processor
self.method_name = method_name
self.method_params = method_params
self.jira_operator = JiraOperator(. <-- This is wrong
task_id=self.task_id,
jira_conn_id=self.jira_conn_id,
jira_method=self.method_name,
jira_method_args=self.method_params,
result_processor=self.result_processor,
)
```
It should not create operator - it should use Jira Hook instead.
Hopefully someone using Jira could fix it (maybe you could attempt it
@kostiantyn-lab ).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
