This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
I am using the new option to use hyper file in the input tool. Most of the times when I do this I get that some fields in the hyper file are being truncated at the input tool step.
Is there a way to go around this? Is this a bug?
Note the hyper file that I am using as input was created by Alteryx in another workflow.
Thanks in advance
Thanks for the feedback. We agree with you! The way it will likely work is that the user will be able to specify the length of the string field. No confirmation of timing yet.
My team just encountered this issue when attempting to ingest a field from Hive with >255 chars. It is constantly being trimmed down to V_String(255)
I have the same issue and can verify all previous comments.
Field size should definitely not be limited for the read in tool concerning hyper files.
Just copy paste the functioanlity similarly to the .csv read in. --> user can select maximum field size before each run.
Pls keep me posted when that limitation is fixed 😉
This is also a blocker for us using Hyper files for Input, we regularly have description fields that are >255 characters.
Other than this issue hyper file format would be greatly preferred over e.g. yxdb due to minimized storage requirements.