Bug #80716 | JSON data not validated if inserted via InnoDB memcache plugin | ||
---|---|---|---|
Submitted: | 13 Mar 2016 9:53 | Modified: | 31 Mar 2016 5:23 |
Reporter: | Daniël van Eeden (OCA) | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Memcached | Severity: | S3 (Non-critical) |
Version: | 5.7.10, 5.7.11 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | innodb, json, Memcache |
[13 Mar 2016 9:53]
Daniël van Eeden
[14 Mar 2016 13:46]
MySQL Verification Team
Hello Daniël, Thank you for the report. Observed this with 5.7.11 build. Thanks, Umesh
[31 Mar 2016 5:23]
Erlend Dahl
Posted by developer: [30 Mar 2016 21:32] Jimmy Yang This is expected, since InnoDB memcached bypasses the optimizer and query execution. The JSON data validation is done by the server, and InnoDB memcached goes around it, and directly interacts with InnoDB. So the user should add one additional layer themselves to validate the data before pump into memcached interfaces.
[21 Sep 2017 20:40]
Mike Talbot
The point is that the data returned and set via the innodb memcached plugin is in the INTERNAL format. Which I don't believe is documented so it becomes very hard to do any validation on it. This is a real shame because for rapid memcached lookups I've had to go back to storing JSON in something that I can parse and re-serialize. If there was a definition of the format or functions for creating and unpacking it then it would be very much more useful with innodb memcached.