phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ankit Singhal (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-3134) varbinary fields bulk load difference between MR/psql and upserts
Date Wed, 28 Dec 2016 07:46:59 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ankit Singhal updated PHOENIX-3134:
-----------------------------------
    Description: 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?    (was:
At the moment we have strange difference between how MR and psql loads varbinary. MR loads
field as it from csv, but psql expects that it's base64 encoded. Should we add an option to
load it as a plain data or base64? Something like --encoding=no/base64 ?)

> 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)

Mime
View raw message