That is an interesting behavior that is occurring with Extract API. What flavor of Linux are you using?
This is on an EMR cluster in AWS, which is based on CentOS 7 (but then Amazon-ified).
I've had to resort to running this on Windows for now due to this problem (and the problem of single character column names), but will keep trying to resolve this on that AWS system.
My latest suspicion is it might be to do with port access permissions, where Linux does not allow non-root users to bind to ports below 1024 - I'd seen another a couple of forum posts here where users got this to work running as root. Do you know the port number used by the extract API - that may help in the diagnosis?
Sorry for the delay in my reply. I do not know the ports that the extact API uses off the top of my head.
Let me dig a little and see what I can find.
Have you had any luck with this? I'm currently having the same issue running the python version of the Extract API 2.0.
I attempt to create an Extract object, passing a file path which I know exists and that the current process has permission to write to, and receive the following error :
TableauException (40200): Hyper Server did not call back on the callback port: process = 2501
I suspect that I need to open a specific port so that the tableau server can communicate with my machine during the extract creation but I don't know which port this would be and don't see any related info in the documentation. Any advice would be much appreciated !
On the off chance that this helps anyone with the same issue, the library had a dependency, libtinfo.so.5, which wasn't installed on the machine I was working with. Installing the package fixed the problem.