Good call @stimme. I was too intent on figuring out the parquet file conversion which led me astray.Dask can process the gzipped csv so I gave that a try and it performed excellently--no issues and pe...

Hey @stimme, File size mostly. As an example, TSV/CSV are 2GB whereas the parquet counterparts are 150MB.

We are looking to download certain table data, transform it, and then upload to our Azure DataLake storage.The solution I have been working on involves a Python Azure Function app. Since the DAP parqu...

+1 to this!Please consider adding an option to the dap endpoint for the normalized data. Parsing this data into normalized columns is very resource heavy for those of us looking to transform this data...

The docs need to reflect this. Even the Postman collection import process refers to the ids simply as a "text" type with no formatting included.Thanks @IanGoh for saving some more facepalming!

Good call @stimme. I was too intent on figuring out the parquet file conversion which led me astray.Dask can process the gzipped csv so I gave that a try and it performed excellently--no issues and pe...

Hey @stimme, File size mostly. As an example, TSV/CSV are 2GB whereas the parquet counterparts are 150MB.

We are looking to download certain table data, transform it, and then upload to our Azure DataLake storage.The solution I have been working on involves a Python Azure Function app. Since the DAP parqu...

+1 to this!Please consider adding an option to the dap endpoint for the normalized data. Parsing this data into normalized columns is very resource heavy for those of us looking to transform this data...

The docs need to reflect this. Even the Postman collection import process refers to the ids simply as a "text" type with no formatting included.Thanks @IanGoh for saving some more facepalming!