Mryange

Results 41 issues of Mryange

## Proposed changes BE has not implemented the code for "return type not nullable." ``` CREATE TABLE test_json ( id INT not null, j JSON not null ) DUPLICATE KEY(id)...

approved
reviewed
dev/2.0.x

## Proposed changes The debug string may be too long, so we'll truncate it here. ## Further comments If this is a relatively large or complex change, kick off the...

dev/2.0.x

## Proposed changes before ``` mysql []>select 3.14 and 3.0; +--------------------------------------------------+ | (cast(3.14 as BOOLEAN) AND cast(3.0 as BOOLEAN)) | +--------------------------------------------------+ | 3 | +--------------------------------------------------+ mysql [test]>select cast(3.000 as boolean)...

dev/2.0.x

## Proposed changes For even PRs, the batch size is set to 50, and this case runs for 50 minutes. ## Further comments If this is a relatively large or...

approved
reviewed
dev/2.0.x

## Proposed changes ``` mysql [test]>select cast(j as int) from test_json_not_null; ERROR 1105 (HY000): errCode = 2, detailMessage = (127.0.0.1)[CANCELLED][INTERNAL_ERROR]block column type check failed , reason : check failed in...

## Proposed changes Issue Number: close #xxx ## Further comments If this is a relatively large or complex change, kick off the discussion at [[email protected]](mailto:[email protected]) by explaining why you chose...

## Proposed changes Issue Number: close #xxx ## Further comments If this is a relatively large or complex change, kick off the discussion at [[email protected]](mailto:[email protected]) by explaining why you chose...

## Proposed changes https://github.com/apache/doris-website/pull/682 ``` mysql [test]>select * from quantile_weighted_table order by k; +------+------+ | k | w | +------+------+ | 1 | 2 | | 3 | 1 |...

approved
reviewed

## Proposed changes Issue Number: close #xxx ## Further comments If this is a relatively large or complex change, kick off the discussion at [[email protected]](mailto:[email protected]) by explaining why you chose...

approved
reviewed

## Proposed changes Issue Number: close #xxx ## Further comments If this is a relatively large or complex change, kick off the discussion at [[email protected]](mailto:[email protected]) by explaining why you chose...