[MDEV-3936] Storage-engine private data area per physical table Created: 2012-12-14  Updated: 2023-10-12

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

Type: Task Priority: Minor
Reporter: Sergei Golubchik Assignee: Sergei Golubchik
Resolution: Unresolved Votes: 1
Labels: plugins

Attachments: File MDEV-3936.patch    
Issue Links:
Relates
relates to MDEV-5271 Support engine-defined attributes per... Closed
relates to MDEV-4783 New .frm file format Open

 Description   

We need a data area per physical table where storage engine can store anything it wants.
Additionally, this should store engine_options, tablefile path, etc. It cannot be directly in the TABLE_SHARE, because partitions have different paths and engine_options.

We cannot directly backport MySQL WL#4305 (see the link below), because it was reverted by Oracle and, anyway, it doesn't solve the problem of different paths and engine_options.

 Comments   
Comment by Sergei Golubchik [ 2013-03-15 ]

Attached the work-in-progress patch for 10.0-base tree.

Left to do:

  • don't pass table name into handler::open()
  • use handler_share in almost all engines
  • move connect_string and other engine options into engine_options.
  • support per-partition engine_options
Comment by Ralf Gebhardt [ 2023-10-12 ]

I have removed the fixVersion for this task as it is one of 5.5, 10.1, 10.2, 10.3, which are EOLed.

Please add a new fixVersion if you plan to work on this task for a not EOLed versions.

Generated at Thu Feb 08 06:52:24 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.