Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-32854

Make JSON_DEPTH_LIMIT configurable

Details

    Description

      The current JSON_DEPTH_LIMIT is 32 as defined in include/json_lib.h
      Source code:
      https://github.com/MariaDB/server/blob/22ffe4dd227451ebd0ef842850ef57b81aa8f930/include/json_lib.h#L10

      This limit is not documented.

      Customer requests to make this limit configurable with a global variable.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MCOL-5885 Adopt the recent MDB's JSON parser lib dynamic array root mem changes

          • Major - Major loss of function.
          • Open

          Task - A task that needs to be done. MDEV-26877 Deeply nested vaid JSON values seem invalid ( JSON_DEPTH_LIMIT )

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MDEV-30343 Optimizer trace produces JSON too deep for MariaDB JSON functions

          • Major - Major loss of function.
          • Confirmed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-33437 JSON_SEARCH fails to find match

          • Major - Major loss of function.
          • Closed

          Activity

            Descending order - Click to sort in ascending order
            ramesh Ramesh Sivaraman added a comment - - edited

            ok to push

            ramesh Ramesh Sivaraman added a comment - - edited ok to push
            akim.demaille Akim Demaille added a comment -

            Hi,
            So what did the efficiency testing give?
            The first implementations were submitted one year ago I have no doubt you guys have lots of things to do, but this is serious limitation.
            Cheers!

            akim.demaille Akim Demaille added a comment - Hi, So what did the efficiency testing give? The first implementations were submitted one year ago I have no doubt you guys have lots of things to do, but this is serious limitation. Cheers!
            sanja Oleksandr Byelkin added a comment -

            It is for efficiency testing

            sanja Oleksandr Byelkin added a comment - It is for efficiency testing
            serg Sergei Golubchik added a comment -

            No was not merged yet. It is in progress, it's planned for 11.9, and it will be there, providing it passes code review and testing. If it, of course, impossible to predict whether it will.

            serg Sergei Golubchik added a comment - No was not merged yet. It is in progress, it's planned for 11.9, and it will be there, providing it passes code review and testing. If it, of course, impossible to predict whether it will.
            akim.demaille Akim Demaille added a comment -

            Hi!

            I'm not sure I know how to read the previous event. Does it mean the branch was merged? In which case, do I understand correctly that it will be shipped with 11.9?

            Many thanks for work on this. It's a major thorn in my shoes.

            akim.demaille Akim Demaille added a comment - Hi! I'm not sure I know how to read the previous event. Does it mean the branch was merged? In which case, do I understand correctly that it will be shipped with 11.9? Many thanks for work on this. It's a major thorn in my shoes.
            View 21 older comments

            People

              rucha174 Rucha Deodhar
              edward Edward Stoever
              Votes:
              6 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.