[
https://issues.apache.org/jira/browse/HAWQ-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15489516#comment-15489516
]
hongwu commented on HAWQ-1046:
------------------------------
I will take care of this issue. I have recommended [~wangzw] to create another
repo in github for the consideration of current libhdfs3 users from community.
Then we should update README.md to give the link of the new repo. After several
days(maybe 10-20days?), we will make the repo under Pivotal-Data-Attic private
and old users may refer to the new link for development which has no
relationship with Pivotal.
For the future development of libhdfs3, I think we'd better develop in
Pivotal-Data-Attic/pivotalrd-libhdfs3 as upstream since it is a dependent
library(not only HAWQ can use it, but also other projects, we plan to
contribute it to apache in the future). For HAWQ, we periodically sync with
upstream repo's releases or commits.
Make sense?
> Document migration of LibHDFS3 library to HAWQ
> ----------------------------------------------
>
> Key: HAWQ-1046
> URL: https://issues.apache.org/jira/browse/HAWQ-1046
> Project: Apache HAWQ
> Issue Type: Wish
> Components: libhdfs
> Reporter: Matthew Rocklin
> Assignee: hongwu
>
> Some people used to depend on the libhdfs3 library maintained alongside HAWQ.
> This library was merged into the HAWQ codebase, making the situation a bit
> more confusing.
> Is independent use of libhdfs3 still supported by this community? If so what
> is the best way for packagers to reason about versions and releases of this
> component? It would be convenient to see documentation on how people can
> best depend on libhdfs3 separately from HAWQ if this is an intention.
> It looks like people have actually submitted work to the old version
> See: https://github.com/Pivotal-Data-Attic/pivotalrd-libhdfs3/pull/28
> It looks like the warning that the library had moved has been removed:
> https://github.com/Pivotal-Data-Attic/pivotalrd-libhdfs3/commit/ddcb2404a5a67e0f39fe49ed20591545c48ff426
> This removal may lead to some frustration
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
