Great. I will file a patch to move the check to the constructor and fail back to old process if the method is missing.
For our case, I just implemented getFileLength and all is happy (on that front) On Fri, Jan 7, 2011 at 12:38 PM, Stack <[email protected]> wrote: > Let me open an issue to add more checks around the reflection; e.g. > check type as you fellas suggest. If anything is not as expected, > then we'd fallback on old getPos behavior. It should not fail for > 'pure' HDFS. 'Alternative' HDFS's probably don't have this 2G > problem. >
