Combine the power of MySQL and NoSQL Database with MySQL

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Combining the Power of SQL and
NoSQL Databases with MySQL
Morgan Tocker
MySQL Product Manager (Server)
Copyright © 2016, Oracle and/or its affiliates. All rights reserved.

Safe Harbor Statement
The following is intended to outline our general product direction. It is intended for
information purposes only, and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described for Oracle’s products remains at the sole discretion of Oracle.
3

Today’s Agenda
4
Introduction
Core New JSON Features
Use Cases
1
2
3

MySQL: Ubiquity & Market Share
5
MySQL is the 2nd most popular database!

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. | 6
More Jobs than Developers/DBAs
• Growing Demand
Source: StackOverflow, Developer Hiring Trends in 2017
More Developers/DBAs than Jobs

MySQL Powers the Web

1. Google
2. Facebook
3. YouTube
4. Baidu
5. Yahoo!
6. Amazon
7. Wikipedia
8. QQ
9. Google.co.in
10. Twitter
11. Live.com
12. Taobao
13. Msn.com
14. Yahoo.co.jp
15. Sina
16. Linkedin.com
17. Google.co.jp
18. Weibo
19. Bing.com
20. Yandaz.ru
Global Top 20 Sites: Powered by MySQL
Source: Wikipedia 2016
8

MySQL Powers Social

MySQL Powers eCommerce

MySQL Powers SaaS

MySQL Powers FinTech
12

MySQL Powers Unicorns

MySQL Powers the Cloud

MySQL 5.7 GA – October 2015
Enhanced InnoDB: faster online & bulk
load operations
Replication Improvements (incl. multi-
source, multi-threaded slaves...)
New Optimizer Cost Model: greater user
control & better query performance
Performance Schema Improvements
MySQL SYS Schema
Performance & Scalability Manageability
3 X Faster than MySQL 5.6
Improved Security: safer initialization,
setup & management
Native JSON Support

Today’s Agenda
16
Introduction
Use Cases
1
2
3
2
1

Core New JSON features in MySQL 5.7
1. Native JSON datatype
2. JSON Functions
3. Generated Columns
4. JSON Comparator
17

The JSON Type
18
CREATE TABLE employees (data JSON);
INSERT INTO employees VALUES ('{"id": 1, "name": "Jane"}');
INSERT INTO employees VALUES ('{"id": 2, "name": "Joe"}');
SELECT * FROM employees;
+---------------------------+
| data |
+---------------------------+
| {"id": 1, "name": "Jane"} |
| {"id": 2, "name": "Joe"} |
+---------------------------+
2 rows in set (0,00 sec)

JSON Type Tech Specs
• utf8mb4 character set
• Optimized for read intensive workload
• Parse and validation on insert only
• Fast access to array cells by index
19

JSON Type Tech Specs (cont.)
• Supports all native JSON types
• Numbers, strings, bool
• Objects, arrays
• Extended
• Date, time, datetime, timestamp
• Other
20

Advantages over TEXT/VARCHAR
1. Provides Document Validation:
2. Efficient Binary Format
Allows quicker access to object members and array elements
21
INSERT INTO employees VALUES ('some random text');
ERROR 3130 (22032): Invalid JSON text: "Expect a value
here." at position 0 in value (or column) 'some random
text'.

Using Real Life Data
• Via SF OpenData
• 206K JSON objects
representing subdivision
parcels.
22
CREATE TABLE features (
id INT NOT NULL auto_increment primary key,
feature JSON NOT NULL
);
http://mysqlserverteam.com/taking-the-new-mysql-5-7-json-features-for-a-test-drive/

{
"type":"Feature",
"geometry":{
"type":"Polygon",
"coordinates":[
[
[-122.42200352825247,37.80848009696725,0],
[-122.42207601332528,37.808835019815085,0],
[-122.42110217434865,37.808803534992904,0],
[-122.42106256906727,37.80860105681814,0],
[-122.42200352825247,37.80848009696725,0]
]
]
},
"properties":{
"TO_ST":"0",
"BLKLOT":"0001001",
"STREET":"UNKNOWN",
"FROM_ST":"0",
"LOT_NUM":"001",
"ST_TYPE":null,
"ODD_EVEN":"E",
"BLOCK_NUM":"0001",
"MAPBLKLOT":"0001001"
}
}

JSON Functions
24
SET @document = '[10, 20, [30, 40]]';
SELECT JSON_EXTRACT(@document, '$[1]');
+---------------------------------+
| JSON_EXTRACT(@document, '$[1]') |
+---------------------------------+
| 20 |
+---------------------------------+
1 row in set (0.01 sec)

JSON_EXTRACT
• Accepts a JSON Path, which is similar to a selector:
• JSON_EXTRACT also supports two short hand operators:
column_name->"$.type" (extract)
column_name->>"$.type" (extract + unquote)
25
$("#type") JSON_EXTRACT
(column_name, "$.type")

Basic Find a Record
27
SELECT * FROM features
WHERE feature->"$.properties.STREET" = 'MARKET'
LIMIT 1G
************************* 1. row *************************
id: 12250
feature: {"type": "Feature", "geometry": {"type": "Polygon",
"coordinates": [[[-122.39836263491878, 37.79189388899312, 0],
[-122.39845248797837, 37.79233030084018, 0], [-
122.39768507706792, 37.7924280850133, 0], [-
122.39836263491878, 37.79189388899312, 0]]]}, "properties":
{"TO_ST": "388", "BLKLOT": "0265003", "STREET": "MARKET",
"FROM_ST": "388", "LOT_NUM": "003", "ST_TYPE": "ST",
"ODD_EVEN": "E", "BLOCK_NUM": "0265", "MAPBLKLOT":
"0265003"}}

Find where not exists
28
SELECT * FROM features
WHERE feature->"$.properties.STREET" IS NULL
LIMIT 1G
Empty set (0.39 sec)

Naive Performance Comparison
29
Unindexed traversal of 206K documents
# as JSON type
SELECT DISTINCT
feature->>"$.type" as json_extract
FROM features;
+--------------+
| json_extract |
+--------------+
| Feature |
+--------------+
# as TEXT type
SELECT DISTINCT
feature->>"$.type" as json_extract
FROM features;
+--------------+
| json_extract |
+--------------+
| Feature |
+--------------+
Using short cut for
JSON_UNQUOTE +
JSON_EXTRACT.
Explanation: Binary format of JSON type is very efficient at searching.
Storing as TEXT performs over 10x worse at traversal.

Introducing Generated Columns
30
CREATE TABLE t1 (
id INT NOT NULL PRIMARY KEY auto_increment,
my_integer INT,
my_integer_plus_one INT AS (my_integer+1)
);
UPDATE t1 SET my_integer_plus_one = 10 WHERE id = 1;
ERROR 3105 (HY000): The value specified for generated
column 'my_integer_plus_one' in table 't1' is not
allowed.
Column automatically
maintained based on your
specification.
Read-only of course
Id my_integer my_integer_plus_one
1 10 11
2 20 21
3 30 31
4 40 41

Generated Columns Support Indexes!
31
From table scan on 206K documents to index scan on 206K materialized values
ALTER TABLE features ADD feature_type VARCHAR(30) AS
(feature->"$.type");
Query OK, 0 rows affected (0.01 sec)
Records: 0 Duplicates: 0 Warnings: 0
ALTER TABLE features ADD INDEX (feature_type);
SELECT DISTINCT feature_type FROM features;
+--------------+
| feature_type |
+--------------+
| "Feature" |
+--------------+
Meta data change only
(FAST). Does not need to
touch table.
Creates index only. Does
not modify table rows.
Down from 1.25 sec to
0.06 sec

Generated Columns (cont.)
• Used for “functional index”
• Available as either VIRTUAL (default) or STORED:
• Both types of computed columns permit for indexes to be added.
32
ALTER TABLE features ADD feature_type varchar(30) AS
(feature->"$.type") STORED;

Indexing Options Available
33
STORED VIRTUAL
Primary and Secondary
BTREE, Fulltext, GIS
Mixed with fields
Requires table rebuild
Not Online
Secondary Only
BTREE Only
Mixed with fields
No table rebuild
INSTANT Alter
Faster Insert
Bottom Line: Unless you need a PRIMARY KEY, FULLTEXT or GIS index
VIRTUAL is probably better.

JSON Path Search
• Provides a novice way to know the path. To retrieve via:
[[database.]table.]column->"$<path spec>"
34
SELECT JSON_SEARCH(feature,
'one', 'MARKET') AS
extract_path
FROM features
WHERE id = 121254;
+-----------------------+
| extract_path |
+-----------------------+
| "$.properties.STREET" |
+-----------------------+
SELECT
feature-
>"$.properties.STREET"
AS property_street
FROM features
WHERE id = 121254;
+-----------------+
| property_street |
+-----------------+
| "MARKET" |
+-----------------+

Create JSON_OBJECT
35
SELECT JSON_OBJECT('id', id,
'street', feature->"$.properties.STREET",
'type', feature->"$.type"
) AS json_object
FROM features ORDER BY RAND() LIMIT 3;
+--------------------------------------------------------+
| json_object |
+--------------------------------------------------------+
| {"id": 122976, "type": "Feature", "street": "RAUSCH"} |
| {"id": 148698, "type": "Feature", "street": "WALLACE"} |
| {"id": 45214, "type": "Feature", "street": "HAIGHT"} |
+--------------------------------------------------------+

Create JSON_ARRAY
36
SELECT JSON_REPLACE(feature, '$.type', JSON_ARRAY('feature', 'bug')) as
json_object FROM features LIMIT 1;
+--------------------------------------------------------+
| json_object |
+--------------------------------------------------------+
| {"type": ["feature", "bug"], "geometry": {"type": ..}} |
+--------------------------------------------------------+

JSON Functions
• 5.7 supports functions to CREATE, SEARCH, MODIFY and RETURN JSON
values:
37
JSON_ARRAY_APPEND()
JSON_ARRAY_INSERT()
JSON_ARRAY()
JSON_CONTAINS_PATH()
JSON_CONTAINS()
JSON_DEPTH()
JSON_EXTRACT()
JSON_INSERT()
JSON_KEYS()
JSON_LENGTH()
JSON_MERGE()
JSON_OBJECT()
JSON_QUOTE()
JSON_REMOVE()
JSON_REPLACE()
JSON_SEARCH()
JSON_SET()
JSON_TYPE()
JSON_UNQUOTE()
JSON_VALID()
https://dev.mysql.com/doc/refman/5.7/en/json-functions.html

JSON Comparator
38
SELECT CAST(1 AS JSON) = 1;
+---------------------+
| CAST(1 AS JSON) = 1 |
+---------------------+
| 1 |
+---------------------+
SELECT CAST('{"a": 10, "num": 1.1}' AS JSON) = CAST('{"num": 1.1, "a":10}' AS JSON);
+------------------------------------------------------------------------------+
| CAST('{"a": 10, "num": 1.1}' AS JSON) = CAST('{"num": 1.1, "a":10}' AS JSON) |
+------------------------------------------------------------------------------+
| 1 |
+------------------------------------------------------------------------------+
JSON value of 1 equals 1
JSON Objects Compare

JSON Comparator (cont.)
39
Join JSON value to MySQL value
CREATE TABLE t1 (id INT NOT NULL PRIMARY KEY, a INTEGER NOT NULL);
CREATE TABLE t2 (id INT NOT NULL PRIMARY KEY, doc JSON NOT NULL);
INSERT INTO t1 VALUES (1, 1), (2, 2);
INSERT INTO t2 VALUES (1, JSON_OBJECT('a', 1)), (2, JSON_OBJECT('a', 2));
SELECT t1.id, t1.a, t2.doc FROM t1 INNER JOIN t2 ON (t1.a=t2.doc->"$.a");
+----+---+----------+
| id | a | doc |
+----+---+----------+
| 1 | 1 | {"a": 1} |
| 2 | 2 | {"a": 2} |
+----+---+----------+

Today’s Agenda
40
Introduction
Use cases
1
22
1
2
3

JSON or Column?
• Up to you!
• Advantages to both approaches
41

Storing as a Column
• Easier to apply a schema to your application
• Schema may make applications easier to maintain over time, as change is
controlled;
• Do not have to expect as many permutations
• Allows some constraints over data
42

Storing as JSON
• More flexible way to represent data that is hard to model in schema;
• Imagine you are a SaaS application serving many customers
• Strong use-case to support custom-fields
• Historically this may have used Entity–attribute–value model (EAV). Does not always
perform well
43

JSON (cont.)
• Easier denormalization; an optimization that is important in some specific
situations
• No painful schema changes*
• Easier prototyping
• Fewer types to consider
• No enforced schema, start storing values immediately
44
* MySQL 5.6+ has Online DDL. This is not as large of an issue as it was historically.

Schema + Schemaless
45
SSDs have capacity_in_gb, CPUs have a core_count. These attributes
are not consistent across products.
CREATE TABLE pc_components (
id INT NOT NULL PRIMARY KEY,
description VARCHAR(60) NOT NULL,
vendor VARCHAR(30) NOT NULL,
serial_number VARCHAR(30) NOT NULL,
attributes JSON NOT NULL
);

Road Map
• In-place partial update of JSON/BLOB (performance)
• Partial streaming of JSON/BLOB (replication)
• Full text and GIS index on virtual columns
• Currently works for "STORED"
• More Functions:
• Aggregate Functions
• Table Function
• Pretty print
• Binary Size / Binary Free
46

Resources
• http://mysqlserverteam.com/
• http://mysqlserverteam.com/tag/json/
• https://dev.mysql.com/doc/refman/5.7/en/mysql-nutshell.html
• http://dev.mysql.com/doc/relnotes/mysql/5.7/en/
• https://dev.mysql.com/doc/refman/5.7/en/json.html
• https://dev.mysql.com/doc/refman/5.7/en/json-functions.html
• http://www.thecompletelistoffeatures.com
47

Combine the power of MySQL and NoSQL Database with MySQL

Combine the power of MySQL and NoSQL Database with MySQL

Recommended

Recommended

More Related Content

Recently uploaded

Recently uploaded (20)

Featured

Featured (20)

Combine the power of MySQL and NoSQL Database with MySQL

Editor's Notes