[MDEV-29030] inconsistent innodb full text max byte length/max char length Created: 2022-07-05  Updated: 2022-07-11

Status: Open
Project: MariaDB Server
Component/s: Full-text Search, Storage Engine - InnoDB
Affects Version/s: 10.3.35
Fix Version/s: 10.3

Type: Bug Priority: Trivial
Reporter: Daniel Black Assignee: Thirunarayanan Balathandayuthapani
Resolution: Unresolved Votes: 0
Labels: None


 Description   

git grep -C 1 HA_FT_MAXCHARLEN include/ft_global.h storage/innobase/include/fts0fts.h

 
include/ft_global.h-#define HA_FT_MAXBYTELEN 254
 
include/ft_global.h:#define HA_FT_MAXCHARLEN (HA_FT_MAXBYTELEN/3)
 
include/ft_global.h-
 
--
 
storage/innobase/include/fts0fts.h-/** Maximum possible Fulltext word length in bytes (assuming mbmaxlen=4) */
 
storage/innobase/include/fts0fts.h:#define FTS_MAX_WORD_LEN             (HA_FT_MAXCHARLEN * 4)
 
storage/innobase/include/fts0fts.h-
 
storage/innobase/include/fts0fts.h-/** Maximum possible Fulltext word length (in characters) */
 
storage/innobase/include/fts0fts.h:#define FTS_MAX_WORD_LEN_IN_CHAR     HA_FT_MAXCHARLEN
 
storage/innobase/include/fts0fts.h-

InnoDB's FTS_MAX_WORD_LEN is larger than HA_FT_MAXBYTELEN.

Probably isn't a problem because the lower limit is the enforcement.

 Comments   
Comment by Daniel Black [ 2022-07-11 ]

Also does this imply that utf8mb4 functioning in InnoDB FT?

Generated at Thu Feb 08 10:05:20 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.