-
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
sql: v20.2.3: expected expression to have key #58104
Comments
The rule is SplitDisjunctionAddKey. It is calling |
Ah, my bad, |
Indeed, I was able to repro with:
The strange filter is necessary to trick the rule into firing (there is a single index on |
Interestingly, this doesn't seem to be a problem on |
Actually, looks like this was already fixed (on master and release-20.2) by #58434 - we no longer call |
61359: tracing: use byte-limits for logs/structured events per span r=irfansharif a=irfansharif Touches #59188. Follow-on work from #60678. We can introduce byte-limits for verbose logging and structured events, instead of limiting things based on count. This PR also: - adds a _dropped tag to recordings with dropped logs/structured events. - squashes a bug where reset spans (as used in SessionTracing) still held onto earlier structured events - moves away from the internal usage of the opentracing.LogRecord type, it's unnecessary Release justification: low risk, high benefit changes to existing functionality Release note: None --- +cc @knz / @erikgrinaker / @angelapwen for pod-visibility. 61482: jobs: add job metrics per-type to track success, failure, and cancel r=fqazi a=fqazi Fixes: #59711 Previously, there were only over all counters tracking how many jobs were completed, cancelled, or failed. This was inadequate because it didn't make it easy to tell in aggregate what job types they were. To address this, this patch will add counters for different job types for tracking success, failure, and cancellation. Release justification: Low risk change only adding a metric inside the crdb_internal.feature_usage table Release note: None 61491: sqlsmith: add support for computed columns r=RaduBerinde a=RaduBerinde This changes the random table generator to also create computed columns (either STORED or VIRTUAL). Some example of definitions: - `col1_14 STRING NOT NULL AS (lower(CAST(col1_8 AS STRING))) VIRTUAL` - `col2_6 DECIMAL NOT NULL AS (col2_2 + 1:::DECIMAL) STORED` - `col1_13 INT4 AS (col1_0 + col1_10) STORED` Release justification: non-production code change. Release note: None Informs #57608. 61509: sql: add a regression test r=RaduBerinde a=RaduBerinde This commit adds a regression test for #58104 (the problem was already fixed). Resolves #58104. Release justification: non-production code change. Release note: None 61522: opt: fix fetch scope in UPDATE..FROM statements r=mgartner a=mgartner Previously, the fetch scope incorrectly included columns in the FROM clause of an UPDATE..FROM statement. As a result, column names shared by the FROM clause and the mutating table lead to ambiguity when resolving partial index DEL column expressions. This commit ensures that the fetch scope does not include columns in the FROM clause. Fixes #61284 Release justification: This is a low-risk bug fix to existing functionality. Release note (bug fix): An UPDATE..FROM statement where the FROM clause contained column names that match table column names erred if the table had a partial index predicate referencing those columns. This bug, present since partial indexes were released in version 20.2.0, has been fixed. 61553: ccl,server: error.Wrap on previously handled errors r=[dt,miretskiy] a=stevendanna These errors.Wrap calls are wrapping errors that are nil and thus will always return a nil error. Release justification: Minor error handling fixes Release note: None Co-authored-by: irfan sharif <[email protected]> Co-authored-by: Faizan Qazi <[email protected]> Co-authored-by: Radu Berinde <[email protected]> Co-authored-by: Marcus Gartner <[email protected]> Co-authored-by: Steven Danna <[email protected]>
This issue was autofiled by Sentry. It represents a crash or reported error on a live cluster with telemetry enabled.
Sentry link: https://sentry.io/organizations/cockroach-labs/issues/2103833235/?referrer=webhooks_plugin
Panic message:
Stacktrace (expand for inline code snippets):
cockroach/pkg/sql/opt/norm/decorrelate_funcs.go
Lines 424 to 426 in 89dd2d1
https://github.com/cockroachdb/cockroach/blob/89dd2d14c29787378c434ed54937757ef5d9877c/pkg/sql/opt/xform/explorer.og.go#L383-L385 in pkg/sql/opt/xform.(*explorer).exploreSelect
https://github.com/cockroachdb/cockroach/blob/89dd2d14c29787378c434ed54937757ef5d9877c/pkg/sql/opt/xform/explorer.og.go#L19-L21 in pkg/sql/opt/xform.(*explorer).exploreGroupMember
cockroach/pkg/sql/opt/xform/explorer.go
Lines 177 to 179 in 89dd2d1
cockroach/pkg/sql/opt/xform/optimizer.go
Lines 462 to 464 in 89dd2d1
cockroach/pkg/sql/opt/xform/optimizer.go
Lines 249 to 251 in 89dd2d1
cockroach/pkg/sql/opt/xform/optimizer.go
Lines 504 to 506 in 89dd2d1
cockroach/pkg/sql/opt/xform/optimizer.go
Lines 449 to 451 in 89dd2d1
cockroach/pkg/sql/opt/xform/optimizer.go
Lines 223 to 225 in 89dd2d1
cockroach/pkg/sql/plan_opt.go
Lines 408 to 410 in 89dd2d1
cockroach/pkg/sql/plan_opt.go
Lines 125 to 127 in 89dd2d1
cockroach/pkg/sql/conn_executor_prepare.go
Lines 251 to 253 in 89dd2d1
cockroach/pkg/sql/conn_executor_prepare.go
Lines 193 to 195 in 89dd2d1
cockroach/pkg/kv/db.go
Lines 706 to 708 in 89dd2d1
cockroach/pkg/kv/txn.go
Lines 810 to 812 in 89dd2d1
cockroach/pkg/kv/db.go
Lines 705 to 707 in 89dd2d1
cockroach/pkg/sql/conn_executor_prepare.go
Lines 205 to 207 in 89dd2d1
cockroach/pkg/sql/conn_executor_prepare.go
Lines 119 to 121 in 89dd2d1
cockroach/pkg/sql/conn_executor_prepare.go
Lines 65 to 67 in 89dd2d1
cockroach/pkg/sql/conn_executor.go
Lines 1550 to 1552 in 89dd2d1
cockroach/pkg/sql/conn_executor.go
Lines 1390 to 1392 in 89dd2d1
cockroach/pkg/sql/conn_executor.go
Lines 507 to 509 in 89dd2d1
cockroach/pkg/sql/pgwire/conn.go
Lines 625 to 627 in 89dd2d1
/usr/local/go/src/runtime/asm_amd64.s#L1356-L1358 in runtime.goexit
v20.2.3
The text was updated successfully, but these errors were encountered: