Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-2180

UDAF docs are currently broken

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 1.2.2
    • 1.2.3
    • None
    • None
    • 2019-03

    Description

      UDAF docs have the following issues:

      1. conf.py is still marked as version 1.1
      2. The changlog table is missing a row separator between the two lines
      3. The docs reference lines in median.cpp that do not exist:

      /home/linuxjedi/Programming/Git/mariadb-columnstore-engine-fixes/utils/udfsdk/docs/source/usage/memoryallocation.rst.rst:79: WARNING: line number spec is out of range(1-225): '290-305'
      /home/linuxjedi/Programming/Git/mariadb-columnstore-engine-fixes/utils/udfsdk/docs/source/usage/memoryallocation.rst:79: WARNING: Line spec '290-305': no lines pulled from include file u'/home/linuxjedi/Programming/Git/mariadb-columnstore-engine-fixes/utils/udfsdk/median.cpp'
      /home/linuxjedi/Programming/Git/mariadb-columnstore-engine-fixes/utils/udfsdk/docs/source/usage/memoryallocation.rst.rst:95: WARNING: line number spec is out of range(1-225): '283-288'
      /home/linuxjedi/Programming/Git/mariadb-columnstore-engine-fixes/utils/udfsdk/docs/source/usage/memoryallocation.rst:95: WARNING: Line spec '283-288': no lines pulled from include file u'/home/linuxjedi/Programming/Git/mariadb-columnstore-engine-fixes/utils/udfsdk/median.cpp'
      

      Also the doc published on KB is out of date.

      Attachments

        Activity

          People

            LinuxJedi Andrew Hutchings (Inactive)
            LinuxJedi Andrew Hutchings (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 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.