[MDEV-30087] Prefix UNIQUE HASH raises unexpected Specified key part was too long Created: 2022-11-24  Updated: 2022-11-27

Status: Open
Project: MariaDB Server
Component/s: Data types
Affects Version/s: 10.4, 10.5, 10.6, 10.7, 10.8, 10.9, 10.11, 11.0
Fix Version/s: 10.4

Type: Bug Priority: Major
Reporter: Alexander Barkov Assignee: Nikita Malyavin
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-371 Unique indexes for blobs Closed

 Description   

Unique hash keys work fine on the entire LONGTEXT column:

CREATE OR REPLACE TABLE t3 (a LONGTEXT CHARACTER SET utf8, UNIQUE KEY(a) USING HASH);

However, if I create an Unique hash key using a long prefix, it fails with an error:

CREATE OR REPLACE TABLE t3 (a LONGTEXT CHARACTER SET utf8, UNIQUE KEY(a(35000)) USING HASH);


ERROR 4159 (42000): Specified key part was too long; max key part length is 65535 bytes

The above error looks wrong.
Generated at Thu Feb 08 10:13:33 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.