- Notifications
You must be signed in to change notification settings - Fork126
Readme updates#4
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
moderakh left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
LGTM. Thanks@susodapop
README.md Outdated
| The Databricks SQL Connector for Python allows you to develop Python applications that connect to Databricks clusters and SQL warehouses. It is a Thrift-based client with no dependencies on ODBC or JDBC. And it conforms to the[Python DB API 2.0 specification](https://www.python.org/dev/peps/pep-0249/). | ||
| Documentation can be found here:[Databricks SQL Connector for Python](https://docs.databricks.com/dev-tools/python-sql-connector.html). | ||
| The initial public release (`v1.0`) was a very lightly modified version of[PyHive](https://pypi.org/project/PyHive/). The`v2.0` release was a complete from scratch re-write, with the same public API. Since`v2.0`, it uses Arrow as the data-exchange format.`v2.0` also supports APIs to directly fetch Arrow tables. Arrow tables are wrapped in the`ArrowQueue` class to provide a natural API to get several rows at a time. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
The
v2.0release was a complete from scratch re-write, with the same public API.
can a customer who is using v1. just bump the version of dependency and use v1 in their code without making any code change other than version bump?
are there any breaking changes from v1 -> v2?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
I think so, yes. However, after conferring with@taotao-db I removed the reference to the v1 connector. I included it originally because I was confused. I thought the v1 code was contained in the commit history here. But it's actually housed elsewhere and will not be open sourced AFAIK. So best not to reference it here to avoid confusion.
…blesget tables function modified
Signed-off-by: Sai Shree Pradhan <saishree.pradhan@databricks.com>
Updating the README prior to announcing the public release at DAIS.