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

Reduce redundancy & confusion around having two columnstore.cnf files

Details

    • Task
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • None
    • 5.5.1
    • N/A
    • None
    • 2020-8

    Description

      Serg correctly observed that after merging one of his PRs into develop, we are now deploying both a x-columnstore.cnf and a columnstore.cnf file in both community and enterprise, b/c we don't have a separate branch or repo for each.

      For community, the x-columnstore.cnf is unnecessary, and once we're gamma-level, the plugin-maturity option can be removed (b/c gamma is the default there).

      His suggestion to avoid having both is to package only columnstore.cnf, and have post-install generate x-columnstore.cnf IF it sees the enterprise-specific .cnf file in /etc/my.cnf.d

      Other option is to mod cmake to detect the INSTALL_LAYOUT var, and if enterprise, install x-columnstore.cnf. Else, don't.

      Multiple easy options. It should be done before the next release.

      Attachments

        Activity

          The enterprise build should have a x-columnstore.cnf (not sure about the hyphen). Community build should have columnstore.cnf. Neither should have both.

          Note that the name change is made during installation of packages.

          David.Hall David Hall (Inactive) added a comment - The enterprise build should have a x-columnstore.cnf (not sure about the hyphen). Community build should have columnstore.cnf. Neither should have both. Note that the name change is made during installation of packages.

          Fix needs to be redone to work with building columnstore as submodule of server

          ben.thompson Ben Thompson (Inactive) added a comment - Fix needs to be redone to work with building columnstore as submodule of server

          We need the Jenkins build from Server to test.

          David.Hall David Hall (Inactive) added a comment - We need the Jenkins build from Server to test.

          People

            ben.thompson Ben Thompson (Inactive)
            pleblanc Patrick LeBlanc (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 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.