Details

    Description

      I want to use Hash Indexes also on the Storage Engine InnoDb.

      I have a lot of Hash-Values in my table's which I create via hex(md5(<value>)) function and store them in a BINARY(16) column.

      In my JOIN's I using them via USING(column), I not order them. So I would expect dramatic performance improvements if the underlying Index is not a B-Tree but also Hashing (ideal the value itself is used also in the index).

      I doing this for a Data-Vault 2.0 Core Model which heavy use MD5 represantation of Business-Key for references the SAT's and the HUB's and the LNK's.

      Attachments

        Issue Links

          Activity

            I wonder if MDEV-371 already implemented this.

            marko Marko Mäkelä added a comment - I wonder if MDEV-371 already implemented this.

            Yes, one can say that MDEV-371 is basically a hash index, so this can be closed.
            But optimizer doesn't use MDEV-371 indexes, iirc, so it needs a new task to implement this optimization.

            serg Sergei Golubchik added a comment - Yes, one can say that MDEV-371 is basically a hash index, so this can be closed. But optimizer doesn't use MDEV-371 indexes, iirc, so it needs a new task to implement this optimization.
            rjasdfiii Rick James added a comment -

            Maybe relates to MDEV-27653 long uniques don't work with unicode collations?

            rjasdfiii Rick James added a comment - Maybe relates to MDEV-27653 long uniques don't work with unicode collations?

            People

              Unassigned Unassigned
              Stefc Stefan Böther
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

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