[
https://issues.apache.org/jira/browse/PHOENIX-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14315114#comment-14315114
]
Nick Dimiduk commented on PHOENIX-1277:
---------------------------------------
When we get around to moving rowkeys over to the HBase DataType interface, the
rule enforcement for compound keys would be enforced at the Struct interface,
not down in the component DataType. Maybe that's too big of a refactor to hold
up a working solution to this specific issue. Just my 0.02$ Looking forward a
couple steps.
> CSVCommonsLoader not allowing null CHAR values (non PK)
> -------------------------------------------------------
>
> Key: PHOENIX-1277
> URL: https://issues.apache.org/jira/browse/PHOENIX-1277
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0
> Reporter: Carter Shanklin
> Priority: Minor
>
> With this simple table:
> {code}
> create table dummy ( x integer primary key, y char(10) );
> {code}
> And dataset
> {code}
> $ cat DummyValues.csv
> 1,x
> 2,
> 3,z
> {code}
> And running psql.py I get this:
> {code}
> psql.py -t DUMMY localhost:2181:/hbase-unsecure DummyValues.csv
> 14/09/22 16:31:02 ERROR util.CSVCommonsLoader: Error upserting record [2, ]:
> CHAR may not be null
> CSV Upsert complete. 2 rows upserted
> Time: 0.052 sec(s)
> {code}
> In sqlline I can insert nulls just fine into column y.
> Didn't check to see if this affects other types, e.g. varchar.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
