Merged PRs

dolt

• 5734: Fixed panic in dolt_commit_diff tables when referring to commits where the table doesn't exist
  Fixes #5730
• 5733: Fixed a bug in auto increment tracking
  Fixes #5731
  Previously auto-increment tracking was only considering locally checked out branches. It needs to consider remote branches as well.
• 5728: go/libraries/doltcore/merge: refactored unique index validation
  fixes #5719 and #4547
• 5724: Bump xml2js and aws-sdk in /.github/actions/ses-email-action
  Bumps xml2js to 0.5.0 and updates ancestor dependency aws-sdk. These dependencies need to be updated together.
  Updates xml2js from 0.4.19 to 0.5.0
  Commits

  • 9f730bb Update package.json with latest PR
  • 50a492a Merge pull request #603 from autopulated/master
  • 7bc3c5d Merge pull request #598 from fnimick/master
  • f412a12 Merge pull request #635 from wisesimpson/patch-1
  • d318ce0 Update README.md
  • 581b19a use Object.create(null) to create all parsed objects (prevent prototype repla...
  • a212950 Add documentation for explicitCharkey option
  • 1832e0b Merge pull request #512 from economia/master
  • 198063c Merge pull request #556 from Omega-Ariston/fix-issue544
  • 0d71785 Merge pull request #562 from Omega-Ariston/addDocExample
  • Additional commits viewable in compare view
  
  Updates `aws-sdk` from 2.828.0 to 2.1354.0
  Release notes

  Sourced from aws-sdk's releases.

  Release v2.1354.0

  See changelog for more information.

  Release v2.1353.0

  See changelog for more information.

  Release v2.1352.0

  See changelog for more information.

  Release v2.1351.0

  See changelog for more information.

  Release v2.1350.0

  See changelog for more information.

  Release v2.1349.0

  See changelog for more information.

  Release v2.1348.0

  See changelog for more information.

  Release v2.1347.0

  See changelog for more information.

  Release v2.1346.0

  See changelog for more information.

  Release v2.1345.0

  See changelog for more information.

  Release v2.1344.0

  See changelog for more information.

  Release v2.1343.0

  See changelog for more information.

  Release v2.1342.0

  See changelog for more information.

  Release v2.1341.0

  See changelog for more information.

  Release v2.1340.0

  See changelog for more information.

  Release v2.1339.0

  See changelog for more information.

  Release v2.1338.0

  See changelog for more information.

  ... (truncated)

  Changelog

  Sourced from aws-sdk's changelog.

  2.1354.0

  • feature: Connect: This release adds the ability to configure an agent's routing profile to receive contacts from multiple channels at the same time via extending the UpdateRoutingProfileConcurrency, CreateRoutingProfile and DescribeRoutingProfile APIs.
  • feature: ECS: This release adds support for enabling FIPS compliance on Amazon ECS Fargate tasks
  • feature: MarketplaceCatalog: Added three new APIs to support resource sharing: GetResourcePolicy, PutResourcePolicy, and DeleteResourcePolicy. Added new OwnershipType field to ListEntities request to let users filter on entities that are shared with them. Increased max page size of ListEntities response from 20 to 50 results.
  • feature: MediaConvert: AWS Elemental MediaConvert SDK now supports conversion of 608 paint-on captions to pop-on captions for SCC sources.
  • feature: Omics: Remove unexpected API changes.
  • feature: Rekognition: This release adds support for Face Liveness APIs in Amazon Rekognition. Updates UpdateStreamProcessor to return ResourceInUseException Exception. Minor updates to API documentation.

  2.1353.0

  • feature: DLM: Updated timestamp format for GetLifecyclePolicy API
  • feature: DocDB: This release adds a new parameter 'DBClusterParameterGroupName' to 'RestoreDBClusterFromSnapshot' API to associate the name of the DB cluster parameter group while performing restore.
  • feature: Lambda: This release adds a new Lambda InvokeWithResponseStream API to support streaming Lambda function responses. The release also adds a new InvokeMode parameter to Function Url APIs to control whether the response will be streamed or buffered.
  • feature: QuickSight: This release has two changes: adding the OR condition to tag-based RLS rules in CreateDataSet and UpdateDataSet; adding RefreshSchedule and Incremental RefreshProperties operations for users to programmatically configure SPICE dataset ingestions.

  2.1352.0

  • feature: CloudFormation: Including UPDATE_COMPLETE as a failed status for DeleteStack waiter.
  • feature: GreengrassV2: Add support for SUCCEEDED value in coreDeviceExecutionStatus field. Documentation updates for Greengrass V2.
  • feature: Proton: This release adds support for the AWS Proton service sync feature. Service sync enables managing an AWS Proton service (creating and updating instances) and all of it's corresponding service instances from a Git repository.

  2.1351.0

  • feature: AppRunner: App Runner adds support for seven new vCPU and memory configurations.
  • feature: ConfigService: This release adds resourceType enums for types released in March 2023.
  • feature: IVSRealTime: Fix ParticipantToken ExpirationTime format
  • feature: NetworkFirewall: AWS Network Firewall now supports IPv6-only subnets.
  • feature: ServiceCatalog: removed incorrect product type value

  2.1350.0

  • feature: AmplifyUIBuilder: Support StorageField and custom displays for data-bound options in form builder. Support non-string operands for predicates in collections. Support choosing client to get token from.
  • feature: DataExchange: This release updates the value of MaxResults.
  • feature: EC2: C6in, M6in, M6idn, R6in and R6idn bare metal instances are powered by 3rd Generation Intel Xeon Scalable processors and offer up to 200 Gbps of network bandwidth.
  • feature: ElasticInference: Updated public documentation for the Describe and Tagging APIs.
  • feature: SageMaker: Amazon SageMaker Asynchronous Inference now allows customer's to receive failure model responses in S3 and receive success/failure model responses in SNS notifications.
  • feature: SageMakerRuntime: Amazon SageMaker Asynchronous Inference now provides customers a FailureLocation as a response parameter in InvokeEndpointAsync API to capture the model failure responses.
  • feature: WAFV2: This release rolls back association config feature for webACLs that protect CloudFront protections.

  2.1349.0

  • feature: Glue: Add support for database-level federation
  • feature: LakeFormation: Add support for database-level federation
  • feature: LicenseManager: This release adds grant override options to the CreateGrantVersion API. These options can be used to specify grant replacement behavior during grant activation.
  • feature: MWAA: This Amazon MWAA release adds the ability to customize the Apache Airflow environment by launching a shell script at startup. This shell script is hosted in your environment's Amazon S3 bucket. Amazon MWAA runs the script before installing requirements and initializing the Apache Airflow process.
  • feature: ServiceCatalog: This release introduces Service Catalog support for Terraform open source. It enables 1. The notify* APIs to Service Catalog. These APIs are used by the terraform engine to notify the result of the provisioning engine execution. 2. Adds a new TERRAFORM_OPEN_SOURCE product type in CreateProduct API.
  • feature: WAFV2: For web ACLs that protect CloudFront protections, the default request body inspection size is now 16 KB, and you can use the new association configuration to increase the inspection size further, up to 64 KB. Sizes over 16 KB can incur additional costs.

  2.1348.0

  • feature: InternetMonitor: This release adds a new feature for Amazon CloudWatch Internet Monitor that enables customers to deliver internet measurements to Amazon S3 buckets as well as CloudWatch Logs.
  • feature: SMS: Deprecating AWS Server Migration Service.
  • feature: SageMakerFeatureStoreRuntime: In this release, you can now chose between soft delete and hard delete when calling the DeleteRecord API, so you have more flexibility when it comes to managing online store data.

  2.1347.0

  • feature: Athena: Make DefaultExecutorDpuSize and CoordinatorDpuSize fields optional in StartSession

  ... (truncated)

  Commits

  • a99fac5 Updates SDK to v2.1354.0
  • 62847a4 Bump xml2js to 0.5.0 (#4389)
  • 56ad952 Updates SDK to v2.1353.0
  • 8a20e16 Updates SDK to v2.1352.0
  • d39ba59 Updates SDK to v2.1351.0
  • 3ee782c Updates SDK to v2.1350.0
  • 8dcb3e2 Updates SDK to v2.1349.0
  • cc11160 Updates SDK to v2.1348.0
  • c58ec67 Updates SDK to v2.1347.0
  • ded882e Updates SDK to v2.1346.0
  • Additional commits viewable in compare view
  
  Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) ---
  Dependabot commands and options

  
  You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/dolthub/dolt/network/alerts).
• 5722: Revert "/go/cmd/dolt/commands/engine/sqlengine.go: close dbs on sql engine close"
  Reverts #5716
• 5716: /go/cmd/dolt/commands/engine/sqlengine.go: close dbs on sql engine close
• 5712: go/store/nbs: correctly handle stashed journal on conjoin
• 5705: sqle: track column renames on alter/modify column
  companion to: dolthub/go-mysql-server#1702
• 5690: Lookup int out of range error
  re: #5673
  companion PR: dolthub/go-mysql-server#1695

go-mysql-server

• 1707: fix JSON map key ordering
  fix for: #5711
• 1704: fix group by over empty result sets
  fix for: #5683
• 1700: OrderedDistinct passes join tree row during exec
  Re: #5700
  OrderedDistinct dropped a parent row while executing a join tree, which caused a field index error in the child.
  The query below has a slightly different plan, but the OrderedDistinct in the right half of a join tree, with a join SEMI_JOIN(scalarSubq0, scalarSubq1) as a child is the issue.

  Project
  ├─ columns: [SUM(xy.x):0!null as SUM(x)]
  └─ GroupBy
  ├─ select: SUM(xy.x:0!null)
  ├─ group:
  └─ Project
  ├─ columns: [xy.x:0!null, xy.y:1]
  └─ HashJoin
  ├─ Eq
  │   ├─ xy.x:0!null
  │   └─ scalarSubq0.u:2!null
  ├─ Filter
  │   ├─ Eq
  │   │   ├─ xy.x:0!null
  │   │   └─ 2 (tinyint)
  │   └─ Table
  │       ├─ name: xy
  │       └─ columns: [x y]
  └─ HashLookup
  ├─ source: TUPLE(xy.x:0!null)
  ├─ target: TUPLE(scalarSubq0.u:0!null)
  └─ CachedResults
  └─ OrderedDistinct
  └─ Project
  ├─ columns: [scalarSubq0.u:0!null]
  └─ SemiJoin
  ├─ Eq
  │   ├─ scalarSubq0.u:2!null
  │   └─ scalarSubq1.a:4!null
  ├─ TableAlias(scalarSubq0)
  │   └─ Table
  │       ├─ name: uv
  │       └─ columns: [u v]
  └─ Filter
  ├─ Eq
  │   ├─ scalarSubq1.a:0!null
  │   └─ 2 (tinyint)
  └─ TableAlias(scalarSubq1)
  └─ Table
  ├─ name: ab
  └─ columns: [a]
  

• 1695: Fix value out of range bug
  re: #5642
• 1663: Return column size in datetime type
  During testing go-mysql-server with Trino and I have noticed that it does work when I have either timestamp or datetime. I have asked them trinodb/trino#16575 whether it's ok for them to implement default column size like they did for Phoenix connector, but they did not want to add it. I still think it should be fine without column size, since most of the clients (except the ones which are written in java) accept date time without column size.
  In order to be fully compatible about it for now I have added 0 as column size for timestamp and datetime

vitess

• 232: go/mysql/conn.go: Improve server-side cursor support.
  1. Send LastRowSent with the result set batch in which the cursor is actually exhausted.
  2. Only send CursorExists in the response to COM_STMT_EXECUTE which creates the cursor.
• 231: support 'show events' statement parsing
  • Added support for SHOW EVENTS statement parsing
  • Added support for SHOW CREATE EVENT statement parsing
  • Removed FULL option from SHOW TRIGGERS as it's not supported in MySQL.

Closed Issues

• 5730: Runtime error when using dolt_commit_diff_$tablename
• 5731: Incorrect autoincrement value being used
• 3081: SHOW PROCEDURE STATUS is always current time
• 5636: Dolt server deadlock with dolt_transaction_commit=1
• 5719: dolt dolt_constraint_violations doesn't show all violations on merge for composite unique keys
• 5441: Dolt does not work with the Postgres MySQL Foreign Data Wrapper
• 3029: Support server side cursors
• 5698: dolt diff --summary no longer shows how many rows were modified
• 5703: dolt panic on SUM(*)
• 5631: Recursive CTE UNION field indexing failure
• 5642: dolt doesn't properly handle large numbers
• 5640: dolt seems to ignore OFFSET sometimes
• 5700: dolt panics with nested WHERE...IN blocks

Latency