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

YUBI LEE edited comment on IMPALA-10408 at 9/13/22 3:35 AM:
------------------------------------------------------------

I made a PR related to it.
https://github.com/apache/impala/pull/34
https://gerrit.cloudera.org/#/c/18975/

If this PR is not valid you think, please tell me I will make a separate jira 
issue.


was (Author: eub):
I made a PR related to it.
https://github.com/apache/impala/pull/34
https://gerrit.cloudera.org/#/c/18966/

If this PR is not valid you think, please tell me I will make a separate jira 
issue.

> Build against Apache official versions
> --------------------------------------
>
>                 Key: IMPALA-10408
>                 URL: https://issues.apache.org/jira/browse/IMPALA-10408
>             Project: IMPALA
>          Issue Type: New Feature
>          Components: Infrastructure
>            Reporter: Quanlong Huang
>            Priority: Major
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Currently, we are building against CDH/CDP components of Hadoop, Hive, HBase, 
> Tez, Ranger, Sentry etc. The main reason is we need some bug fixes or new 
> features that haven't been released in Apache official versions. Depending on 
> CDH/CDP versions help us evolve faster.
> However, building against Apache official releases can increase Impala's 
> adoption on non CDH/CDP users. For released versions like 3.4.0, we can try 
> to find/release compatible Apache official versions for the dependencies.
> This would require significant works so we need to make it step by step. 
> There are some discussions in this email thread:
>  
> [https://lists.apache.org/thread.html/r7bee90b9f0b7c5038798562b2e6340f41d21426cfb8c7978b9ba4842%40%3Cdev.impala.apache.org%3E]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to