Hyper input - Field ... was truncated
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hello
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
Rodrigo
Solved! Go to Solution.
- Labels:
- Input
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
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)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
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.
Thanks in advance
Pls keep me posted when that limitation is fixed 😉
Greetings
Santosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
This is also a blocker for us using Hyper files for Input, we regularly have description fields that are >255 characters.
Jonathan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Other than this issue hyper file format would be greatly preferred over e.g. yxdb due to minimized storage requirements.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Has this been fixed in later versions? If so, which version?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hi, I just tested this on v2021.3.4 and the issue has been fixed, I don't have any prior releases to test against.
Jonathan
- « Previous
-
- 1
- 2
- Next »