Skip to content

[release-21.0] json array insert test#18194

Merged
harshit-gangal merged 2 commits intovitessio:release-21.0from
planetscale:b21-json-arry-insert
May 21, 2025
Merged

[release-21.0] json array insert test#18194
harshit-gangal merged 2 commits intovitessio:release-21.0from
planetscale:b21-json-arry-insert

Conversation

@harshit-gangal
Copy link
Copy Markdown
Member

@harshit-gangal harshit-gangal commented Apr 23, 2025

Description

Added a test in prepared statement that tests json doc column type.
Added prepared statements test suite to upgrade/downgrade test flow.

Related Issue(s)

Checklist

  • Tests were added or are not required
  • Did the new or modified tests pass consistently locally and on CI?
  • Documentation was added or is not required

Deployment Notes

Signed-off-by: Harshit Gangal <harshit@planetscale.com>
@vitess-bot
Copy link
Copy Markdown
Contributor

vitess-bot bot commented Apr 23, 2025

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

  • Ensure that the Pull Request has a descriptive title.
  • Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

  • Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

  • Apply the release notes (needs details) label if users need to know about this change.
  • New features should be documented.
  • There should be some code comments as to why things are implemented the way they are.
  • There should be a comment at the top of each new or modified test to explain what the test does.

New flags

  • Is this flag really necessary?
  • Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

  • Each item in Jobs should be named in order to mark it as required.
  • If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

  • Protobuf changes should be wire-compatible.
  • Changes to _vt tables and RPCs need to be backward compatible.
  • RPC changes should be compatible with vitess-operator
  • If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
  • vtctl command output order should be stable and awk-able.

@vitess-bot vitess-bot bot added NeedsBackportReason If backport labels have been applied to a PR, a justification is required NeedsDescriptionUpdate The description is not clear or comprehensive enough, and needs work NeedsIssue A linked issue is missing for this Pull Request NeedsWebsiteDocsUpdate What it says labels Apr 23, 2025
@github-actions github-actions bot added this to the v21.0.5 milestone Apr 23, 2025
@codecov
Copy link
Copy Markdown

codecov bot commented Apr 23, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.52%. Comparing base (d7cc3f6) to head (401449b).
Report is 14 commits behind head on release-21.0.

Additional details and impacted files
@@               Coverage Diff                @@
##           release-21.0   #18194      +/-   ##
================================================
+ Coverage         67.50%   67.52%   +0.02%     
================================================
  Files              1572     1572              
  Lines            252233   252261      +28     
================================================
+ Hits             170263   170345      +82     
+ Misses            81970    81916      -54     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Signed-off-by: Harshit Gangal <harshit@planetscale.com>
@harshit-gangal harshit-gangal changed the title [release-21.] json array insert test [release-21.0] json array insert test Apr 24, 2025
@harshit-gangal harshit-gangal added Component: Query Serving Type: Testing and removed NeedsDescriptionUpdate The description is not clear or comprehensive enough, and needs work NeedsWebsiteDocsUpdate What it says NeedsIssue A linked issue is missing for this Pull Request NeedsBackportReason If backport labels have been applied to a PR, a justification is required labels Apr 24, 2025
@harshit-gangal harshit-gangal marked this pull request as ready for review April 24, 2025 10:18
Copy link
Copy Markdown
Member

@dbussink dbussink left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should also add this to main and release-22.0 then to ensure that we have this as a regression test.

@harshit-gangal harshit-gangal merged commit 7bb5811 into vitessio:release-21.0 May 21, 2025
105 of 115 checks passed
@harshit-gangal harshit-gangal deleted the b21-json-arry-insert branch May 21, 2025 19:28
@harshit-gangal harshit-gangal mentioned this pull request May 21, 2025
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants