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

Goden Yao updated HAWQ-206:
---------------------------
    Description: 
As a HAWQ user, I should be able to:
not type delimiter twice in DDL in the case of using HiveRC/Text profile via PXF

*Background*
Currently user has to specify the same delimiter twice in DDL(in the case of 
HiveRC/Text profiles):
{code}
...
location(E'pxf://...&delimiter=\x01') FORMAT TEXT (delimiter = E'\x01');
{code}
It would be really helpful if we could use the delimiter provided in TEXT this 
would reduce error prone DDL grammar and duplication.


  was:
As a HAWQ user, I should be able to:
not type delimiter twice in DDL in the case of using HiveRC/Text profile via PXF

*Background*
Currently user has to specify the same delimiter twice in DDL(in the case of 
HiveRC/Text profiles):
{code}
...
location(E'pxf://...&delimtier=\x01') FORMAT TEXT (delimiter = E'\x01');
{code}
It would be really helpful if we could use the delimiter provided in TEXT this 
would reduce error prone DDL grammar and duplication.



> Use the DELIMITER in FORMAT for External Table DDL Creation
> -----------------------------------------------------------
>
>                 Key: HAWQ-206
>                 URL: https://issues.apache.org/jira/browse/HAWQ-206
>             Project: Apache HAWQ
>          Issue Type: Improvement
>          Components: PXF
>            Reporter: Goden Yao
>            Assignee: Goden Yao
>
> As a HAWQ user, I should be able to:
> not type delimiter twice in DDL in the case of using HiveRC/Text profile via 
> PXF
> *Background*
> Currently user has to specify the same delimiter twice in DDL(in the case of 
> HiveRC/Text profiles):
> {code}
> ...
> location(E'pxf://...&delimiter=\x01') FORMAT TEXT (delimiter = E'\x01');
> {code}
> It would be really helpful if we could use the delimiter provided in TEXT 
> this would reduce error prone DDL grammar and duplication.



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

Reply via email to