[Snyk] Security upgrade pyarrow from 0.13.0 to 0.15.1

[snyk-bot]

Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • requirements_all_ds.txt

⚠️ Warning

snowflake-connector-python 2.3.4 has requirement pytz<2021.0, but you have pytz 2022.4.
snowflake-connector-python 2.3.4 has requirement urllib3<1.26.0,>=1.20, but you have urllib3 1.26.12.
snowflake-connector-python 2.3.4 has requirement certifi<2021.0.0, but you have certifi 2022.9.24.
snowflake-connector-python 2.3.4 has requirement requests<2.24.0, but you have requests 2.28.1.
rbc-project 0.8.0 requires numba, which is not installed.
pyOpenSSL 20.0.1 has requirement cryptography>=3.2, but you have cryptography 2.9.2.
pymapd 0.19.0 requires pandas, which is not installed.
pymapd 0.19.0 requires numpy, which is not installed.
pymapd 0.19.0 requires pyarrow, which is not installed.
pymapd 0.19.0 has requirement thrift==0.11.0, but you have thrift 0.16.0.
pyathena 2.14.0 has requirement botocore>=1.24.7, but you have botocore 1.18.0.
pyathena 2.14.0 has requirement boto3>=1.21.0, but you have boto3 1.14.63.
memsql 3.0.0 requires mysqlclient, which is not installed.
httplib2 0.20.4 has requirement pyparsing!=3.0.0,!=3.0.1,!=3.0.2,!=3.0.3,<4,>=2.4.2; python_version > "3.0", but you have pyparsing 2.1.4.
botocore 1.18.0 has requirement urllib3<1.26,>=1.20; python_version != "3.4", but you have urllib3 1.26.12.
boto3 1.14.63 has requirement botocore<1.18.0,>=1.17.63, but you have botocore 1.18.0.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	454/1000 Why? Has a fix available, CVSS 4.8	Use of Uninitialized Variable SNYK-PYTHON-PYARROW-483026	pyarrow: 0.13.0 -> 0.15.1	No	No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

Check the changes in this PR to ensure they won't cause issues with your project.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.