bugraoz93 commented on PR #54034: URL: https://github.com/apache/airflow/pull/54034#issuecomment-3146667957
> @bugraoz93 I think it would be hard to drop the functionality to support empty string, since users might have a lot of connection and might end up getting failed imports, which could be a problem. We already had some [issue](https://github.com/apache/airflow/issues/49734) reported in 3.0.0, I think we can give an exception to the empty string, anyways we are supporting to edit an empty string in extra due to the issue mentioned. I haven't meant to drop supporting it but rather storing in the database in a unified way. I support backwards compatibility importing from older versions to newer versions for a smooth transition but this doesn't necessarily mean they will be persisted as the default empty string. This means export from a newer version can work on newer versions. It could be even invisible to users if they aren't reading newsletters before updates or following up on database changes. If there is a lot of automation on it across users, we may be even more relaxed about it, I am not against that. -- 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]
