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

SphinxSE missing in 10.0.6 debian repo

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Not a Bug
    • 10.0.6
    • 10.0.7
    • None
    • None
    • Debian 6

    Description

      I recently ran apt-get upgrade and this updated my MariaDB 10.0.4 to 10.0.6. After the update the SphinxSE engine is gone and my Sphinx tables no longer function. I did not see a mention of Sphinx or SphinxSE in change log so I'm assuming this is a bug. Please put SphinxSE back in by default for 10.0.7. Is there a way to get it working with 10.0.6?

      Attachments

        Activity

          The engine is provided as a plugin, the library name is 'ha_sphinx.so'. To enable it, you can run

          install soname 'ha_sphinx'

          it will install the engine back and make it persistent for further server restarts.

          elenst Elena Stepanova added a comment - The engine is provided as a plugin, the library name is 'ha_sphinx.so'. To enable it, you can run install soname 'ha_sphinx' it will install the engine back and make it persistent for further server restarts.

          I presume the previous comment clarifies it, so I am closing the report for now. If you have further questions, please feel free to comment and we will re-open the report if necessary.

          elenst Elena Stepanova added a comment - I presume the previous comment clarifies it, so I am closing the report for now. If you have further questions, please feel free to comment and we will re-open the report if necessary.

          People

            elenst Elena Stepanova
            rmedeksza Robert Medeksza
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.