Bug #75632 Remove innodb_optimize_point_storage away and disable the fixed length POINT
Submitted: 26 Jan 2015 11:18 Modified: 29 Jan 2015 18:54
Reporter: Bin Su Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:5.7.5 OS:Any
Assigned to: CPU Architecture:Any

[26 Jan 2015 11:18] Bin Su
Description:
As we decided and concluded in email thread 'Deciding on what to do with WL#6942', we want to remove the session variable innodb_optimize_point_storage away and disable the fixed length POINT in InnoDB in 5.7.

This fix should include:
1) We should remove the session variable away and not allow users to set it.
2) We should also disable the new data types introduced by WL#6942 in InnoDB, such as DATA_POINT, DATA_VAR_POINT.
3) We should disable the rejection of invalid POINT data when inserting and updating.

How to repeat:
Read the code.
[29 Jan 2015 18:54] Daniel Price
Posted by developer:
 
Fixed as of the upcoming 5.7.6 release, and here's the changelog entry:

The "innodb_optimize_point_storage" option and related internal data
types ("DATA_POINT" and "DATA_VAR_POINT") were removed. 

* Also noted in the 5.7 What's New under "Removed Features".
[30 Jan 2015 17:30] Daniel Price
Posted by developer:
 
Closing again. The bug was reset to Documenting state by a follow-up fix that removed a test case.