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] [Commented] (PHOENIX-3134) varbinary fields bulk load difference between MR and psql.
Date Tue, 22 Nov 2016 16:34:58 GMT

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

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

[~sergey.soldatov], I just checked and found that both CSVBulkLoad and psql.py exhibits the
same behaviour for varbinary field i.e they expect the base64 encoded value. can you please
check this again at your side too.

> varbinary fields bulk load difference between MR and psql.
> ----------------------------------------------------------
>
>                 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 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 ?



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

Mime
View raw message