You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2019/05/24 22:25:00 UTC

[jira] [Commented] (PHOENIX-5301) Doc: Fix incorrect DDL and DML (In ARRAY Type page)

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

Hadoop QA commented on PHOENIX-5301:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org
  against master branch at commit fffd21aea72ec47a36adcb7d3ba778a15fd7dc10.
  ATTACHMENT ID: http:

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

    {color:green}+0 tests included{color}.  The patch appears to be a documentation, build,
                        or dev patch that doesn't require tests.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-PHOENIX-Build/2600//console

This message is automatically generated.

> Doc: Fix incorrect DDL and DML (In ARRAY Type page)
> ---------------------------------------------------
>
>                 Key: PHOENIX-5301
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5301
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 5.0.0
>            Reporter: Karthik Palanisamy
>            Assignee: Karthik Palanisamy
>            Priority: Minor
>         Attachments: array_type.md
>
>
> 1. Remove multipart PRIMARY KEY constraint since this pk is defined already. 
> CREATE TABLE regions ( region_name VARCHAR PRIMARY KEY, zips VARCHAR ARRAY[10], CONSTRAINT pk PRIMARY KEY (region_name));
> Error: ERROR 510 (42889): The table already has a primary key. columnName=REGION_NAME (state=42889,code=510)
> java.sql.SQLException: ERROR 510 (42889): The table already has a primary key. columnName=REGION_NAME
>  
>  
> 2.  DML failed because undefined column "zip" is used.  Use "zips", instead.
> SELECT zip[1] FROM regions WHERE region_name = 'SF Bay Area';
> SELECT region_name FROM regions WHERE zip[1] = '94030' OR zip[2] = '94030' OR zip[3] = '94030';
> ..
> Error: ERROR 504 (42703): Undefined column. columnName=REGIONS.ZIP (state=42703,code=504)
> org.apache.phoenix.schema.ColumnNotFoundException: ERROR 504 (42703): Undefined column. columnName=REGIONS.ZIP



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