[
https://issues.apache.org/jira/browse/PHOENIX-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14263959#comment-14263959
]
Gabriel Reid commented on PHOENIX-1277:
---------------------------------------
[~jamestaylor] - just want to quickly ping you on this one. Is there any reason
why PDataType.CHAR needs to guard against null? As listed above, CHAR fields
are always nullable, so I'm wondering if there's another reason for there being
a guard against it in PDataType.CHAR.
> 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)
