Treasure Data's primary idea portal. 

Submit your ideas & feature requests directly to our product requirements team! We look forward to hearing from you.

Import data as String instead of skipping the record

Sometimes, the users have 3rd-party data with inconsistencies and our guess command doesn't capture those scenarios and ends up skipping events. The customers feel that TD shouldn't reject any data point at all and that if a field has consistent data then it should be brought in as String automatically. Right now, we have to change each column's type manually. I'm not sure what logic needs to be implemented to handle such auto-string situations. Maybe set a global flag to bring all fields as String: --all-string (reference:

  • Prakhar Agarwal
  • Sep 13 2016
  • Under Review