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

Crash on UTF-8 Full text search

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Blocker
    • Resolution: Fixed
    • 10.4.10
    • 10.4.11
    • Optimizer
    • Centos os 7

    Description

      You can reproduce the problem by creating an table that have a Full-text index and then search with charset other than latin1.
      For reproducing the bug you should use several other indexes along the full-text search.

      For example:

      SELECT t.* FROM threads t WHERE [some other search based on indexes] MATCH (t.subject) AGAINST ('Some Arabic/Persian Text') >= '3' ORDER BY t.tid DESC LIMIT 0, 10;

      Attachments

        1. mysql.err
          2.67 MB
          Mohammad Tanhaei

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-21040 InnoDB: fulltext search with ` in(...)` crashed on specific combination

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-20407 mysqld got signal 11; rowid filter

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-21125 Crash with FTS query

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Activity

            People

              igor Igor Babaev
              uisoftware Mohammad Tanhaei
              Votes:
              0 Vote for this issue
              Watchers:
              5 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.