You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I came across a very unfortunate problem using this library.
Whenever I try to read a parquet file created with this same tool and containing a comma , in any of its headers.
I get this error while await parquetReader.getCursor().next(): TypeError: Cannot read property 'fields' of undefined
stacktrace:
at ParquetSchema.findField (../../.yarn/cache/parquetjs-npm-0.11.2-9df3a54481-63137e17bc.zip/node_modules/parquetjs/lib/schema.js:35:22)
at Object.exports.materializeRecords (../../.yarn/cache/parquetjs-npm-0.11.2-9df3a54481-63137e17bc.zip/node_modules/parquetjs/lib/shred.js:164:26)
at ParquetCursor.next (../../.yarn/cache/parquetjs-npm-0.11.2-9df3a54481-63137e17bc.zip/node_modules/parquetjs/lib/reader.js:62:40)
I guess this is caused by a rather "unsafe" operation in the parquetjs/lib/schema.js file on line 28: path.split(",")
I would be very helpful for any help with this problem.
Thank you
The text was updated successfully, but these errors were encountered:
bartero
changed the title
Cannot write a parquet file having a header name containing a comma
Cannot write a parquet file having a comma in one of its headers
Oct 9, 2020
I have prepared solution of this problem here: ironSource#118.
Please have a look! :-)
I am not sure what is the relation between the ZJONSSON/parquetjs <-> ironSource/parquetjs.
I came across a very unfortunate problem using this library.
Whenever I try to read a parquet file created with this same tool and containing a comma
,
in any of its headers.I get this error while
await parquetReader.getCursor().next()
:TypeError: Cannot read property 'fields' of undefined
stacktrace:
I guess this is caused by a rather "unsafe" operation in the
parquetjs/lib/schema.js
file on line 28:path.split(",")
I would be very helpful for any help with this problem.
Thank you
The text was updated successfully, but these errors were encountered: