Skip to content
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

test: make it easier to run tests without a main keyspace #17501

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

systay
Copy link
Collaborator

@systay systay commented Jan 9, 2025

Description

When using keyspaces in tests, the current schema wrapper we use makes it hard if we are missing a main keyspace. This change makes it easier to handle situations without this keyspace.

Checklist

  • "Backport to:" labels have been added if this change should be back-ported to release branches
  • If this change is to be back-ported to previous releases, a justification is included in the PR description
  • 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

@systay systay requested a review from deepthi as a code owner January 9, 2025 19:26
Copy link
Contributor

vitess-bot bot commented Jan 9, 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 Jan 9, 2025
@systay systay 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 Jan 9, 2025
@github-actions github-actions bot added this to the v22.0.0 milestone Jan 9, 2025
@frouioui frouioui requested review from harshit-gangal and GuptaManan100 and removed request for deepthi January 9, 2025 20:32
Signed-off-by: Andres Taylor <[email protected]>
Copy link

codecov bot commented Jan 10, 2025

Codecov Report

Attention: Patch coverage is 42.10526% with 11 lines in your changes missing coverage. Please review.

Project coverage is 67.69%. Comparing base (aabf1c9) to head (66ba4bc).
Report is 3 commits behind head on main.

Files with missing lines Patch % Lines
go/test/vschemawrapper/vschema_wrapper.go 42.10% 11 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##             main   #17501   +/-   ##
=======================================
  Coverage   67.68%   67.69%           
=======================================
  Files        1584     1584           
  Lines      254466   254511   +45     
=======================================
+ Hits       172235   172289   +54     
+ Misses      82231    82222    -9     

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

Comment on lines -304 to 296
return vw.V.Keyspaces["main"].Keyspace, nil
return vw.AnyKeyspace()
}
Copy link
Member

Choose a reason for hiding this comment

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

use vw. Vcursor

Comment on lines -308 to +300
return vw.SelectedKeyspace()
ks, found := vw.V.Keyspaces["main"]
if found {
Copy link
Member

Choose a reason for hiding this comment

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

same here
use vw. Vcursor

Comment on lines -312 to 321
return vw.V.Keyspaces["main"].Keyspace, nil
return vw.AnyKeyspace()
}
Copy link
Member

Choose a reason for hiding this comment

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

same
use vw. Vcursor

Comment on lines 356 to +360
destKeyspace, destTabletType, _, err := topoproto.ParseDestination(tab.Qualifier.String(), topodatapb.TabletType_PRIMARY)
if err != nil {
return nil, err
}
mirrorRule, err := vs.V.FindMirrorRule(destKeyspace, tab.Name.String(), destTabletType)
mirrorRule, err := vw.V.FindMirrorRule(destKeyspace, tab.Name.String(), destTabletType)
Copy link
Member

Choose a reason for hiding this comment

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

possibly duplicate logic,
we now have vw. Vcursor, that could be used here.

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