You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Richard Antal (Jira)" <ji...@apache.org> on 2020/06/11 15:47:00 UTC
[jira] [Commented] (PHOENIX-5900) Bulk load a csv file into a
phoenix table created in lowercase fails
[ https://issues.apache.org/jira/browse/PHOENIX-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17133354#comment-17133354 ]
Richard Antal commented on PHOENIX-5900:
----------------------------------------
What version of Phoenix did you use?
I tried to do it on the master branch but I did not manage to reproduce this issue.
> Bulk load a csv file into a phoenix table created in lowercase fails
> ---------------------------------------------------------------------
>
> Key: PHOENIX-5900
> URL: https://issues.apache.org/jira/browse/PHOENIX-5900
> Project: Phoenix
> Issue Type: Bug
> Reporter: Mich Talebzadeh
> Priority: Major
>
> I have a phoenix table *created in lowercase* as follows:
>
> CREATE TABLE "MICHTEST"."StagingNotificationPreferencesRT"
> (
> ROWKEY VARCHAR NOT NULL PRIMARY KEY
> , "cf"."partyId" VARCHAR
> , "cf"."childNotificationId" VARCHAR
> , "cf"."brand" VARCHAR
> , "cf"."accountReference" VARCHAR
> , "cf"."expiredDate" VARCHAR
> , "cf"."parentNotificationId" VARCHAR
> ...
>
> This table creates OK. When I try to bulk load from a csv file at Linux bash command line as follows
>
> *psql -t MICHTEST."StagingNotificationPreferencesRT" ./StagingNotificationPreferences.csv -s*
> 20/05/11 21:35:07 ERROR util.CSVCommonsLoader: Error upserting record [3c7953b3-0c69-42ee-9abf-fe7a77d29c87, 876543914, 1, LTB, , , 50, 76543210, , 2017-13-18 18:29:23:345, 19, 1, , , , , , , 9876543210123456]
> java.lang.RuntimeException: org.apache.phoenix.schema.TableNotFoundException: ERROR 1012 (42M03): Table undefined. tableName=MICHTEST.STAGINGNOTIFICATIONPREFERENCESRT
>
> Note that the table name shown in error is uppercase! Now this works if I go back and create table all in UPPERCASE!
>
> This seems to be a Phoenix bug similar to below as I have been advised
>
> https://issues.apache.org/jira/browse/PHOENIX-3541
> https://issues.apache.org/jira/browse/PHOENIX-5319
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)