yangBottle commented on pull request #31302: URL: https://github.com/apache/spark/pull/31302#issuecomment-766493076
> Hi, if it's assignable to both, why does Apache Spark need to use old one? Instead, it sounds like `Hivehbasetableinputformat` seems to miss the correct implementation for `mapreduce.InputFormat`. This doesn't look like a Spark issue to me. Is there an Hive JIRA issue for that? > > > Hivehbasetableinputformat relies on two versions of inputformat，one is org.apache.hadoop.mapred.InputFormat, the other is org.apache.hadoop.mapreduce.InputFormat,Causes both conditions to be true: > > classOf[oldInputClass[_, _]].isAssignableFrom(inputFormatClazz) is true > > classOf[newInputClass[_, _]].isAssignableFrom(inputFormatClazz) is true > > In view of this situation,It is expected to be compatible with the old version first I think in order to be compatible with implementation classes similar to 'org.apache.hadoop.hive.hbase.HiveHBaseTableInputFormat' that both uses the old API and the new API, it should be prioritized whether to create the old one. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
