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

Add Feature_json status variable

Details

    • Task
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • 10.3.7
    • JSON
    • None

    Description

      Add Feature_json status variable that's incremented when a json functionality is used.

      For example, in item_create.cc when a json function item is created.

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          serg Sergei Golubchik created issue -
          elenst Elena Stepanova added a comment -

          Feature_json sounds a bit ambiguous. We have EXPLAIN/ANALYZE FORMAT=JSON, JSON as a table type in Connect engine, maybe more that I don't remember now.

          elenst Elena Stepanova added a comment - Feature_json sounds a bit ambiguous. We have EXPLAIN/ANALYZE FORMAT=JSON, JSON as a table type in Connect engine, maybe more that I don't remember now.
          holyfoot Alexey Botchkov made changes -
          Field Original Value New Value
          Status Open [ 1 ] In Progress [ 3 ]
          holyfoot Alexey Botchkov added a comment -

          http://lists.askmonty.org/pipermail/commits/2018-April/012439.html

          holyfoot Alexey Botchkov added a comment - http://lists.askmonty.org/pipermail/commits/2018-April/012439.html
          holyfoot Alexey Botchkov made changes -
          Assignee Alexey Botchkov [ holyfoot ] Sergei Golubchik [ serg ]
          Status In Progress [ 3 ] In Review [ 10002 ]
          serg Sergei Golubchik added a comment -

          ok to push, thanks!

          serg Sergei Golubchik added a comment - ok to push, thanks!
          serg Sergei Golubchik made changes -
          Assignee Sergei Golubchik [ serg ] Alexey Botchkov [ holyfoot ]
          Status In Review [ 10002 ] Stalled [ 10000 ]
          holyfoot Alexey Botchkov added a comment -

          I can note also GEOJSON functions as a source of some ambiquity.
          Though after all I decided to stick with Feature_json as a name. The self-explanatory name is too long and inconvenient. And i doubt many people would think about EXPLAIN JSON in connection with this variable. So it's better just to comment it properly.

          holyfoot Alexey Botchkov added a comment - I can note also GEOJSON functions as a source of some ambiquity. Though after all I decided to stick with Feature_json as a name. The self-explanatory name is too long and inconvenient. And i doubt many people would think about EXPLAIN JSON in connection with this variable. So it's better just to comment it properly.
          holyfoot Alexey Botchkov made changes -
          issue.field.resolutiondate 2018-04-26 19:47:55.0 2018-04-26 19:47:55.362
          holyfoot Alexey Botchkov made changes -
          Fix Version/s 10.3.7 [ 23005 ]
          Fix Version/s 10.3 [ 22126 ]
          Resolution Fixed [ 1 ]
          Status Stalled [ 10000 ] Closed [ 6 ]
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 86627 ] MariaDB v4 [ 133526 ]

          People

            holyfoot Alexey Botchkov
            serg Sergei Golubchik
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

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