forked from rathboma/Hive-JSON-Serde-1
-
Notifications
You must be signed in to change notification settings - Fork 0
/
README.txt
103 lines (70 loc) · 3.54 KB
/
README.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
JsonSerde - a read/write SerDe for JSON Data
AUTHOR: Roberto Congiu <[email protected]>
Serialization/Deserialization module for Apache Hadoop Hive
This module allows hive to read and write in JSON format (see http://json.org for more info).
Features:
* Read data stored in JSON format
* Convert data to JSON format when INSERT INTO table
* arrays and maps are supported
* nested data structures are also supported.
* Field name remapping is supported (should you have a field name that is a reserved word in hive)
COMPILE
Use maven to compile the serde.
EXAMPLES
Example scripts with simple sample data are in src/test/scripts. Here some excerpts:
* Query with complex fields like arrays
CREATE TABLE json_test1 (
one boolean,
three array<string>,
two double,
four string )
ROW FORMAT SERDE 'org.openx.data.jsonserde.JsonSerDe'
STORED AS TEXTFILE;
LOAD DATA LOCAL INPATH 'data.txt' OVERWRITE INTO TABLE json_test1 ;
hive> select three[1] from json_test1;
gold
yellow
EXAMPLE WITH REMAPPED COLUMNS
CREATE TABLE json_test1 (
one boolean,
three array<string>,
two double,
four string )
ROW FORMAT SERDE 'org.openx.data.jsonserde.JsonSerDe'
WITH SERDEPROPERTIES ('json.mappings' = 'oldname:one,other_old_name:two')
STORED AS TEXTFILE;
What this means in practice, is that if your input looks like this:
{'oldname':true,'other_old_name':23.4}
it will be interpreted as if it looked like this:
{'one':true, 'two':23.4}
* Nested structures
You can also define nested structures:
add jar ../../../target/json-serde-1.0-SNAPSHOT-jar-with-dependencies.jar;
CREATE TABLE json_nested_test (
country string,
languages array<string>,
religions map<string,array<int>>)
ROW FORMAT SERDE 'org.openx.data.jsonserde.JsonSerDe'
STORED AS TEXTFILE;
-- data : {"country":"Switzerland","languages":["German","French","Italian"],"religions":{"catholic":[10,20],"protestant":[40,50]}}
LOAD DATA LOCAL INPATH 'nesteddata.txt' OVERWRITE INTO TABLE json_nested_test ;
select * from json_nested_test; -- result: Switzerland ["German","French","Italian"] {"catholic":[10,20],"protestant":[40,50]}
select languages[0] from json_nested_test; -- result: German
select religions['catholic'][0] from json_nested_test; -- result: 10
* ARCHITECTURE
For the JSON encoding/decoding, I am using a modified version of Douglas Crockfords JSON library:
https://github.com/douglascrockford/JSON-java
which is included in the distribution. I had to make some minor changes to it, for this reason
I included it in my distribution and moved it to another package (since it's included in hive!)
The SerDe builds a series of wrappers around JSONObject. Since serialization and deserialization
are executed for every (and possibly billions) record we want to minimize object creation, so
instead of serializing/deserializing to an ArrayList, I kept the JSONObject and built a cached
objectinspector around it. So when deserializing, hive gets a JSONObject, and a JSONStructObjectInspector
to read from it. Hive has Structs, Maps, Arrays and primitives while JSON has Objects, Arrays and primitives.
Hive Maps and Structs are both implemented as object, which are less restrictive than hive maps:
a JSON Object could be a mix of keys and values of different types, while hive expects you to declare the
type of map (example: map<string,string>). The user is responsible for having the JSON data structure
match hive table declaration.
* THANKS
Thanks to Douglas Crockford for the liberal license for his JSON library, and thanks to
my employer OpenX and my boss Michael Lum for letting me open source the code.