The stable sql interface project involves the restricting of access to the crdb_internal and system namespaces to external callers. This project is being done in two phases, the first where the ability to restrict access is available for testing, and then the second where these interfaces are actually restricted by default.
In order to accomplish the second part of this process, we need to allow all testing surfaces to succeed, which includes a number of things which attempt to read the unsafe internals. You can see examples of this breakage (and some of their possible fixes) in this PR. One of these is the example-orms build job. Example orms is a separate repository, which tests a variety of orms for different languages against CRDB. It's failing right now on a version check, which attempts to access the crdb_internal schema. To fix it, it may be possible to simply parse the version out from the show crdb_version command, as an example is given here. The goal of this ticket is to fix this issue going forward.
Epic CRDB-55276
Jira issue: CRDB-55061
The stable sql interface project involves the restricting of access to the crdb_internal and system namespaces to external callers. This project is being done in two phases, the first where the ability to restrict access is available for testing, and then the second where these interfaces are actually restricted by default.
In order to accomplish the second part of this process, we need to allow all testing surfaces to succeed, which includes a number of things which attempt to read the unsafe internals. You can see examples of this breakage (and some of their possible fixes) in this PR. One of these is the example-orms build job. Example orms is a separate repository, which tests a variety of orms for different languages against CRDB. It's failing right now on a version check, which attempts to access the crdb_internal schema. To fix it, it may be possible to simply parse the version out from the
show crdb_version command, as an example is given here. The goal of this ticket is to fix this issue going forward.Epic CRDB-55276
Jira issue: CRDB-55061