Kazaam was created with the goal of supporting easy and fast transformations of JSON data with Golang. This functionality provides us with an easy mechanism for taking intermediate JSON message representations and transforming them to formats required by arbitrary third-party APIs.
Inspired by Jolt, Kazaam supports JSON to JSON transformation via a transform "specification" also defined in JSON. A specification is comprised of one or more "operations". See Specification Support, below, for more details.
API Documentation is available at http://godoc.org/gopkg.in/qntfy/kazaam.v2.
Kazaam currently supports the following transforms:
- shift
- concat
- coalesce
- default
- pass
The shift transform is the current Kazaam workhorse used for remapping of fields. The specification supports jsonpath-esque JSON accesses and sets. Concretely
{
"operation": "shift",
"spec": {
"object.id": "doc.uid",
"gid2": "doc.guid[1]",
"allGuids": "doc.guidObjects[*].id"
}
}executed on a JSON message with format
{
"doc": {
"uid": 12345,
"guid": ["guid0", "guid2", "guid4"],
"guidObjects": [{"id": "guid0"}, {"id": "guid2"}, {"id": "guid4"}]
},
"top-level-key": null
}would result in
{
"object": {
"id": 12345
},
"gid2": "guid2",
"allGuids": ["guid0", "guid2", "guid4"]
}The jsonpath implementation supports a few special cases:
- Array accesses: Retrieve
nth element from array - Array wildcarding: indexing an array with
[*]will return every matching element in an array - Top-level object capture: Mapping
$into a field will nest the entire original object under the requested key
The shift transform also supports a "require" field. When set to true,
Kazaam will throw an error if any of the paths in the source JSON are not
present.
The concat transform allows to combine fields and literal strings into a single string value.
{
"operation": "concat",
"spec": {
"sources": [{
"value": "TEST"
}, {
"path": "a.timestamp"
}],
"targetPath": "a.timestamp",
"delim": ","
}
}executed on a JSON message with format
{
"a": {
"timestamp": 1481305274
}
}would result in
{
"a": {
"timestamp": "TEST,1481305274"
}
}Notes:
- sources: list of items to combine (in the order listed)
- literal values are specified via
value - field values are specified via
path(supports the same addressing asshift)
- literal values are specified via
- targetPath: where to place the resulting string
- if this an existing path, the result will replace current value.
- delim: Optional delimiter
The concat transform also supports a "require" field. When set to true,
Kazaam will throw an error if any of the paths in the source JSON are not
present.
A coalesce transform provides the ability to check multiple possible keys to find a desired value. The first matching key found of those provided is returned.
{
"operation": "coalesce",
"spec": {
"firstObjectId": ["doc.guidObjects[0].uid", "doc.guidObjects[0].id"]
}
}executed on a json message with format
{
"doc": {
"uid": 12345,
"guid": ["guid0", "guid2", "guid4"],
"guidObjects": [{"id": "guid0"}, {"id": "guid2"}, {"id": "guid4"}]
}
}would result in
{
"doc": {
"uid": 12345,
"guid": ["guid0", "guid2", "guid4"],
"guidObjects": [{"id": "guid0"}, {"id": "guid2"}, {"id": "guid4"}]
},
"firstObjectId": "guid0"
}A default transform provides the ability to set a key's value explicitly. For example
{
"operation": "default",
"spec": {
"type": "message"
}
}would ensure that the output JSON message includes {"type": "message"}.
A pass transform, as the name implies, passes the input data unchanged to the output. This is used internally when a null transform spec is specified, but may also be useful for testing.
To start, go get the versioned repository::
go get gopkg.in/qntfy/kazaam.v2If you want to create an executable binary from this project, follow
these steps (you'll need go installed and $GOPATH set):
go get gopkg.in/qntfy/kazaam.v2
cd $GOPATH/src/gopkg.in/qntfy.kazaam.v2/kazaam
go installThis will create an executable in $GOPATH/bin like you
would expect from the normal go build behavior.
See godoc examples.