dolt 1.31.0#159361
Merged
BrewTestBot merged 2 commits intoHomebrew:masterfrom Jan 8, 2024
BrewTestBot:bump-dolt-1.31.0
Merged
Conversation
chenrui333
approved these changes
Jan 8, 2024
Contributor
|
🤖 An automated task has requested bottles to be published to this PR. |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Created by
brew bumpCreated with
brew bump-formula-pr.Details
release notes
Three changes to the
dolt sqlshell:mydb/main>I recommend looking at one commit at a time.
This PR implemented the "Primary Goal" outlined in this doc.
Basically, when two branches in a merge both modify the same JSON value, but touch different keys, dolt should be able to automatically resolve the merge by doing a Three Way Merge that compares the value on both branches to the value at a common ancestor.
This implementation deviates from the strategy outlined in the doc in one major way: when a branch contains an edit to a nested object, we don't run the diff or merge algorithms recursively. Instead, we generate a diff that contains a JSON path to the modified object. Doing this allows us to generate all the diffs in a single linear pass, and is still easy to reason about what changes are conflicts.
We discussed only performing this merge on JSON objects below a certain size for performance reasons, but the size of the object isn't actually visible to the merge algorithm. Given that this algorithm only runs for rows that would otherwise have a merge conflict, all dolt merges that succeed before this PR should see zero performance impact from this change, so I'm not worried about performance.
go-mysql-server
SYSDATE()functionAdds support for the
SYSDATE()function.Related to: Please implement SYSDATE for Mediawiki install dolthub/dolt#7270
fixes: Panic when Using
INNER JOINwith String inINdolthub/dolt#7262Some table nodes need to be executed as IndexScans with mandatory filters. The new interface makes this transparent to join planning.
re: [no-release-notes] bump and test for required commit_diff index predicates dolthub/dolt#7256
Cardinality estimation happens once after join reordering, indexing, and lookup join planning. The indexes and lookups help with result count estimates.
Closed Issues
INNER JOINwith String inIN