[ 
https://issues.apache.org/jira/browse/TAJO-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708319#comment-14708319
 ] 

Jihoon Son commented on TAJO-1798:
----------------------------------

Thanks for asking me. I've forgot it.
Here is the log.
{noformat}
2015-08-23 13:44:11,170 INFO org.apache.tajo.querymaster.Query: Processing 
q_1440304970100_0001 of type QUERY_COMPLETED
2015-08-23 13:44:11,170 INFO org.apache.tajo.worker.TaskManager: Stopped 
execution block:eb_1440304970100_0001_000002
2015-08-23 13:44:11,183 INFO org.apache.tajo.storage.FileTablespace: Moved from 
the staging dir to the output directory 
'hdfs://localhost:7020/tajo/warehouse/tpch1/partitioned_lineitem
2015-08-23 13:44:11,376 FATAL org.apache.hadoop.yarn.event.AsyncDispatcher: 
Error in dispatcher thread
org.apache.tajo.exception.TajoInternalError: internal error: The statement was 
aborted because it would have caused a duplicate key value in a unique or 
primary key constraint or unique index identified by 'C_PARTITIONS_UNIQ' 
defined on 'PARTITIONS'.
        at 
org.apache.tajo.exception.ExceptionUtil.toTajoExceptionCommon(ExceptionUtil.java:124)
        at 
org.apache.tajo.exception.ExceptionUtil.toTajoException(ExceptionUtil.java:151)
        at 
org.apache.tajo.exception.ExceptionUtil.throwsIfThisError(ExceptionUtil.java:103)
        at 
org.apache.tajo.catalog.AbstractCatalogClient.addPartitions(AbstractCatalogClient.java:483)
        at 
org.apache.tajo.querymaster.Query$QueryCompletedTransition.finalizeQuery(Query.java:526)
        at 
org.apache.tajo.querymaster.Query$QueryCompletedTransition.transition(Query.java:447)
        at 
org.apache.tajo.querymaster.Query$QueryCompletedTransition.transition(Query.java:436)
        at 
org.apache.hadoop.yarn.state.StateMachineFactory$MultipleInternalArc.doTransition(StateMachineFactory.java:385)
        at 
org.apache.hadoop.yarn.state.StateMachineFactory.doTransition(StateMachineFactory.java:302)
        at 
org.apache.hadoop.yarn.state.StateMachineFactory.access$300(StateMachineFactory.java:46)
        at 
org.apache.hadoop.yarn.state.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:448)
        at org.apache.tajo.querymaster.Query.handle(Query.java:860)
        at org.apache.tajo.querymaster.Query.handle(Query.java:67)
        at 
org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:173)
        at 
org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:106)
        at java.lang.Thread.run(Thread.java:745)
{noformat}

> Query execution is not finished even though it actually is done.
> ----------------------------------------------------------------
>
>                 Key: TAJO-1798
>                 URL: https://issues.apache.org/jira/browse/TAJO-1798
>             Project: Tajo
>          Issue Type: Bug
>            Reporter: Jihoon Son
>             Fix For: 0.11.0
>
>
> The following query runs continuously even though the progress is reached to 
> 100%.
> {noformat}
> tpch1> create table partitioned_lineitem (l_orderkey int8, l_partkey int8, 
> l_suppkey int8, l_linenumber int8, l_quantity float8, l_extendedprice float8, 
> l_discount float8, l_tax float8, l_linestatus text, l_shipdate text, 
> l_commitdate text, l_receiptdate text, l_shipinstruct text, l_shipmode text, 
> l_comment text) partition by column (l_returnflag text) as select l_orderkey, 
> l_partkey, l_suppkey, l_linenumber , l_quantity , l_extendedprice , 
> l_discount , l_tax , l_linestatus , l_shipdate , l_commitdate , l_receiptdate 
> , l_shipinstruct , l_shipmode , l_comment, l_returnflag from lineitem;
> ...
> Progress: 100%, response time: 328.515 sec
> Progress: 100%, response time: 329.517 sec
> Progress: 100%, response time: 330.524 sec
> Progress: 100%, response time: 331.527 sec
> Progress: 100%, response time: 332.529 sec
> ...
> {noformat}
> When I check the query status through the web UI, its all stages are already 
> completed with 'SUCCEEDED' state. So, I killed the running query. However, 
> surprisingly, I found that the result table of the above query is 
> successfully registered in catalog as follows.
> {noformat}
> tpch1> \d
> customer
> lineitem
> nation
> orders
> partitioned_lineitem
> partitioned_nation
> partitioned_region
> partsupp
> region
> supplier
> tpch1> \d partitioned_lineitem
> table name: tpch1.partitioned_lineitem
> table uri: hdfs://localhost:7020/tajo/warehouse/tpch1/partitioned_lineitem
> store type: TEXT
> number of rows: 6001215
> volume: 750.5 MB
> Options: 
>       'text.delimiter'='|'
> schema: 
> l_orderkey    INT8
> l_partkey     INT8
> l_suppkey     INT8
> l_linenumber  INT8
> l_quantity    FLOAT8
> l_extendedprice       FLOAT8
> l_discount    FLOAT8
> l_tax FLOAT8
> l_linestatus  TEXT
> l_shipdate    TEXT
> l_commitdate  TEXT
> l_receiptdate TEXT
> l_shipinstruct        TEXT
> l_shipmode    TEXT
> l_comment     TEXT
> Partitions: 
> type:COLUMN
> columns::l_returnflag (TEXT)
> tpch1> select count(*) from partitioned_lineitem;
> Progress: 6%, response time: 1.164 sec
> Progress: 6%, response time: 1.165 sec
> Progress: 6%, response time: 1.568 sec
> Progress: 100%, response time: 1.793 sec
> ?count
> -------------------------------
> 6001215
> (1 rows, 1.793 sec, 8 B selected)
> {noformat}



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

Reply via email to