[ 
https://issues.apache.org/jira/browse/HADOOP-18039?focusedWorklogId=692792&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-692792
 ]

ASF GitHub Bot logged work on HADOOP-18039:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 08/Dec/21 18:42
            Start Date: 08/Dec/21 18:42
    Worklog Time Spent: 10m 
      Work Description: virajjasani commented on a change in pull request #3768:
URL: https://github.com/apache/hadoop/pull/3768#discussion_r765137142



##########
File path: hadoop-project/pom.xml
##########
@@ -2428,9 +2428,10 @@
       </activation>
       <properties>
         <hbase.version>${hbase.two.version}</hbase.version>
-        
<hbase-compatible-hadoop.version>3.0.0</hbase-compatible-hadoop.version>
+        
<hbase-compatible-hadoop.version>2.8.5</hbase-compatible-hadoop.version>

Review comment:
       Valid question. The earlier hbase version 2.0 is not only not so stable 
but also it just worked with Hadoop 3 version magically but as we upgrade HBase 
2.x versions, they won't work by default with Hadoop 3 because as of today, 
hbase has only published hadoop 2 compatible hbase 2 artifacts by default. If 
we want to make hbase 2 work with hadoop 3, first we need to compile hbase 2 
with hadoop-3.0 profile, only then we get hadoop 3 compatible hbase 2 jars. 
Hence, we should have anyways kept `hbase-compatible-hadoop.version` on 
Hadoop's 2.x release line but somehow we didn't and this worked with HBase 2.0.
   
   I have provided detailed explanation of this also on HADOOP-17668. Comment 
[here](https://issues.apache.org/jira/browse/HADOOP-17668?focusedCommentId=17454172&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17454172)
 (hope I covered the right link, Jira interface seems to have been updated 
recently)
   
   And yes @jojochuang's review would also be great, thanks for the reminder 
(my bad, I missed).




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 692792)
    Time Spent: 50m  (was: 40m)

> Upgrade hbase2 version and fix TestTimelineWriterHBaseDown
> ----------------------------------------------------------
>
>                 Key: HADOOP-18039
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18039
>             Project: Hadoop Common
>          Issue Type: Sub-task
>            Reporter: Viraj Jasani
>            Assignee: Viraj Jasani
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> As mentioned on the parent Jira, we can't upgrade hbase2 profile version 
> beyond 2.2.4 until we either have hbase 2 artifacts available that are built 
> with hadoop 3 profile by default or hbase 3 is rolled out (hbase 3 is 
> compatible with hadoop 3 versions only).
> Let's upgrade hbase2 profile version to 2.2.4 as part of this Jira and also 
> fix TestTimelineWriterHBaseDown to create connection only after mini cluster 
> is up.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to