TPC-H standard column names
gregrahn opened this issue · comments
Was wondering why the decision was made to not use the column names that match the TPC-H specification? This means that all queries that match the TPC-H standard (and run everywhere else) need to be rewritten to work with this (which is a bummer). Thanks.
IIRC the files don't have names at all, so when you load the files into your database, you can set the names to what ever you want.
Perhaps I overlooked where the names are set in the Presto code base (because that is where I noticed the difference). I'll close this issue and open one there.