Github user gengliangwang commented on the issue:
https://github.com/apache/spark/pull/22119
@tgravescs I saw your comments. Just feel that we can make it simpler by
reverting it.
For hive tables that used Databricks spark-avro, the tables can still using
the Databricks repo(since the built-in spark-avro is not loaded by default), or
have a manually migration to the built-in one, which makes more sense.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
