[jira] [Updated] (HAWQ-1046) Document migration of LibHDFS3 library to HAWQ
[ https://issues.apache.org/jira/browse/HAWQ-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Goden Yao updated HAWQ-1046: Fix Version/s: backlog > 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 > Fix For: backlog > > > 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)
[jira] [Updated] (HAWQ-1046) Document migration of LibHDFS3 library to HAWQ
[ https://issues.apache.org/jira/browse/HAWQ-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ed Espino updated HAWQ-1046: Assignee: hongwu (was: Ruilong Huo) > 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)
[jira] [Updated] (HAWQ-1046) Document migration of LibHDFS3 library to HAWQ
[ https://issues.apache.org/jira/browse/HAWQ-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ed Espino updated HAWQ-1046: Assignee: Ruilong Huo (was: Ed Espino) > 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: Ruilong Huo > > 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)
