1. Home
  2. Sesam Hub
  3. Documentation
  4. Data Transformation Language
  5. Misc

Misc

hash128

Description

Examples
Arguments:
ALGORITM(“murmur3”)
SEED(integer-expression{0|1})
VALUES(value-expression{1})

Generates 128 bit integer hashes from bytes and strings. Values of other types are ignored. This function can be used to generate content hashes. The only supported algoritm is “murmur3” (MurmurHash3).
The function takes an optional seed argument. The seed can be used to randomize the hash function.
["hash128", "murmur3", "abc"]

Returns 79267961763742113019008347020647561319.

["hash128", "murmur3", ["combine", "abc", 123, "def"]]

Returns [[79267961763742113019008347020647561319,
114697464648834432121201791580882983835]].

is-changed

Description

Examples
Arguments:
FUNCTION(function-expression{1}),

Returns true if the results of evaluating the FUNCTION expression on the current version and the previous version of the source entity are different.

If the previous version does not exist then the is-changed
function returns null. This means that we don’t know if it has changed.

If either the current or the previous version of the entity
has _deleted set to true then the is-changed
function returns true.

Note

If the source is not a dataset source then the is-changed function will always return null.

Note

Do not use the is-changed function to track state changes in the sink. This does not work as the pipe may not actually have seen the previous version of the source entity. This is particularly likely if the dataset source reads the latest versions only. Compaction in the source dataset may also prevent the pipe from actually seeing all versions.

If you need to do track state changes in the dataset sink then do hops to the sink dataset. In that case you have to set "batch_size": 1 on the pipe and "set_initial_offset": "onload" on the dataset sink. The former so that the pipe can see its own writes and the latter so that the pipe don’t have to wait for the sink dataset to be populated (something that will never happen as the pipe won’t be allowed to run).
["is-changed", "_.name"]

Returns true if the source entity’s name property changed.

["is-changed", ["list", "_.height", "_.width"]]

Returns true if the source entity’s height or width properties changed.

["is-changed", ["-", "_.end", "_.start"]]

Returns true if the source entity’s distance between start and end changed.

literal

Description

Examples
Arguments:
VALUE(value{1})

A function that returns its argument. The argument is not evaluated and is returned as-is. This function is used to avoid literal values having side-effects from expression evaluation.
["literal", "_S.foo"]

Returns the string _S.foo, and not the value of the source entity’s foo property.

["literal", {"foo": 1, "bar": 2}]

Returns the dict {"foo": 1, "bar": 2}.

["literal", ["upper", "hello"]]

Returns the array ["upper", "hello"], and not the result of evaluating the DTL expression.

tuples

Description

Examples
Arguments:
VALUES(value-expression{>0})

Constructs a list of tuples, the product of the values given in the arguments. The tuple length is equal to the number of function arguments. null values are ignored.

This function is a good choice when you need to do joins on composite keys.
["tuples"]

Returns [].

["tuples", "a", "b", "c"]

Returns [["a", "b", "c"]].

["tuples", ["list", 1, 2], 3]

Returns [[1, 3], [2, 3]].

["tuples",
["list", 1, 2], ["list", 3, null, 4, 5]]

Returns [[1, 3], [1, 4], [1, 5],
[2, 3], [2, 4], [2, 5]]. The null value was ignored.

completeness

Description

Examples
Arguments:
VIA_DATASET_ID(string{1})
DATASET_ID(string{1})

Looks up the completeness value of the dataset DATASET_ID via the dataset VIA_DATASET_ID. Completeness values are propagated from upstream to downstream pipes when the pipes run, so the completeness value of DATASET_ID can be different when accessed via different downstream datasets.
This function returns a datetime object on success, or null if either of the datasets don’t exist, or if the dataset VIA_DATASET_ID doesn’t have any record of the completeness of the dataset DATASET_ID.
["completeness", "pipe1", "pipe1"]

Since VIA_DATASET_ID is the same as DATASET_ID this will give the up-to-date completeness-value of the dataset pipe1. (example: “~t2015-07-28T07:46:00Z”).

["completeness", "pipe-that-doesnt-have-pipe1-upstream", "pipe1"]

Returns null, since the pipe that writes to the “pipe-that-doesnt-have-pipe1-upstream” hasn’t heard about the “pipe1” dataset.

["completeness", "pipe-that-does-have-pipe1-upstream", "pipe1"]

Returns the last “pipe1” completeness value that the pipe writing the “pipe-that-does-have-pipe1-upstream” dataset has seen.
This value can be older than the current completeness value of “pipe1”, since the latest completeness value might not have been propagated down to the “pipe-that-does-have-pipe1-upstream” pipe yet.

previous

Math

next

Namespaced identifiers