-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
84555: sql: make sequence integer bound consistent with `default_int_size` r=ZhouXing19 a=ZhouXing19 This PR is based on #84034. Please just look at the 2nd commit. I'll rebase this PR once #84034 is merged. Previously, the default bounds of sequence are always`math.MaxInt64` or `math.MinInt64` (depending on the sequence's order). This can be inconsistent with the cluster setting `default_int_size`. This commit is to fix it. fixes #84554 Release note (bug fix): make sequence integer bound consistent with the cluster setting `default_int_size`. Release justification: fix a bug of sequence integer bound 86253: changefeedccl: make core changefeeds more resilient r=jayshrivastava a=jayshrivastava This change updates core changefeeds to save checkpoints inside the EvalCtx. With this change, core changefeeds can retry from the last checkpoint instead of restarting from the beginning. Fixes: #84511 Release note (general change): This change updates core/experimental changefeeds to be more resilient to transient errors (ex. network blips) by adding checkpointing. Previously, transient errors would result in a core changefeed stopping and terminating the underlying SQL statement. This would require the SQL statement to be restarted by a user. Furtheremore, if the core changefeed were restarted during an inital scan, the initial scan would start from the beginning. For large initial scans, transient errors are more likely, so restarting from the beginning would likely see more transient errors and restarts which would not progress the changefeed. Now, an experimental changefeed will automatically take frequent checkpoints and retry from the last checkpoint when a transient errors occurs. Release justification: This change updates an experimental feature. 86272: insights: execution_insights_capacity cluster setting r=matthewtodd a=matthewtodd Fixes #79450. Whereas we previously retained only the 10 most recent insights, we now let the user choose how many they'd like to hang onto. It may make sense to be more sophisticated than a simple LRU cache here: perhaps we won't want a single fingerprint to dominate the list. That work is captured in #86271. Release justification: Category 2: Bug fixes and low-risk updates to new functionality. Release note (ops change): The `sql.insights.execution_insights_capacity` cluster setting was introduced, limiting the number of SQL execution insights retained in memory per node. 86329: ui/cluster-ui: show status as waiting when txn is waiting for lock r=xinhaoz a=xinhaoz Now that we have surfaced contention information in the UI, we can update the stmt / txn status field for active executions to be 'Waiting' when the stmt or txn is waiting to acquire a lock. Release justification: low risk update to existing functionality Release note (ui change): txns and stmts in active exec pages that are waiting for a lock will now have the status 'Waiting' <img width="654" alt="image" src="https://user-images.githubusercontent.com/20136951/185226858-8c194582-d405-4c8b-aec9-7a21a4bc1c22.png"> 86348: sql/stats: remove NumRange-stealing behavior from histogram prediction r=yuzefovich,rytaft a=michae2 We should be able to handle NumEq=0 just fine everywhere that uses histograms, so delete this NumRange-stealing code. Fixes: #86344 Release justification: low-risk updates to new functionality. Release note: None 86383: sql: move UDF execution tests to bottom of test file r=mgartner a=mgartner This commit moves UDF execution logic tests to the bottom of the UDF test file so that execution-related tests add in the future will not change the output of schema-related tests. Release justification: This is a test-only change. Release note: None 86385: opt: clarify the return type of Index.Ordinal() r=mgartner a=mgartner The return type of `Index.Ordinal()` is now the type alias `cat.IndexOrdinal` to be consistent with other functions that use an index ordinal, like `Table.Index(i cat.IndexOrdinal)`. It is now more clear that `idx == Table().Index(idx.Ordinal())` Release justification: This is a very small, low-risk change. Release note: None Co-authored-by: Jane Xing <[email protected]> Co-authored-by: Jayant Shrivastava <[email protected]> Co-authored-by: Matthew Todd <[email protected]> Co-authored-by: Xin Hao Zhang <[email protected]> Co-authored-by: Michael Erickson <[email protected]> Co-authored-by: Marcus Gartner <[email protected]>
- Loading branch information
Showing
31 changed files
with
796 additions
and
413 deletions.
There are no files selected for viewing
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 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 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 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 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 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
Oops, something went wrong.