Re: [I] Dynamic mapped tasks group arguments are interpreted as MappedArgument when provided to classic operators [airflow]

2024-07-11 Thread via GitHub
potiuk closed issue #39222: Dynamic mapped tasks group arguments are interpreted as MappedArgument when provided to classic operators URL: https://github.com/apache/airflow/issues/39222 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to Gi

Re: [I] Dynamic mapped tasks group arguments are interpreted as MappedArgument when provided to classic operators [airflow]

2024-07-11 Thread via GitHub
potiuk commented on issue #39222: URL: https://github.com/apache/airflow/issues/39222#issuecomment-919010 Converting it to a discussion - as it is unlikely to be an "airflow issue" -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

Re: [I] Dynamic mapped tasks group arguments are interpreted as MappedArgument when provided to classic operators [airflow]

2024-07-11 Thread via GitHub
potiuk commented on issue #39222: URL: https://github.com/apache/airflow/issues/39222#issuecomment-917953 Yes. And you can use simply Python subprocess.* calls to run bash script in such taskflow-decorated method, there is no particular need to use BashOperator for that if you can just

Re: [I] Dynamic mapped tasks group arguments are interpreted as MappedArgument when provided to classic operators [airflow]

2024-07-11 Thread via GitHub
Locustv2 commented on issue #39222: URL: https://github.com/apache/airflow/issues/39222#issuecomment-375285 The only workaround would be to use taskflow or not use mapped argument IMO -- This is an automated message from the Apache Git Service. To respond to the message, please log on

Re: [I] Dynamic mapped tasks group arguments are interpreted as MappedArgument when provided to classic operators [airflow]

2024-07-09 Thread via GitHub
florian-guily commented on issue #39222: URL: https://github.com/apache/airflow/issues/39222#issuecomment-2217902808 didn't find a proper workaround to use non-taskflow operators so i just used python operator for everything. I'm investigating on the fix but i'm fairly new to open so

Re: [I] Dynamic mapped tasks group arguments are interpreted as MappedArgument when provided to classic operators [airflow]

2024-07-09 Thread via GitHub
d-callan commented on issue #39222: URL: https://github.com/apache/airflow/issues/39222#issuecomment-2217876185 wondering if there is a known work-around in the mean time? or an update on this? @florian-guily ? -- This is an automated message from the Apache Git Service. To respond to the

Re: [I] Dynamic mapped tasks group arguments are interpreted as MappedArgument when provided to classic operators [airflow]

2024-05-31 Thread via GitHub
Locustv2 commented on issue #39222: URL: https://github.com/apache/airflow/issues/39222#issuecomment-2142258553 More examples: 1. https://github.com/apache/airflow/issues/31481 2. https://github.com/apache/airflow/discussions/39927 -- This is an automated message from the Apache

Re: [I] Dynamic mapped tasks group arguments are interpreted as MappedArgument when provided to classic operators [airflow]

2024-05-13 Thread via GitHub
joshtree41 commented on issue #39222: URL: https://github.com/apache/airflow/issues/39222#issuecomment-2109022868 Noticing this issue as well, tested a task group with task flow API and the arguments get picked up properly, but when passed to traditional operators they don't get picked up p

Re: [I] Dynamic mapped tasks group arguments are interpreted as MappedArgument when provided to classic operators [airflow]

2024-05-08 Thread via GitHub
renzo-sanchez-h commented on issue #39222: URL: https://github.com/apache/airflow/issues/39222#issuecomment-2100960245 > > > > Hello there, I've just encountered the same issue. > > It doesn't only happen with classic operators, but anything in a task group scope, such as:

Re: [I] Dynamic mapped tasks group arguments are interpreted as MappedArgument when provided to classic operators [airflow]

2024-05-07 Thread via GitHub
florian-guily commented on issue #39222: URL: https://github.com/apache/airflow/issues/39222#issuecomment-2099548426 > Hello there, I've just encountered the same issue. > It doesn't only happen with classic operators, but anything in a task group scope, such as: > > ``` > @task

Re: [I] Dynamic mapped tasks group arguments are interpreted as MappedArgument when provided to classic operators [airflow]

2024-05-07 Thread via GitHub
renzo-sanchez-h commented on issue #39222: URL: https://github.com/apache/airflow/issues/39222#issuecomment-2098964742 Hello there, I've just encountered the same issue. It not only happens with classic operators, but anything in a task group scope, such as: ` @task_group def

Re: [I] Dynamic mapped tasks group arguments are interpreted as MappedArgument when provided to classic operators [airflow]

2024-04-24 Thread via GitHub
florian-guily commented on issue #39222: URL: https://github.com/apache/airflow/issues/39222#issuecomment-2075777459 > @florian-guily Would you like to be assigned to this issue? I'd like to yes, i'll find the time to resolve it ! -- This is an automated message from the Apache Git

Re: [I] Dynamic mapped tasks group arguments are interpreted as MappedArgument when provided to classic operators [airflow]

2024-04-24 Thread via GitHub
RNHTTR commented on issue #39222: URL: https://github.com/apache/airflow/issues/39222#issuecomment-2075666741 @florian-guily Would you like to be assigned to this issue? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use

Re: [I] Dynamic mapped tasks group arguments are interpreted as MappedArgument when provided to classic operators [airflow]

2024-04-24 Thread via GitHub
boring-cyborg[bot] commented on issue #39222: URL: https://github.com/apache/airflow/issues/39222#issuecomment-2074407340 Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for ap

[I] Dynamic mapped tasks group arguments are interpreted as MappedArgument when provided to classic operators [airflow]

2024-04-24 Thread via GitHub
florian-guily opened a new issue, #39222: URL: https://github.com/apache/airflow/issues/39222 ### Apache Airflow version Other Airflow 2 version (please specify below) ### If "Other Airflow 2 version" selected, which one? 2.8.4 ### What happened? When using