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
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
use ;
use Value;
use crateJsonPointer;
/// The JSON transformation specification.
///
/// Composes a list of operation specifications. Each operation has its own DSL (Domain Specific
/// Language) in order to facilitate its narrow job.
///
/// ```
/// use fluvio_jolt::TransformSpec;
///
/// let spec: TransformSpec =
/// serde_json::from_str(r#"[
/// {
/// "operation": "shift",
/// "spec": {
/// "name": "data.name",
/// "account": "data.account"
/// }
/// }
/// ]"#).unwrap();
/// ```
///
/// ### `Shift` operation
/// Specifies where the data from the input JSON should be placed in the output JSON, or in other
/// words, how the input JSON/data should be shifted around to make the output JSON/data.
///
/// At a base level, a single `shift` operation is a mapping from an input path to an output path,
/// similar to the `mv` command in Unix, `mv /var/data /var/backup/data`.
///
/// The input path is a JSON tree structure, and the output path is flattened "dot notation" path
/// notation.
///
/// For example, given this simple input JSON:
/// <pre>
/// {
/// "id": 1,
/// "name": "John Smith",
/// "account": {
/// "id": 1000,
/// "type": "Checking"
/// }
/// }
/// </pre>
/// A simple spec could be constructed by copying that input, and modifying it to supply an output
/// path for each piece of data:
/// <pre>
/// {
/// "id": "data.id",
/// "name": "data.name",
/// "account": "data.account"
/// }
/// </pre>
/// would produce the following output JSON:
/// <pre>
/// {
/// "data" : {
/// "id": 1,
/// "name": "John Smith",
/// "account": {
/// "id": 1000,
/// "type": "Checking"
/// }
/// }
/// }
/// </pre>
/// #### Wildcards
/// The `shift` specification on the keys level supports wildcards and conditions:
/// 1. `*` - match everything
/// 2. `name1|name2|nameN` - match any of the specified names
///
/// `&` lookup allows referencing the values captured by the `*` or `|`.
/// It allows for specs to be more compact. For example, for this input:
/// <pre>
/// {
/// "id": 1,
/// "name": "John Smith",
/// "account": {
/// "id": 1000,
/// "type": "Checking"
/// }
/// }
/// </pre>
/// to get the output:
/// <pre>
/// {
/// "data" : {
/// "id": 1,
/// "name": "John Smith",
/// "account": {
/// "id": 1000,
/// "type": "Checking"
/// }
/// }
/// }
/// </pre>
/// the spec with wildcards would be:
/// <pre>
/// {
/// "*": "data.&0"
/// }
/// </pre>
/// If you want only `id` and `name` in the output, the spec is:
/// <pre>
/// {
/// "id|name": "data.&0"
/// }
/// </pre>
///
///
/// `&` wildcard also allows to dereference any level of the path of given node:
/// <pre>
/// {
/// "foo": {
/// "bar" : {
/// "baz": "new_location.&0.&1.&2" // &0 = baz, &1 = bar, &2 = foo
/// }
/// }
/// }
/// }
/// </pre>
/// for the input:
/// <pre>
/// {
/// "foo": {
/// "bar": {
/// "baz": "value"
/// }
/// }
/// }
/// </pre>
/// will produce:
/// <pre>
/// {
/// "new_location": {
/// "baz": {
/// "bar": {
/// "foo": "value"
/// }
/// }
/// }
/// }
/// </pre>
///
/// ### `Default` operation
/// Applies default values if the value is not present in the input JSON.
///
/// For example, given this simple input JSON:
/// <pre>
/// {
/// "phones": {
/// "mobile": 01234567,
/// "country": "US"
/// }
/// }
/// </pre>
/// with the following specification for `default` operation:
/// <pre>
/// {
/// "phones": {
/// "mobile": 0000000,
/// "code": "+1"
/// }
/// }
/// </pre>
/// the output JSON will be:
/// <pre>
/// {
/// "phones": {
/// "mobile": 01234567,
/// "country": "US",
/// "code": "+1"
/// }
/// }
/// </pre>
/// As you can see, the field `mobile` remains not affected while the `code` has a default '+1' value.
///
/// ### `Remove` operation
/// Removes content from the input JSON.
/// The spec structure matches the input JSON structure. The value of fields is ignored.
///
/// For example, given this simple input JSON:
/// <pre>
/// {
/// "phones": {
/// "mobile": 01234567,
/// "country": "US"
/// }
/// }
/// </pre>
/// you can remove the `country` by the following specification for `remove` operation:
/// <pre>
/// {
/// "phones": {
/// "country": ""
/// }
/// }
/// </pre>
/// the output JSON will be:
/// <pre>
/// {
/// "phones": {
/// "mobile": 01234567
/// }
/// }
/// </pre>
;
pub
pub
pub ;
pub