-
Notifications
You must be signed in to change notification settings - Fork 65
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
4f0add2
commit 750b572
Showing
34 changed files
with
1,921 additions
and
11 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
12 changes: 12 additions & 0 deletions
12
site/content/en/docs/Archives/v2.2.x/Developer Guide/_index.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,12 @@ | ||
| --- | ||
| date: 2021-05-12 | ||
| title: "Developer Guide" | ||
| linkTitle: "Developer Guide" | ||
| weight: 20 | ||
| description: > | ||
| Learn about the concepts and the functionalities of the Connect File Pulse Plugin. | ||
| --- | ||
|
|
||
| The Developer Guide section helps you learn about the functionalities of the File Pulse Connector and the concepts | ||
| File Pulse uses to process and transform your data, and helps you obtain a deeper understanding of how File Pulse Connector works. | ||
|
|
223 changes: 223 additions & 0 deletions
223
.../content/en/docs/Archives/v2.2.x/Developer Guide/accessing-data-and-metadata.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,223 @@ | ||
| --- | ||
| date: 2021-06-10 | ||
| title: "Accessing Data and Metadata" | ||
| linkTitle: "Accessing Data and Metadata" | ||
| weight: 60 | ||
| description: > | ||
| The commons configuration for Connect File Pulse. | ||
| --- | ||
|
|
||
| Some filters (e.g : [AppendFilter](/kafka-connect-file-pulse/docs/developer-guide/filters/#appendfilter)) can be configured using *Simple Connect Expression Language*. | ||
|
|
||
| *Simple Connect Expression Language* (ScEL for short) is an expression language based on regex that allows quick access and manipulating record fields and metadata. | ||
|
|
||
| The syntaxes to define an expression are of the form : `<expression string>` or `"{{ <expression string> }}"`. | ||
|
|
||
| ScEL supports the following capabilities : | ||
|
|
||
| * **Literal expressions** | ||
| * **Field Selector** | ||
| * **Nested Navigation** | ||
| * **String substitution** | ||
| * **Functions** | ||
|
|
||
| ## Literal expressions | ||
|
|
||
| * String : `'Hello World'` | ||
| * Number : `42` | ||
| * Boolean: `True` | ||
| * Nullable: `null` | ||
|
|
||
| ## Field Selector | ||
|
|
||
| The expression language can be used to easily select one field from the input record : | ||
|
|
||
| `$.username` | ||
|
|
||
| ## Nested Navigation | ||
|
|
||
| To navigate down a struct value, just use a period to indicate a nested field value : | ||
|
|
||
| `$.address.city` | ||
|
|
||
| ## String substitution | ||
|
|
||
| The expression language can be used to easily build a new string field that concatenate multiple ones : | ||
|
|
||
| `The user {{ $.username }} is living in city {{ $.address.city }}` | ||
|
|
||
| ## Function | ||
|
|
||
| The expression language support function call : | ||
|
|
||
| `The user {{ $.username }} is living in city {{ uppercase($.address.city) }}` | ||
|
|
||
| ## Dynamic Field Selector | ||
|
|
||
| String substitution can be used to dynamically select a field : | ||
|
|
||
| The bellow example shows how to dynamically build a field selector by concatenating `$.` and | ||
| the first element present in the array field `$.values`. | ||
|
|
||
| `{{ '$.'extract_array($.values, 0) }}` | ||
|
|
||
|
|
||
| Note the use of double-quotes to define a substitution expressions | ||
|
|
||
| ## Built-in Functions | ||
|
|
||
| ScEL supports a number of predefined functions that can be used to apply a single transformation on a field. | ||
|
|
||
| | Function | Description | Syntax | | ||
| | ----------------|---------------|-----------| | ||
| | `concat` | Concatenate two or more string expressions. | `{{ concat(expr1, expr2, ...) }}` | | ||
| | `concat_ws` | Concatenate two or more string expressions, using the specified separator between each. | `{{ concat_ws(separator, prefix, suffix, expr1, expr2, ...) }}` | | ||
| | `contains` | Returns `true` if an array field's value contains the specified value | `{{ contains(array, 'value') }}` | | ||
| | `converts` | Converts a field's value into the specified type | `{{ converts(field_expr, INTEGER) }}` | | ||
| | `ends_with` | Returns `true` if a string field's value end with the specified string suffix | `{{ ends_with(field_expr, 'suffix') }}` | | ||
| | `equals` | Returns `true` if a string or number fields's value equals the specified value | `{{ equals(field_expr, value) }}` | | ||
| | `exists` | Returns `true` if an object has the specified field | `{{ exists(obj_expr, field_expr) }}` | | ||
| | `extract_array` | Returns the element at the specified position of the specified array | `{{ extract_array(array, 0) }}` | | ||
| | `hash` | Hash a given string expression, using murmur2 algorithm | `{{ hash(field_expr) }}` | | ||
| | `is_null` | Returns `true` if a field's value is null | `{{ is_null(field) }}` | | ||
| | `length` | Returns the number of elements into an array of the length of an string field | `{{ length(array) }}` | | ||
| | `lowercase` | Converts all of the characters in a string field's value to lower case | `{{ lowercase(field) }}` | | ||
| | `matches` | Returns `true` if a field's value match the specified regex | `{{ matches(field_expr, 'regex') }}` | | ||
| | `md5` | Compute the MD5 hash of string expression | `{{ md5(field_expr) }}` | | ||
| | `nlv` | Sets a default value if a field's value is null | `{{ length(array) }}` | | ||
| | `replace_all ` | Replaces every subsequence of the field's value that matches the given pattern with the given replacement string. | `{{ replace_all(field_expr, 'regex', 'replacement') }}` | | ||
| | `split` | Split a string field's value into an array using the specified regex or character | `{{ split(field_expr, regex) }}` or `{{ split(field_expr, regex, limit) }}` | | ||
| | `starts_with` | Returns `true` if an a string field's value start with the specified string prefix | `{{ starts_with(field_expr, 'prefix') }}` | | ||
| | `trim` | Trims the spaces from the beginning and end of a string. | `{{ trim(field_expr) }}` | | ||
| | `uppercase` | Converts all of the characters in a string field's value to upper case | `{{ uppercase(field_expr) }}` | | ||
| | `uuid` | Create a Universally Unique Identifier (UUID) | `{{ uuid() }}` | | ||
|
|
||
|
|
||
| In addition, ScEL supports nested functions. | ||
|
|
||
| For example, the following expression can be used to replace all whitespace characters after transforming our field's value into lowercase. | ||
|
|
||
| ``` | ||
| replace_all(lowercase($.field), '\\s', '-') | ||
| ``` | ||
|
|
||
| {{% alert title="Limitation" color="warning" %}} | ||
| Currently, FilePulse does not support user-defined functions (UDFs). So you cannot register your own functions to enrich the expression language. | ||
| {{% /alert %}} | ||
|
|
||
|
|
||
| ## Scopes | ||
|
|
||
| In the previous section, we have shown how to use the expression language to select a specific field. | ||
| The selected field was part of our the current record being processed. | ||
|
|
||
| Actually, ScEL allows you to get access to additional fields through the used of scopes. | ||
| Basically, a scope defined the root object on which a selector expression must evaluated. | ||
|
|
||
| The syntax to define an expression with a scope is of the form : "`$<scope>.<selector expression string>`". | ||
|
|
||
| By default, if no scope is defined in the expression, the scope `$value` is implicitly used. | ||
|
|
||
| ScEL supports a number of predefined scopes that can be used for example : | ||
|
|
||
| - **To define the topic for the record.** | ||
| - **To define the key for the record.** | ||
| - **To get access to metadata about the source file.** | ||
| - Etc. | ||
|
|
||
| | Scope | Description | Type | | ||
| |--- | --- |--- | | ||
| | `$headers` | The record headers | - | | ||
| | `$key` | The record key | `string` | | ||
| | `$metadata` | The file metadata | `struct` | | ||
| | `$offset` | The offset information of this record into the source file | `struct` | | ||
| | `$system` | The system environment variables and runtime properties | `struct` | | ||
| | `$timestamp` | The record timestamp | `long` | | ||
| | `$topic` | The output topic | `string` | | ||
| | `$value` | The record value| `struct` | | ||
| | `$variables` | The contextual filter-chain variables| `map[string, object]` | | ||
|
|
||
| Note, that in case of failures more fields are added to the current filter context (see : [Handling Failures](/kafka-connect-file-pulse/docs/developer-guide/handling-failures/)) | ||
|
|
||
| ### Record Headers | ||
|
|
||
| The scope `headers` allows defining the headers of the output record. | ||
|
|
||
| ### Record key | ||
|
|
||
| The scope `key` allows defining the key of the output record. Only string key is currently supported. | ||
|
|
||
| ### Source Metadata | ||
|
|
||
| The scope `metadata` allows read access to information about the file being processing. | ||
|
|
||
| | Predefined Fields (ScEL) | Description | Type | | ||
| |--- | --- |--- | | ||
| | `$metadata.name` | The file name | `string` | | ||
| | `$metadata.path` | The file directory path | `string` | | ||
| | `$metadata.absolutePath` | The file absolute path | `string` | | ||
| | `$metadata.hash` | The file CRC32 hash | `int` | | ||
| | `$metadata.lastModified` | The file last modified time. | `long` | | ||
| | `$metadata.size` | The file size | `long` | | ||
| | `$metadata.inode` | The file Unix inode | `long` | | ||
|
|
||
| ## Record Offset | ||
|
|
||
| The scope `offset` allows read access to information about the original position of the record into the source file. | ||
| The available fields depend on the configured FileInputRecord. | ||
|
|
||
| | Predefined Fields (ScEL) | Description | Type | | ||
| |--- | --- |--- | | ||
| | `$offset.timestamp` | The creation time of the record (millisecond) | `long` | | ||
|
|
||
| Information only available if `RowFilterReader` is configured. | ||
|
|
||
| | Predefined Fields (ScEL) | Description | Type | | ||
| |--- | --- |--- | | ||
| | `$offset.startPosition` | The start position of the record into the source file | `long` | | ||
| | `$offset.endPosition` | The end position of the record into the source file | `long` | | ||
| | `$offset.size` | The size in bytes | `long` | | ||
| | `$offset.row` | The row number of the record into the source | `long` | | ||
|
|
||
| Information only available if `BytesArrayInputReader` is configured. | ||
|
|
||
| | Predefined Fields (ScEL) | Description | Type | | ||
| |--- | --- |--- | | ||
| | `$offset.startPosition` | The start position of the record into the source file (always equals to 0) | `long` | | ||
| | `$offset.endPosition` | The end position of the record into the source file (equals to the file size) | `long` | | ||
|
|
||
| Information only available if `AvroFilterInputReader` is configured. | ||
|
|
||
| | Predefined Fields (ScEL) | Description | Type | | ||
| |--- | --- |--- | | ||
| | `$offset.blockStart` | The start position of the current block | `long` | | ||
| | `$offset.position` | The position into the current block. | `long` | | ||
| | `$offset.records` | The number of record read into the current block. | `long` | | ||
|
|
||
| ## System | ||
|
|
||
| The scope `system` allows accessing to the system environment variables and runtime properties. | ||
|
|
||
| | Predefined Fields (ScEL) | Description | Type | | ||
| |--- | --- |--- | | ||
| | `$system.env` | The system environment variables. | `map[string, string]` | | ||
| | `$system.props` | The system environment properties. | `map[string, string]` | | ||
|
|
||
| ## Timestamp | ||
|
|
||
| The scope `$timestamp` allows defining the timestamp of the output record. | ||
|
|
||
| ## Topic | ||
|
|
||
| The scope `$topic` allows defining the target topic of the output record. | ||
|
|
||
| ## Value | ||
|
|
||
| The scope `$value` allows defining the fields of the output record | ||
|
|
||
| ## Variables | ||
|
|
||
| The scope `$variables` allows read/write access to a simple key-value map structure. | ||
| This scope can be used to share user-defined variables between [Processing Filters](/kafka-connect-file-pulse/docs/developer-guide/filters/). | ||
|
|
||
| Note : variables are not cached between records. |
Oops, something went wrong.