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

logictest: enhance crdb_internal_tenant logic test #55860

Merged
merged 1 commit into from
Oct 26, 2020
Merged

logictest: enhance crdb_internal_tenant logic test #55860

merged 1 commit into from
Oct 26, 2020

Conversation

asubiotto
Copy link
Contributor

This commit copies the full crdb_internal test to crdb_internal_tenant, and
rewrites it to succeed with this configuration in order to increase
crdb_internal tenant test coverage.

Release note: None (testing change)

This commit copies the full crdb_internal test to crdb_internal_tenant, and
rewrites it to succeed with this configuration in order to increase
crdb_internal tenant test coverage.

Release note: None (testing change)
@asubiotto asubiotto requested review from tbg and andy-kimball October 22, 2020 15:08
@cockroach-teamcity
Copy link
Member

This change is Reviewable

query B
select crdb_internal.cluster_id() != '00000000-0000-0000-0000-000000000000' FROM foo
----
false
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@tbg is this expected?

Copy link
Member

Choose a reason for hiding this comment

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

Yes, it is. The ClusterID is primarily a KV concept. Tenants could learn it only from Gossip, but they don't since that has not been necessary.

@asubiotto
Copy link
Contributor Author

TFTR

bors r=tbg

@craig
Copy link
Contributor

craig bot commented Oct 26, 2020

Build succeeded:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants