-
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: internal error with BUCKET_COUNT = NULL #130353
Comments
Hi @SteveLeungYL, please add branch-* labels to identify which branch(es) this C-bug affects. 🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf. |
Hello, I am Blathers. I am here to help you get the issue triaged. Hoot - a bug! Though bugs are the bane of my existence, rest assured the wretched thing will get the best of care here. I have CC'd a few people who may be able to assist you:
If we have not gotten back to your issue within a few business days, you can try the following:
🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf. |
This bug was introduced in v20.2. Prior to that, it errored gracefully. In v20.1.19:
|
Previously, the `EvalShardBucketCount` function did not properly handle the case where `BUCKET_COUNT` was set to `NULL`, causing evaluation errors. This change adds explicit handling for `NULL` values, ensuring that `BUCKET_COUNT` cannot be set to `NULL` and returns an appropriate error message. Also added a check for NULL before sanitizing and evaluating shardBuckets to avoid invalid operations on NULL values. returns the error `BUCKET_COUNT cannot be NULL`. Epic: none Fixes: cockroachdb#130353 Release note: None
Previously, the `EvalShardBucketCount` function did not properly handle the case where `BUCKET_COUNT` was set to `NULL`, causing evaluation errors. This change adds explicit handling for `NULL` values, ensuring that `BUCKET_COUNT` cannot be set to `NULL` and returns an appropriate error message. Also added a check for NULL before sanitizing and evaluating shardBuckets to avoid invalid operations on NULL values. returns the error `BUCKET_COUNT cannot be NULL`. Epic: none Fixes: cockroachdb#130353 Release note: None
131212: sql: internal error with BUCKET_COUNT = NULL r=spilchen a=vidit-bhat Previously, the `EvalShardBucketCount` function did not properly handle the case where `BUCKET_COUNT` was set to `NULL`, causing evaluation errors. This change adds explicit handling for `NULL` values, ensuring that `BUCKET_COUNT` cannot be set to `NULL` and returns an appropriate error message. Epic: none Fixes: #130353 Release note: None Co-authored-by: Vidit Bhat <[email protected]>
Previously, the `EvalShardBucketCount` function did not properly handle the case where `BUCKET_COUNT` was set to `NULL`, causing evaluation errors. This change adds explicit handling for `NULL` values, ensuring that `BUCKET_COUNT` cannot be set to `NULL` and returns an appropriate error message. Also added a check for NULL before sanitizing and evaluating shardBuckets to avoid invalid operations on NULL values. returns the error `BUCKET_COUNT cannot be NULL`. Epic: none Fixes: #130353 Release note: None
Previously, the `EvalShardBucketCount` function did not properly handle the case where `BUCKET_COUNT` was set to `NULL`, causing evaluation errors. This change adds explicit handling for `NULL` values, ensuring that `BUCKET_COUNT` cannot be set to `NULL` and returns an appropriate error message. Also added a check for NULL before sanitizing and evaluating shardBuckets to avoid invalid operations on NULL values. returns the error `BUCKET_COUNT cannot be NULL`. Epic: none Fixes: #130353 Release note: None
Previously, the `EvalShardBucketCount` function did not properly handle the case where `BUCKET_COUNT` was set to `NULL`, causing evaluation errors. This change adds explicit handling for `NULL` values, ensuring that `BUCKET_COUNT` cannot be set to `NULL` and returns an appropriate error message. Also added a check for NULL before sanitizing and evaluating shardBuckets to avoid invalid operations on NULL values. returns the error `BUCKET_COUNT cannot be NULL`. Epic: none Fixes: #130353 Release note: None
Previously, the `EvalShardBucketCount` function did not properly handle the case where `BUCKET_COUNT` was set to `NULL`, causing evaluation errors. This change adds explicit handling for `NULL` values, ensuring that `BUCKET_COUNT` cannot be set to `NULL` and returns an appropriate error message. Also added a check for NULL before sanitizing and evaluating shardBuckets to avoid invalid operations on NULL values. returns the error `BUCKET_COUNT cannot be NULL`. Epic: none Fixes: #130353 Release note: None
Describe the problem
The latest version of the CockroachDB (60313dc or v24.2.1) crashes when executing the following query:
To Reproduce
Expected behavior
The Create Table statement execution should return error:
Additional data / screenshots
Here is the crash stack trace from CockroachDB v24.2.1:
Environment:
Jira issue: CRDB-42013
Epic CRDB-40419
The text was updated successfully, but these errors were encountered: