-
Couldn't load subscription status.
- Fork 680
feat(databricks): allow read_only option for Databricks backend #11648
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
base: main
Are you sure you want to change the base?
feat(databricks): allow read_only option for Databricks backend #11648
Conversation
|
Is there a way we can support local data (pandas dataframes, polars dataframes, etc) that doesn't require a user to have volume writing permissions? Lots of useful features require memtables, so it'd be nice if we can make this work without this flag. |
|
Hi @cpcloud, Not sure what you mean by "support local table", it would be to replace the volume created by a local table instead I guess. Then a local path would lead to a local table validation/creation, without any CREATE VOLUME required. I'll look into it! |
4ea393e to
84b35a7
Compare
…as memtable_volume argument fixes ibis-project#11598
Add manual switch to keep memtable_volume None if it is, in 'do_connect' Return None when memtable is None in common memory table operations (_verify_in_memory_tables_are_unique and _make_memtable_finalizer)
…l both databricks and Polars backends
7b862c0 to
9c2198d
Compare
Description of changes
Allow data access through Databricks with only READ access on the table, by skipping memory table.
Issues closed