-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
roachtest: acceptance/version-upgrade failed #104178
Comments
We are still seeing issues with the schemachange workload on this test: {
"workerId": 0,
"clientTimestamp": "05:32:17.070325",
"ops": [
"BEGIN",
{
"sql": "CREATE TABLE public.table8 (\"col8 _9\" INT8 NOT NULL, col8_10 TSQUERY, col8_11 STRING COLLATE de, col8_12 INT8 NOT NULL, \"'col8%8c_13\" JSONB NOT NULL, col8_14 TSQUERY NOT NULL, col8_15 TIME NOT NULL, 😖co̟l8̎_16 FLOAT4 NOT NULL, col8_17 TIMESTAMPTZ NULL, \"😓col8_!18\" STRING AS (lower(CAST(col8_11 AS STRING))) STORED, INDEX (\"'col8%8c_13\") STORING (col8_10, col8_11, col8_12, 😖co̟l8̎_16))",
"potentialExecErr": "0A000,42601"
}
],
"expectedExecErrors": "",
"expectedCommitErrors": "",
"message": "***UNEXPECTED ERROR; Received an unexpected execution error.: ERROR: index element 'col8%8c_13 of type jsonb is not indexable in a non-inverted index (SQLSTATE 42P16)",
"errorState": {
"potentialErrors": [
"0A000",
"42601"
], @fqazi Do you think this could be related to #103452? If so do you mind taking a look? |
Yeah, it's related, I wonder what was missed here. Let me pick this up |
Friendly ping, as this still flakes intermittently. |
@renatolabs Getting back to this today, sorry about that |
Another friendly ping. This flaked on a PR which had no related changes [1],
|
FWIW, the issue above is due to the use of The previous failures in this thread are related to |
@renatolabs Some of the version checking in the workload is off, let me get that fixed. I have a patch for it somewhere from before vacation |
Another jsonb-related failure in a recent bors build:
|
@renatolabs This is a code bug where we are not correctly generating user-facing errors in the declarative schema changer. Let me try and get to this later today |
105840: sql: version gate JSON columns on inverted indexes r=fqazi a=fqazi Previously, our version gate for forward JSON indexes did not correctly handle the case when they are used in inverted indexes. When these columns are not the last column in an inverted index they need to be forward indexable, requiring a similar version gate. This patch fixes version gate logic for this scenario. Fixes: #104178, Fixes #104707 Release note: None 106197: sql: delete TestGCJobWaitsForProtectedTimestamps r=chengxiong-ruan a=chengxiong-ruan Informs #85876 In the legacy gc path, we explictly check protected timestamps. The new gc path does not need this since the mvcc gc queue handles protected timestamps, and we can remove the resonposibility of testing the PTS logic since kv is handling it. Release note: None Co-authored-by: Faizan Qazi <[email protected]> Co-authored-by: Chengxiong Ruan <[email protected]>
roachtest.acceptance/version-upgrade failed with artifacts on master @ e2b704df25b012baf7d5fbe26e034f520a70f25c:
Parameters:
ROACHTEST_cloud=gce
,ROACHTEST_cpu=4
,ROACHTEST_encrypted=false
,ROACHTEST_ssd=0
Help
See: roachtest README
See: How To Investigate (internal)
Same failure on other branches
This test on roachdash | Improve this report!
Jira issue: CRDB-28390
The text was updated successfully, but these errors were encountered: