JingsongLi opened a new issue, #1303:
URL: https://github.com/apache/paimon-rust/issues/1303
SQLContext currently rejects a number of common SQL dialect entry points
even when native DataFusion or Paimon primitives are available.
Examples:
```sql
SELECT count_if(p), max_by(v,k), collect_list(v)
FROM (VALUES (TRUE,'a',1),(FALSE,'b',2)) t(p,v,k);
SELECT listagg(v, ',') WITHIN GROUP (ORDER BY k)
FROM (VALUES ('a',1),('b',2)) t(v,k);
SELECT CAST(parse_json('{"a":1}') AS STRING), to_json(named_struct('a',1));
SELECT s LIKE 'a!_%' ESCAPE '!' FROM (VALUES ('a_x')) t(s);
ALTER TABLE default.events MODIFY COLUMN id BIGINT;
DESCRIBE TABLE EXTENDED default.events;
```
The compatibility work should cover:
- Basic, selection and collection aggregates: count_if, any, any_value,
first, approx_count_distinct, max_by, min_by, arg_max, collect_list and listagg.
- Typed JSON output, json_object and Variant string CAST/TRY_CAST.
- One-character LIKE/ILIKE escape literals.
- assert_true, conv, two/three-argument date_diff and explicit-zone
convert_tz.
- Scalar MODIFY COLUMN through existing SchemaChange validation and extended
table metadata descriptions.
Preserve existing session-function precedence, portable REST definitions,
logical NULL behavior, filtering/ordering and existing native/temporary-table
behavior. Schema changes must preserve field IDs and unmentioned attributes and
reject unsupported nested evolution before committing metadata.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
