Closed maslick closed 8 months ago
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 approval.
Hi @john-jac! Given your expertise in this area, I thought your insights could be incredibly helpful. Would you and your team be able to take a look at this issue and share your thoughts? Your input would be greatly appreciated :) Thanks in advance.
Please open that issue in the issue tracker of MWAA . This is not an Airflow issue. We are not handling MWAA issues here.
Reposted in the aws-mwaa-local-runner
repository maintained by AWS. The issue can be found at https://github.com/aws/aws-mwaa-local-runner/issues/340
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).Operating System
N/A (running in MWAA, so Amazon Linux 2 I believe)
Versions of Apache Airflow Providers
Default that come with MWAA v2.6.3 (see https://docs.aws.amazon.com/mwaa/latest/userguide/connections-packages.html#connections-packages-table-263)
Deployment
Amazon (AWS) MWAA
Deployment details
No response
Anything else?
No response
Are you willing to submit PR?
Code of Conduct