Github user interma commented on the issue:
https://github.com/apache/incubator-hawq/pull/1376
@superbobry
As I known, no/not many person declare that they depend on libhdfs3. In the
past, they just make a copy into their repo if need it (not a good things, but
understandable,
Github user linwen commented on a diff in the pull request:
https://github.com/apache/incubator-hawq/pull/1377#discussion_r196996343
--- Diff: depends/libhdfs3/src/rpc/RpcChannel.cpp ---
@@ -768,7 +771,15 @@ void RpcChannelImpl::readOneResponse(bool writeLock) {
[
https://issues.apache.org/jira/browse/HAWQ-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16518816#comment-16518816
]
Hongxu Ma commented on HAWQ-1627:
-
User can set this value in _etc/hdfs-client.xml_:
{code}
[
https://issues.apache.org/jira/browse/HAWQ-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16518816#comment-16518816
]
Hongxu Ma edited comment on HAWQ-1627 at 6/21/18 2:32 AM:
--
User can set this
GitHub user interma opened a pull request:
https://github.com/apache/incubator-hawq/pull/1377
HAWQ-1627. Support setting the max protocol message size when talking
with HDFS
**Fix what?**
User can set the max protocol message size, e.g.
In _etc/hdfs-client.xml_:
Github user superbobry commented on the issue:
https://github.com/apache/incubator-hawq/pull/1376
Hi @interma, thank you for the review.
Regarding hdfsFlush: what I meant was how to proceed with making its
behaviour compatible with libhdfs, i.e. removing the H part from the
