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

Tajo QA commented on TAJO-1815:
-------------------------------

{color:red}*-1 overall.*{color}  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12754205/TAJO-1815.patch
  against master revision release-0.9.0-rc0-443-g7e0a4a1.

    {color:green}+1 @author.{color}  The patch does not contain any @author 
tags.

    {color:red}-1 tests included.{color}  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {color:green}+1 javac.{color}  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc.{color}  The applied patch does not increase the 
total number of javadoc warnings.

    {color:green}+1 checkstyle.{color}  The patch generated 0 code style errors.

    {color:red}-1 findbugs.{color}  The patch appears to introduce 8 new 
Findbugs (version 2.0.3) warnings.

    {color:green}+1 release audit.{color}  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests.{color}  The patch passed unit tests in 
tajo-catalog/tajo-catalog-server.

Test results: 
https://builds.apache.org/job/PreCommit-TAJO-Build/853//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-TAJO-Build/853//artifact/incubator-tajo/patchprocess/newPatchFindbugsWarningstajo-catalog-server.html
Console output: https://builds.apache.org/job/PreCommit-TAJO-Build/853//console

This message is automatically generated.

> Catalog store initialization with PostgreSQL failed
> ---------------------------------------------------
>
>                 Key: TAJO-1815
>                 URL: https://issues.apache.org/jira/browse/TAJO-1815
>             Project: Tajo
>          Issue Type: Bug
>          Components: Catalog
>    Affects Versions: 0.10.1
>         Environment: PostgreSQL 9.4
>            Reporter: Jongyoung Park
>            Assignee: Jongyoung Park
>            Priority: Minor
>         Attachments: TAJO-1815.patch
>
>
> According to a document on Tajo website, PostgreSQL catalog store is set, but 
> initialization failed like following:
> {quote}
> 2015-09-04 22:20:09,977 WARN 
> org.apache.tajo.catalog.store.XMLCatalogSchemaManager: Failed to drop 
> database objects TABLE INDEXES,TABLE STATS,TABLE PARTITION_METHODS,TABLE 
> PARTITIONS,TABLE PARTITION_KEYS
> 2015-09-04 22:20:09,978 ERROR org.apache.tajo.catalog.CatalogServer: 
> CatalogServer initialization failed
> java.lang.reflect.InvocationTargetException
>   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>   at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>   at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
>   at org.apache.tajo.catalog.CatalogServer.serviceInit(CatalogServer.java:129)
>   at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
>   at 
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
>   at org.apache.tajo.master.TajoMaster.serviceInit(TajoMaster.java:213)
>   at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
>   at org.apache.tajo.master.TajoMaster.main(TajoMaster.java:561)
> Caused by: org.apache.tajo.exception.TajoInternalError: internal error: 
> internal error: ERROR: multiple primary keys for table "indexes" are not 
> allowed
>   Position: 586
>   at 
> org.apache.tajo.catalog.store.AbstractDBStore.<init>(AbstractDBStore.java:187)
>   at 
> org.apache.tajo.catalog.store.PostgreSQLStore.<init>(PostgreSQLStore.java:32)
>   ... 10 more
> {quote}



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

Reply via email to