Re: [I] Names for expanded tasks [airflow]

2024-02-26 Thread via GitHub
uranusjr commented on issue #23020: URL: https://github.com/apache/airflow/issues/23020#issuecomment-1965800647 Implemented in #36797. -- 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

Re: [I] Names for expanded tasks [airflow]

2024-02-26 Thread via GitHub
uranusjr closed issue #23020: Names for expanded tasks URL: https://github.com/apache/airflow/issues/23020 -- 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-mai

Re: [I] Names for expanded tasks [airflow]

2024-02-07 Thread via GitHub
RNHTTR commented on issue #23020: URL: https://github.com/apache/airflow/issues/23020#issuecomment-1933020783 > @RNHTTR are you working on it? yep! https://github.com/apache/airflow/pull/36797 -- This is an automated message from the Apache Git Service. To respond to the message, pl

Re: [I] Names for expanded tasks [airflow]

2024-02-07 Thread via GitHub
damjad commented on issue #23020: URL: https://github.com/apache/airflow/issues/23020#issuecomment-1932675131 @RNHTTR are you working on it? -- 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 sp

Re: [I] Names for expanded tasks [airflow]

2024-01-07 Thread via GitHub
kaxil commented on issue #23020: URL: https://github.com/apache/airflow/issues/23020#issuecomment-1880105381 > I'm interested in taking this on (or at least moving it forward). Would it be sufficient to start by: > > 1. Adding something like `named_mapped_index` to BaseOperator and as

Re: [I] Names for expanded tasks [airflow]

2024-01-07 Thread via GitHub
RNHTTR commented on issue #23020: URL: https://github.com/apache/airflow/issues/23020#issuecomment-1880089536 I'm interested in taking this on (or at least moving it forward). Would it be sufficient to start by: 1. Adding something like `named_mapped_index` to BaseOperator and as a c

Re: [I] Names for expanded tasks [airflow]

2023-12-18 Thread via GitHub
potiuk commented on issue #23020: URL: https://github.com/apache/airflow/issues/23020#issuecomment-1861821868 > It looks like this issue has lost moment but we really need some sort of tag or label attribute that could be assigned per mapped task instance and surfaced in the airflow UI to a

Re: [I] Names for expanded tasks [airflow]

2023-12-18 Thread via GitHub
paulg-mscience commented on issue #23020: URL: https://github.com/apache/airflow/issues/23020#issuecomment-1861262894 @kaxil Is this something you can influence and push through? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

Re: [I] Names for expanded tasks [airflow]

2023-12-18 Thread via GitHub
paulg-mscience commented on issue #23020: URL: https://github.com/apache/airflow/issues/23020#issuecomment-1861257150 It looks like this issue has lost moment but we really need some sort of tag or label attribute that could be assigned per mapped task instance and surfaced in the airflow U