Translates content and attributes from one language to another
yandex, translate, translation, language
In the list below, the names of required properties appear in bold. Any other properties (not in bold) are considered optional. The table also indicates any default values, and whether a property supports the NiFi Expression Language.
Name | Default Value | Allowable Values | Description |
---|---|---|---|
Yandex API Key | The API Key that is registered with Yandex | ||
Input Language | es | The language of incoming data Supports Expression Language: true | |
Target Language | en | The language to translate the text into Supports Expression Language: true | |
Translate Content | false |
| Specifies whether or not the content should be translated. If false, only the text specified by user-defined properties will be translated. |
Character Set | UTF-8 | Specifies the character set of the data to be translated Supports Expression Language: true |
Dynamic Properties allow the user to specify both the name and value of a property.
Name | Value | Description |
---|---|---|
The name of an attribute to set that will contain the translated text of the value | The value to translate | User-defined properties are used to translate arbitrary text based on attributes. Supports Expression Language: true |
Name | Description |
---|---|
translation.failure | This relationship is used if the translation cannot be performed for some reason other than communications failure |
comms.failure | This relationship is used when the translation fails due to a problem such as a network failure, and for which the translation should be attempted again |
success | This relationship is used when the translation is successful |
Name | Description |
---|---|
yandex.translate.failure.reason | If the text cannot be translated, this attribute will be set indicating the reason for the failure |
language | When the translation succeeds, if the content was translated, this attribute will be set indicating the new language of the content |