[
https://issues.apache.org/jira/browse/NIFI-5449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16559543#comment-16559543
]
Dalibor Frívaldský commented on NIFI-5449:
------------------------------------------
Hi and thank you very much for looking into it so quickly. I wanted to ask why
take `String` as the input to `base64Encode` instead of `bytes[]` (and vice
versa for `base64Decode`). Wouldn't that provide more flexible interface? There
is already `toBytes` function that one can use to convert `String` to `byte[]`
and even choose his own charset (and `toString` for the other way around).
> RecordPath Language should allow base64 encode and decode
> ---------------------------------------------------------
>
> Key: NIFI-5449
> URL: https://issues.apache.org/jira/browse/NIFI-5449
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Dalibor Frívaldský
> Assignee: Matt Burgess
> Priority: Minor
>
> Currently there is no way to encode/decode a record field using base64
> encoder/decoder. Without this functionality it is, for example, impossible to
> store data into databases that require base64 representation of varbinary
> values (e.g. Apache Phoenix).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
