[jira] [Commented] (PHOENIX-3134) varbinary fields bulk load difference between MR/psql and upserts

["Ankit Singhal (JIRA)" <ji...@apache.org>]

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

Ankit Singhal commented on PHOENIX-3134:
----------------------------------------

Added an option (--binaryEncoding or -b) to specify binary encoding in CSVBulkLoadTool and pSQL.py. BinaryEncoding can also be provided by "phoenix.upload.binaryDataType.encoding".
Currently, we can support only BASE64 and ASCII encoding for Binary data type.



> varbinary fields bulk load difference between MR/psql and upserts
> -----------------------------------------------------------------
>
>                 Key: PHOENIX-3134
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3134
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.7.0
>            Reporter: Sergey Soldatov
>            Assignee: Sergey Soldatov
>
> At the moment we have strange difference between how MR/psql upload and upsert handles varbinary. MR/ psql expects that it's base64 encoded whereas upsert takes input as a string. Should we add an option to load it as a plain data or base64 in MR/psql?  



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