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-374) Enable access to dynamic columns in * or cf.* selection
Date Tue, 05 Feb 2019 07:10:00 GMT

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

Hadoop QA commented on PHOENIX-374:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12957574/PHOENIX-374.patch
  against master branch at commit 3cb1d322b9fe256f2c6bd3c060b9df43f2485721.
  ATTACHMENT ID: 12957574

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

    {color:green}+1 tests included{color}.  The patch appears to include 3 new or modified
tests.

    {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 1 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.index.MutableIndexSplitReverseScanIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.SpillableGroupByIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.ConcurrentMutationsIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.MutableIndexSplitForwardScanIT

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

This message is automatically generated.

> Enable access to dynamic columns in * or cf.* selection
> -------------------------------------------------------
>
>                 Key: PHOENIX-374
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-374
>             Project: Phoenix
>          Issue Type: New Feature
>            Reporter: nicolas maillard
>            Assignee: Chinmay Kulkarni
>            Priority: Critical
>         Attachments: PHOENIX-374.patch
>
>          Time Spent: 3h 40m
>  Remaining Estimate: 0h
>
> As of recent work we can now read and write columns that are not in the schema, AKA dynamic
columns. the Select and Upsert allow dynamic columns to be specified. 
> I think two additions are still needed.
> - Alter dynamicly: In the Upsert and/or Select statement  the ability to add on the specified
dynamic column to schema. Say Upsert into Table (key, cf.dynColumn varchar SCHEMAADD) values
(..)
> and for select: 
>      - select key, cf.dynColumn varchar from T would only read
>      - select key from T(cf.dynColumn varchar ) would only read and wrtie to schema
> - Select a complete column Family: More complex, accessing a whole Column Family with
all rows known in schema or not.
>  select cf.* from T
> today this works for know columns it could be nice to have this for all columns of a
family in the schema or not. I'm trying right now to extend this to schema for unknown columns.
However every new row can a lot of very different unknowcolumns. The defined ones will be
first but the unknown one will be appended at the end.
> This means the metadata might need to be updated at every row to account for all new
columns discovered.



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

Mime
View raw message