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
release deltalake 0.4 #319
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit 4ad7426.
This isn't related to #222 but I saw the missing integration test coverage
…r files in a partition This commit also adds an integration test but I have not yet manually tested this with Azure or S3 storage providers Fixes #222
… and losing data This lays the groundwork exposing file stats to consumers of the public Rust API See #45
This data set contains file statistics. Apparently none of the golden data sets, nor our pre-existing data sets have per-file statistics in them, making them very unhelpful for tests :) Incorporated with permission from @dennyglee
Co-authored-by: R. Tyler Croy <rtyler@brokenco.de>
I deleted these resources in my Azure account 🤷
Originally authored by @xianwill
…he "add" action This API might receive some changes to accommodate users which need to provide `txn` actions along with the add_file
…actions This should support use-cases where the caller needs to put a txn or two into the log
…level writer interface I envision this writers module encapsulating a few different flavors of high-level writers. The exact syntax/API surface that should be common for all the high-level writers should be largely identical but I'm not ready to stabilize around what's here for that. I also am on the fence on how this should handle (or not handle) `txn` actions
…, and finish up BufferedJSONWriter There are some optimizations that come to mind for this work, but at this point I think it's ready for simple high-level JSON writer usage
This commit also addresses a number of other code review comments
* Added .to_pandas to deltalake python * Fixed linting issue * Changed pandas import. Check pandas only during type checking * Ignore pd.DataFrame during type check
also extend typechecks to python tests
…295) * Make dynamodb lease_duration optional to support non-expirable lock * Add do_not_timeout_on_non_expirable_locks and unit tests * Refactor has_timed_out options check * Remove unneeded do_not_timeout_on_non_expirable_locks option
* Add delta-checkpoint release workflow
…ics for Datafusion `TableProvider` (#308) * Expose delta statistics * Start using statistics from delta
* Expose, calculate number of records in table provider * Add TODO
anyone remember why we named the release branch 3.x? |
OK, i think this was a typo, was supposed to be 0.3.x :( |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Get a new release out before we upgrade to arrow/parquet to 5.x