-
Notifications
You must be signed in to change notification settings - Fork 80
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
Relational data ingestion via ADBC/ODBC #3279
Relational data ingestion via ADBC/ODBC #3279
Conversation
a8c79be
to
d33cc6d
Compare
d33cc6d
to
8b64035
Compare
d23f020
to
f836431
Compare
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.
My only comment here is that really the JDBC integration looks exactly like this usage:
cursor.execute("SELECT t_ts, t_exchange, t_price, t_size FROM CRYPTO_TRADES "
"LIMIT 1000")
It feels like an extra step pulling this into python's arrow format then translating, with another copy, into a deephaven table.
Wrapping the arrow column sources as accessible directly from DH's engine probably mitigates the concern of yet-another-copy. But, the API looks pretty similar (if not identical) to the java API.
f836431
to
a0a04b5
Compare
Remove unwanted comment
Co-authored-by: Chip Kent <[email protected]>
4043a5f
to
3243767
Compare
Labels indicate documentation is required. Issues for documentation have been opened: How-to: https://github.com/deephaven/deephaven.io/issues/2123 |
Fixes #3131