phoenix-dev 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-4441) Reflect changes that were made recently in HBase branch-2
Date Thu, 07 Dec 2017 09:05:00 GMT

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

Hadoop QA commented on PHOENIX-4441:
------------------------------------

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

    {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:red}-1 patch{color}.  The patch command could not apply the patch.

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

This message is automatically generated.

> Reflect changes that were made recently in HBase branch-2 
> ----------------------------------------------------------
>
>                 Key: PHOENIX-4441
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4441
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Sergey Soldatov
>            Assignee: Sergey Soldatov
>              Labels: HBase-2.0
>             Fix For: 5.0.0
>
>         Attachments: PHOENIX-4441.patch
>
>
> There were several changes that break our build:
> HBASE-19417. Changed method signature in RegionObserver
> HBASE-19430. Removed setTimestamp(byte[], int)  method from ExtendedCell.
> Also, there is another problem - configuration on coprocessor env is now read-only, so
we need to find out a way to set index failure policy for index coprocessor. Will cover in
a separate jira. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message