MaksYermak commented on PR #40421:
URL: https://github.com/apache/airflow/pull/40421#issuecomment-2444255761
> @VladaZakharova @MaksYermak -> I see we have no feedback here, but my
question is - how eager you are to get this merged? There are some risks
involved if we release it in 2.10.3 - because we want to really avoid relasing
2.10.4 quickly. On the other hand the whole mechanism of connection UI
management will be rewritten from scratch in Airflow 3. And there are
workarounds for the problem (delete and recreate the connection).
>
> So without having any clue from @josh-fell and @dstandish (they likely
don't remember either, though it would be nice to hear back) about the actual
problem that introduced this "limitation" - I'd say it's a bit risky to merge
that one and backport it for 2.10.3.
>
> Is there an important reason why we want to get this case fixed?
Hello @potiuk
In Composer we have a customer issue related to this problem. Also I have
one more solution for this problem which is to save current behavior and delete
value if the user decides to delete it on UI. Here's the code:
```
if value != "":
extra[field_name] = value
elif field_name in extra:
del extra[field_name]
```
In my opinion this solution is not risky, because the current behavior is
saved. And if we don't have any answer from contributors we can use this
solution as a safety one for fixing this problem. WDYT?
--
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]
