[
https://issues.apache.org/jira/browse/HAWQ-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15490453#comment-15490453
]
Matthew Rocklin commented on HAWQ-1046:
---------------------------------------
Separating libhdfs3 into a separate repository with occasional updates of the
copied version within HAWQ sounds great to me.
I agree you should avoid the term "attic". It does mean "private space" as
[~wangzw] pointed out and also "space for unused things" or "long term storage".
> 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)
