[MDEV-9826] KEY partitioning results in uneven data distribution - bad hash algorithm Created: 2016-03-29 Updated: 2019-09-17 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Partitioning |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Valerii Kravchuk | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Test case from https://bugs.launchpad.net/percona-server/+bug/1348295 gives the same result (uneven data disctribution) on recent MariaDB 10.1.13:
No wonder, as this is upstream bug known also as: https://bugs.mysql.com/bug.php?id=72428 Percona set the bug to "Won't fix" and Oracle seems to postpone fixing as the fix requires changing of hash algorithm and may result in backward compatibility issues. I wonder if mariaDB can implement new hashing algorithm for KEY partitioning (maybe under some new "name"/partition type) in 10.1 or 10.2, one that distributes data in a more even/expected way? |
| Comments |
| Comment by Sergei Golubchik [ 2017-05-29 ] |
|
It's not too difficult to add a new hashing algorithm and store it in the frm. This way we can change hashing later as we want or even let the user do it. |
| Comment by Sergei Golubchik [ 2018-09-07 ] |
|
Note, that we'll need some kind of SQL syntax for that, so that SHOW CREATE TABLE would show the hashing algorithm and that one would be able to dump/restore the table. |