Github user a10y commented on the issue:
    If you did add a test it should probably generate the Parquet file 
programmatically rather than checking it in. Some examples in
    However, given that there weren't tests before and this just fixes a break 
that was recently introduced, it seems reasonable that creation of tests for 
the vectorized reader can be done in a folowup?


To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to