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

Hudson commented on PHOENIX-4737:
---------------------------------

ABORTED: Integrated in Jenkins build Phoenix-4.x-HBase-1.3 #133 (See 
[https://builds.apache.org/job/Phoenix-4.x-HBase-1.3/133/])
PHOENIX-4737 Use position as column qualifier for APPEND_ONLY_SCHEMA (jtaylor: 
rev a72aad3369789129196cf180da7e757a71034fcb)
* (edit) 
phoenix-core/src/it/java/org/apache/phoenix/end2end/ColumnEncodedBytesPropIT.java
* (edit) 
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/MetaDataEndpointImpl.java
* (edit) 
phoenix-core/src/main/java/org/apache/phoenix/schema/MetaDataClient.java


> Use position as column qualifier for APPEND_ONLY_SCHEMA
> -------------------------------------------------------
>
>                 Key: PHOENIX-4737
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4737
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: James Taylor
>            Assignee: James Taylor
>            Priority: Major
>             Fix For: 4.14.0, 5.0.0
>
>         Attachments: PHOENIX-4737_v1.patch
>
>
> An easy way to prevent gaps in the column encoding used to define column 
> qualifiers is to use the position to define the column qualifier. This only 
> works if:
>  * You disallow removes of columns
>  * You disallow adding columns to the base table
> This is pretty easy to enforce and will enable column encoding to be used 
> effectively when a base table has many views.



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

Reply via email to