joeramirez commented on issue #48057: URL: https://github.com/apache/arrow/issues/48057#issuecomment-3498387785
@thisisnic Fantastic! Luckily, this particular parquet file IS written with R, so I can make that change. I tested this with my production dataset and it worked great, even with reading from AWS S3 the mean was ~600ms (and ~200 reading from local). Most of my other use cases for arrow::read_parquet actually read parquets written by pyarrow in AWS lambda functions. I haven't noticed any issues with those yet, but those are much smaller parquet files anyway. This is good info to know though, so I'll be on the lookout in case I notice the same thing with those files. And lol @ the reprex - I didn't want to upload the real dataset, but I wanted to replicate the form of the data as close as possible, so that was what I came up with haha. Thanks again for your help with this and for checking on it so quickly! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
