1 Answer
- Newest
- Most votes
- Most comments
0
Sounds like a configuration issue, this algorithm should be able to output proper output CSVs.
Are you using accept="text/csv"
and assemble_with="Line"
on your Transformer
? Is your strategy
set to SingleRecord
or MultiRecord
?
And split_type="Line"
, content_type="text/csv"
on the .transform()
call?
I have had custom algorithms accidentally output row vectors instead of column vectors for multi-record batches in the past (because they gave a 1D output which the default serializer interpreted as a row), but not built-in algorithms.
Dropping to SingleRecord
could be a last resort (forcing Batch Transform itself to handle the serialization), but would decrease efficiency/speed.
Relevant content
- asked a year ago
- asked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 8 months ago