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
Great tool, glad I found it, because I almost started writing something like this myself!
One thing I ran into, though... nested types can't be exported to CSV.
Error: ArrowReadWriteError(CsvError("Nested type List(Field { name: \"item\", data_type: Utf8, nullable: true, dict_id: 0, dict_is_ordered: false, metadata: {} }) is not supported in CSV"))
Sometimes, we just don't care about the exact format, or don't even care about this particular column, and just want to load the dang thing into a spreadsheet. Encoding non-primitive column types as JSON helps to accomplish just that, and also happens to be non-ambiguous and therefore possibly even useful.
The text was updated successfully, but these errors were encountered:
ttencate
added a commit
to ttencate/pqrs
that referenced
this issue
Aug 19, 2024
These apply to both `cat` and `head` subcommands, and specify how to
handle nested fields if the output format is CSV (which does not support
nested fields). The default, `--nested-fields=error`, just exits with a
helpful error message.
This also changes the printing of errors escaping from the `main()`
function to use `Display`, rather than `Debug`, in order to make them
more user-friendly.
Fixesmanojkarthick#54.
Great tool, glad I found it, because I almost started writing something like this myself!
One thing I ran into, though... nested types can't be exported to CSV.
Sometimes, we just don't care about the exact format, or don't even care about this particular column, and just want to load the dang thing into a spreadsheet. Encoding non-primitive column types as JSON helps to accomplish just that, and also happens to be non-ambiguous and therefore possibly even useful.
The text was updated successfully, but these errors were encountered: