Debugging typing errors when working with existing tables with a large number of columns is extremely frustrating, to say the least: the pyarrow error never indicates which column is causing the issue.

It would be an absolute life saver if more debugging information were raised with the exception.

E.g.:

pyarrow.lib.ArrowTypeError: object of type <class 'str'> cannot be converted to int