Anything further in the UNICODE plane crashes the Extract API.
And the crashes happen in ToTableauString method
This happens with
CPP samples seem to handle all UNICODE characters as far as i can tell from the tests i ran, so im wondering what is wrong with the Java API.
Tested extract api version is hyperextractapi-cpp-linux-gcc-x86_64-release_2019_2.2019.2.2.189.r7796868f
When looking WHY the c++ solution is actually working i see in TableauHyperExtract_cpp.h the usage of MakeTableauString(value.c_str()) where the std_wstring#c_str is (strangely) used yet this results in unicode getting to the extract correctly (judging after seeing the data in TableauServer).
TAB_RESULT result = TabRowSetString(m_handle
if ( result != TAB_RESULT_Success )
throw TableauException( result, TabGetLastErrorMessage() );
So could a developer answer these questions:
- is whole UNICODE set supported in extract API ?
- could you fix the Java API to not crash JVM in com.tableausoftware.common.StringUtils#ToTableauString as the C++ samples seems to be able to what we're trying to do via the JAVA api ?