The scenario is 1. user creates an external writable table, 2. copy data into that external writable table. 3. query that external writable table (by creating another readable table)
I think user doesn't copy to internal tables due to some possible reasons: the format is not supported by hawq internal tables (in JIRA , it was a text file) As for https://issues.apache.org/jira/browse/HAWQ-956 , I put milestone as backlog and welcome further discussion. On Thu, Jul 28, 2016 at 2:22 AM Lili Ma <[email protected]> wrote: > Hi Alex, > > Could you kindly share the user scenario for copying data to external > table? Why don't we copy to internal table directly? Thanks :) I thought > external table can directly points to the file which we need copy when > created. > > Thanks > Lili > > 2016-07-28 6:53 GMT+08:00 Oleksandr Diachenko <[email protected]>: > > > Hi, > > > > Recently we discovered that COPY command for external tables is not > > transactional. > > It means if user is running COPY command and during this process > underlying > > HDFS fails - the end state of table is inconstant. > > As a result I filled a JIRA - > > https://issues.apache.org/jira/browse/HAWQ-956 > > . > > > > From user perspective, COPY command might also need to support additional > > options, to make import/export process more flexible. > > > > - Number of error lines to tolerate. > > - Batch size to commit. > > - TBD > > > > Please feel free to join discussion. > > > > Regards, Alex. > > >
