feat(expr): add jsonb_object function

[wangrunji0408]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

As title.
Due to the bug in parsing array literals, some test cases are not enabled.

Checklist

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
• My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
• All checks passed in ./risedev check (or alias, ./risedev c)
• My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

• My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

• My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

Support the following functions:

jsonb_object ( text[] ) → jsonb
# Builds a JSON object out of a text array. The array must have exactly one dimension with an even number of members, in which case they are taken as alternating key/value pairs. All values are converted to JSON strings.
Example: jsonb_object('{a, 1, b, def, c, 3.5}') → {"a" : "1", "b" : "def", "c" : "3.5"}

jsonb_object ( text[][] ) → jsonb
# Builds a JSON object out of a text array. The array must have two dimensions such that each inner array has exactly two elements, which are taken as a key/value pair. All values are converted to JSON strings.
Example: jsonb_object('{{a, 1}, {b, def}, {c, 3.5}}') → {"a" : "1", "b" : "def", "c" : "3.5"}

jsonb_object ( keys text[], values text[] ) → jsonb
# This form of jsonb_object takes keys and values pairwise from separate text arrays. Otherwise it is identical to the one-argument form.
Example: jsonb_object('{a,b}', '{1,2}') → {"a": "1", "b": "2"}

Reference: https://www.postgresql.org/docs/16/functions-json.html#FUNCTIONS-JSON-CREATION-TABLE

[codecov]

Codecov Report

Merging #13036 (c6a98a4) into main (31d6dc0) will decrease coverage by 0.02%.
Report is 1 commits behind head on main.
The diff coverage is 1.31%.

@@            Coverage Diff             @@
##             main   #13036      +/-   ##
==========================================
- Coverage   68.26%   68.24%   -0.02%     
==========================================
  Files        1498     1499       +1     
  Lines      252574   252650      +76     
==========================================
+ Hits       172411   172421      +10     
- Misses      80163    80229      +66     

Flag	Coverage Δ
rust	68.24% <1.31%> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
src/frontend/src/binder/expr/function.rs	78.54% <100.00%> (+0.01%)	⬆️
src/frontend/src/expr/pure.rs	87.69% <ø> (ø)
src/expr/impl/src/scalar/jsonb_object.rs	0.00% <0.00%> (ø)

... and 9 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[xiangjinwu]

rest lgtm

[wangrunji0408]

@xiangjinwu By the way, do we plan to be consistent with postgres on array types? i.e. ignore multi-dimensions in the type declaration. In postgres, both one dimension and two dimension input share the same signature jsonb_object ( text[] ) → jsonb.

[xiangjinwu]

@xiangjinwu By the way, do we plan to be consistent with postgres on array types? i.e. ignore multi-dimensions in the type declaration. In postgres, both one dimension and two dimension input share the same signature jsonb_object ( text[] ) → jsonb.

#3811 (comment)

No. And in this case, separating {a,b,c,d,e,f} from {{a,b},{c,d},{e,f}} is clearer.

[neverchanje]

@wangrunji0408 This function lacks the sqllogictests.

[BugenZhao]

@wangrunji0408 This function lacks the sqllogictests.

#5246