You need to give your "equipment.location.name" an alias that is a valid column name. For example,   create view ... select equipment.location.name as name .... ... View more

  Some thoughts on your question: - Hive is more flexible in terms of data formats that it can scan - You may find Hive to be more feature rich in terms of SQL language support and built-in functions - Hive will most likely complete your query even if there are node failures (this makes it suitable for long-running jobs); this is true for both Hive on MR and Hive on Spark - If Impala can run your ETL, then it will probably be faster - Impala will fail/abort a query if a node goes down during query execution - The last point may make Impala less suitable for long-running jobs, but of course there is also a shorter failure window because queries are faster, so Impala may very well suit your ETL needs if you can tolerate the faiure behavior   You may also find this article interesting: https://vision.cloudera.com/sql-on-apache-hadoop-choosing-the-right-tool-for-the-right-job/   ... View more

I believe you can append query options applied to that JDBC to the connection string like this: jdbc:impala://your_impalad.com:21050/default;UseNativeQuery=1;SET RUNTIME_FILTER_MODE=OFF;   Alternatively, you should be able to run "SET RUNTIME_FILTER_MODE=OFF" as a query from JDBC to alter the defauly query options of that session. ... View more

Thanks for investigating. We've confirmed internally that the issue is related to Avro with many columns. 900 is somewhat wide.   Thanks for reporting! We'll continue to look into this issue. ... View more