Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixed spark3.0 access hive table while data in hbase problem
What changes were proposed in this pull request?
The PR modify TableReader.scala to create OldHadoopRDD when inputformat is 'org.apache.hadoop.hive.hbase.HiveHBaseTableInputFormat', beacuse NewHadoopRDD uses the new MapReduce API (
org.apache.hadoop.mapreduce),but some initialization operations for hbase are implemented using the older MapReduce API (org.apache.hadoop.mapred),this makes the default NewHadoopRDD can not access hbase table.Therefore, in order to be compatible with implementation classes similar to 'org.apache.hadoop.hive.hbase.HiveHBaseTableInputFormat' that uses the old API and the new API, it should be prioritized whether to create OldHadoopRDD.This PR is similar to #29178
Reference link: https://issues.apache.org/jira/browse/SPARK-32380
Why are the changes needed?
Sparksql cannot access hive table while data in hbase, want to fixed this bug.
Does this PR introduce any user-facing change?
No
How was this patch tested?