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

JSON_VALID don't respect KILL QUERY / max_statement_time limit

    XMLWordPrintable

Details

    • Can result in unexpected behaviour
    • Hide
      JSON_VALID wasn't able to be stopped if a large document was passed to it; it also failed to respect the max_statement_time; in correcting the error handling of this function there is also an SQL note if the JSON is invalid indicating at what position it is invalid and why
      Show
      JSON_VALID wasn't able to be stopped if a large document was passed to it; it also failed to respect the max_statement_time; in correcting the error handling of this function there is also an SQL note if the JSON is invalid indicating at what position it is invalid and why

    Description

      JSON_VALID cannot be killed or max_statement_time to have an effect.

      MDEV-28404 did resolve its max recursion depth, though JSON_VALID doesn't report error messages.

      As fixing this will involve creating a json_engine in the Item, it will change the json_valid C function schematics which impacts MDEV-40174 and MDEV-40165. Minor change in sql_acl around DBUG_ASSERT(json_valid()) calling.

      Attachments

        Issue Links

          Activity

            People

              danblack Daniel Black
              danblack Daniel Black
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 0d
                  0d
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 0.25d
                  0.25d

                  Git Integration

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