Open maslick opened 8 months ago
I'm not sure where you're seeing the discrepancy. The current constraint looks to be 2.2.8
as expected, on the v2.6.3
branch: https://github.com/aws/aws-mwaa-local-runner/blob/v2.6.3/docker/config/constraints.txt#L510.
Could you send the link to the constraint file you were looking at?
@mayushko26 you have to run an MWAA environment in AWS (not a local Docker environment). It uses pymssql 2.2.7
I see, I originally misunderstood what you meant. You're correct, there is a mismatch. In MWAA, in rare cases, we will change the version in the default constraints for the environment due to dependency or security issues, but this is not one of those cases to my memory.
I notice that pymssql
in particular had a version-bump for 2.6.3 in this commit: https://github.com/apache/airflow/commit/4bdb4b13df8966c20b7cb307356f12a97e2065ac. This commit is dated approximately a month after 2.6.3 was officially released, so it's likely that it has fallen out of sync due to that reason; since new versions to the local runner are generally added about a month after release.
I'll need to sync up with the MWAA team to see if we can change the version in MWAA, and make sure it doesn't unexpectedly break existing customer environments.
Apache Airflow version
Other Airflow 2 version (please specify below)
If "Other Airflow 2 version" selected, which one?
2.6.3
What happened?
I recently ran a task using a BashOperator on a new Managed Workflows for Apache Airflow (MWAA) v2.6.3 instance, which involved reading the
/constraints.txt
file. During this operation, I noticed a discrepancy in the version of thepymssql
library listed in the MWAA environment compared to the version specified in the Airflow constraints file on GitHub.In the MWAA's
/constraints.txt
file (source [1]), the version ofpymssql
is specified aspymssql==2.2.7
. However, the corresponding constraints file on GitHub (source [2], accessible at https://raw.githubusercontent.com/apache/airflow/constraints-2.6.3/constraints-3.10.txt), which is referenced in the first line of [1], listspymssql
aspymssql==2.2.8
.This version inconsistency with
pymssql
might result in unexpected behavior and challenges in dependency management within the environment. I seek clarification on this discrepancy, particularly from the MWAA team due to their significant contributions to this repository. Any guidance on how to reconcile these version differences would be greatly appreciated.source [1]
source [2]
What you think should happen instead?
Ideally, MWAA v2.6.3 should align with the Airflow constraints file by using pymssql==2.2.8 instead of pymssql==2.2.7. If there is a deliberate rationale for using the older version (pymssql==2.2.7) in MWAA, this reasoning should be explicitly documented in MWAA's documentation for clarity and transparency.
How to reproduce
pymssql
version: 2.2.7 (in question) vs 2.2.8 (Github).