[jira] [Commented] (NIFI-2997) Provide processor to convert between standard encodings

["Andy LoPresto (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15645907#comment-15645907 ] 

Andy LoPresto commented on NIFI-2997:
-------------------------------------

[~JPercivall] pointed out that [((ConvertCharacterSet}}|https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.standard.ConvertCharacterSet/index.html] provides some of this functionality, although only on flowfile content and only the character sets [listed here|https://docs.oracle.com/javase/8/docs/technotes/guides/intl/encoding.doc.html], so by my estimation, no binary, hexadecimal, or Base64. He also noted that Base64 encoding/decoding was added to the Expression Language in 1.0.0. 

> Provide processor to convert between standard encodings
> -------------------------------------------------------
>
>                 Key: NIFI-2997
>                 URL: https://issues.apache.org/jira/browse/NIFI-2997
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Extensions
>    Affects Versions: 1.0.0
>            Reporter: Andy LoPresto
>              Labels: ascii, base64, encoding, hexadecimal
>
> A common request is to convert some data between ASCII, hexadecimal, binary, etc. format. While I am generally not a fan of "catch-all" processors and would usually suggest following the NiFi precedent/'Unix tool mentality", the conversion between these encodings is a similar process, so I think a single processor with selectable input and output formats is sufficient here. In actuality, I would suggest the core functionality be captured in a library/service with pluggable implementations and then be exposed to one processor for content conversion and one for attribute conversion. If {{Base64}} is included, this could replace the [{{Base64EncodeContent}}|https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.standard.Base64EncodeContent/index.html] processor (or it could at least be marked as {{@Deprecated}}). 
> *Processors*
> * EncodeAttribute
> * EncodeContent
> *Formats*
> * Binary
> * ASCII
> * Hexadecimal
> * UTF-8
> * UTF-16
> * Base64



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)