Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: update recommended pyathena version #24200

Closed
wants to merge 1 commit into from
Closed

docs: update recommended pyathena version #24200

wants to merge 1 commit into from

Conversation

boenshao
Copy link
Contributor

SUMMARY

The recommended version of pyathena in the doc is PyAthena>1.2.0, which is not in sync with the version specified in setup.py, which is pyathena[pandas]>=2,<3.

If pyathena v3 is installed, it will result in a runtime error Name "Optional" is not defined. Revert back to v2 resolved the issue and the connection works correctly.

Also, other packages lack version constrain in the same doc, should I also update them? Let me know.

Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Congrats on making your first PR and thank you for contributing to Superset! 🎉 ❤️

We hope to see you in our Slack community too! Not signed up? Use our Slack App to self-register.

@@ -22,8 +22,8 @@ A list of some of the recommended packages.

| Database | PyPI package | Connection String |
| --------------------------------------------------------- | ---------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| [Amazon Athena](/docs/databases/athena) | `pip install "PyAthenaJDBC>1.0.9` , `pip install "PyAthena>1.2.0` | `awsathena+rest://{aws_access_key_id}:{aws_secret_access_key}@athena.{region_name}.amazonaws.com/{ ` |
| [Amazon DynamoDB](/docs/databases/dynamodb) | `pip install "PyDynamoDB>=0.4.2` | `dynamodb://{access_key_id}:{secret_access_key}@dynamodb.{region_name}.amazonaws.com?connector=superset` |
| [Amazon Athena](/docs/databases/athena) | `pip install "PyAthenaJDBC>1.0.9"` , `pip install "pyathena[pandas]>=2,<3"` | `awsathena+rest://{aws_access_key_id}:{aws_secret_access_key}@athena.{region_name}.amazonaws.com/{ ` |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe it would be better if we treat this table as an example and point the reader to the files where the most up to date versions can be found such as setup.py and requirements/*. That way, this documentation will be more resilient to version upgrades.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree, should I extend the scope of the current PR, or open a new PR for this?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for opening a new PR for it.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@michael-s-molina
I tried looking into this issue once before. I couldn't figure out why this table had been changed from referencing the optional extras requirements that are managed in the setup.py to the state the table now is in where it no longer specifies the optional extras requirements but instead directly lists the actual driver package names in the documentation table itself.

I think there is a bigger question of how to manage the driver compatibility and support in general. I.e. should the be such a concept of "officially supported and tested drivers" that should have an expectation of always working, vs community-supported and tested drivers?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's an interesting question @cwegener. My suggestion would be to create a GitHub discussion and tag some folks such as @dpgaspar @villebro @john-bodley @rusackas @betodealmeida and myself or bring this to the Town Hall.

@boenshao boenshao closed this May 28, 2023
@boenshao boenshao deleted the docs/update-recommended-pyathena-version branch May 30, 2023 14:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants