The first thing I would try is turning on verbose errors. The setting for that is exec.errors.verbose
I use select * from sys.options quite a bit when determining how to approach problems. To alter your session to use verbose errors type ALTER SESSION set `exec.errors.verbose` = true; Then you may get more data back on your error. On Wed, Mar 1, 2017 at 10:34 AM, Wesley Chow <[email protected]> wrote: > Is there any guidance on finding a needle-in-a-haystack input error in a > ton of data? For example, I've got one row in a csv file amongst thousands > containing tens of millions of rows that has as its first column a string > instead of a number like it should be. Is there some way to get Drill to > tell me which file that row is in? Something like the dirX columns would > work, since I can select for the row. > > Note, these are CSV files hosted in S3. > > Thanks, > Wes >
