phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-5209) Cannot add non-PK column to table when the last PK column is of type VARBINARY or ARRAY
Date Fri, 14 Jun 2019 09:19:00 GMT

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

Hadoop QA commented on PHOENIX-5209:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12971763/PHOENIX-5209.4.x-HBase-1.4.v2.patch
  against 4.x-HBase-1.4 branch at commit 5bf49e62601e7d241eb0f649b78253708b1ee42d.
  ATTACHMENT ID: 12971763

    {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:red}-1 release audit{color}.  The applied patch generated 2 release audit warnings
(more than the master's current 0 warnings).

    {color:green}+1 lineLengths{color}.  The patch does not introduce lines longer than 100

     {color:red}-1 core tests{color}.  The patch failed these unit tests:
     ./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.ViewIT

Test results: https://builds.apache.org/job/PreCommit-PHOENIX-Build/2674//testReport/
Release audit warnings: https://builds.apache.org/job/PreCommit-PHOENIX-Build/2674//artifact/patchprocess/patchReleaseAuditWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-PHOENIX-Build/2674//console

This message is automatically generated.

> Cannot add non-PK column to table when the last PK column is of type VARBINARY or ARRAY
> ---------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-5209
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5209
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Toshihiro Suzuki
>            Assignee: Toshihiro Suzuki
>            Priority: Major
>         Attachments: PHOENIX-5209.4.x-HBase-1.3.v1.patch, PHOENIX-5209.4.x-HBase-1.4.v1.patch,
PHOENIX-5209.4.x-HBase-1.4.v2.patch, PHOENIX-5209.4.x-HBase-1.5.v1.patch, PHOENIX-5209.4.x-HBase-1.5.v2.patch,
PHOENIX-5209.master.v1.patch, PHOENIX-5209.master.v2.patch
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Let's see we have the following table:
> {code}
> CREATE TABLE tbl (id VARBINARY PRIMARY KEY, col1 INTEGER)
> {code}
> The type of the primary key of this table is VARBINARY.
> And when we alter this table to add a new column:
> {code}
> ALTER TABLE tbl ADD col2 INTEGER
> {code}
> we are facing the following error:
> {code}
> java.sql.SQLException: ERROR 1015 (42J04): Cannot add column to table when the last PK
column is of type VARBINARY or ARRAY. columnName=ID
> {code}
> I think we should be able to do it without the above error because we don't try to add
a PK column.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message