Colin Marc

Hi @urykhy, thanks for the huge contribution! I am interested in supporting this feature, but I lack the context to understand if the implementation is correct. If you're willing to...

Thanks for sticking with this!

Hi @yuchengwu, thanks for the bug report. What hadoop distro and version are you running? Can you look in the namenode logs and see what the error is there?

Thanks for figuring this out! This is definitely a bug.

Fixed in 1dee011.

Hi @kimtree, thanks for the suggestion. I think this may be the simplest way to solve the problem, but I've also been considering adding `context` support for some methods, eg...

Exactly. I would change the signature of `Execute` to take a context.

Currently my thinking would be to add `RenameContext` etc for a point release, and then change the old `Rename` etc for a 3.0 release. I'm not working on context support...

> This way of using `context` is not complete since `client.Open` function is out of control. Thus, our problem occurs when executing `c.namenode.Execute` from `client.Open` function. Are you going to...

> The reason why I specified read/write timeout especially for the datanode is to handle failure from the namenode, not lazily loaded Read or the action afterward. Hm, maybe `Open`...