[MDEV-19095] [feature] Issue: #45 Support for INVISIBLE indexes Created: 2019-03-31  Updated: 2023-09-10

Status: Open
Project: MariaDB Server
Component/s: None
Fix Version/s: None

Type: Task Priority: Major
Reporter: Anel Husakovic Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
PartOf
is part of MDEV-28906 MySQL 8.0 desired compatibility Open
Problem/Incident
causes MDEV-19102 [bugfix] Issue: #56 invisible index i... Closed
Epic Link: AliSQL patches

 Description   

This feature is ported from upstream 8.0.
 
As 8.0 introduces Data Dictionary which substitute metadata files
in server layer used in previous version(such as frm) , so there are
some subtle differences.
1. we store index visibility info in frm
2. we use the HA_SORT_ALLOWS_SAME flag, which was not stored in frm
   before, in frm to indicate HA_INVISIBLE_KEY, so that we don't need
   to expand frm format, and compatibility is held.

https://github.com/alibaba/AliSQL/commit/238c63990e85fa6c11cce1b5af8350ea5664fef8

 Description
  ============
  bug#88847, this issue is related to invisible indexes feature which we ported
  from 8.0 upstream. Invisible index is not considered by slave SQL row applier
  when searching index to use, and choosed anyway as long as the index is fit for
  update.
 
  Solution:
  ============
  Make slave SQL applier thread respecting invisible indexes and don't choose them
  when searching index to use.

https://github.com/alibaba/AliSQL/commit/229996d67b4caaf27a330491b9e668dc7e0c0120



 Comments   
Comment by Sergei Golubchik [ 2019-04-01 ]

we cannot call indexes "INVISIBLE", this keyword is already taken and has a well-defined semantics.

Generated at Thu Feb 08 08:49:01 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.