Call For Participation: Improve the JSON functionality #14486
Labels
component/json
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
type/enhancement
The issue or PR belongs to an enhancement.
All issues are open and welcomed to contributors. You can join #sig-exec on tidb community slack to discuss and get help from someone.
Feature Request
Is your feature request related to a problem? Please describe:
Here we collect some issues about JSON functions, please help us to fix them if you are interested in any of them:
JSON_MERGE_PATCH
; difficulty: mediumJSON_PRETTY
; difficulty: mediumJSON_ARRAYAGG
; difficulty: medium executor: add builtin aggregate functionjson_arrayagg
#19957JSON_OBJECTAGG
; difficulty: medium; @hg2990656 *: add builtin aggregate functionjson_objectagg
#11154JSON_STORAGE_SIZE
; difficulty: mediumJSON_EXTRACT
gets wrong decimal when insert into table; difficulty: easyJSON_OBJECT
handle long strings wrongly; difficulty: easyJSON_EXTRACT(...) IN (...)
; difficulty: easyThanks for your help! If you have any question, please discuss it with us in our slack channel #sig-exec on tidb community slack or in this issue by comments :D
Document Collection
Talent Challenge Program information
Milestones and action items
Milestone 1: Merge missing functions from 5.7.
Milestone 2: Fix bugs in current implementation
Milestone 3: Implement functionality from MySQL 8.0
* The MySQL 8.0 functionality may need to be broken down into design docs, since TiDB does not currently support TABLE functions or multi-valued indexes. There may be some assumptions that we've made that will need to be fixed for these to be added.
The text was updated successfully, but these errors were encountered: