[HBASE-22769] Make reflection explicit in to avoid ClassNotFoundException in SQL pushdown with filters #74
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.
Queries with filters may error out with ClassNotFoundException as detailed in HBASE-22769.
The error can be worked around with
.option("hbase.spark.pushdown.columnfilter", false)but this bypasses SQL pushdown, which is a useful feature.The error appears to come from reflection. This PR aims at making reflection explicit for
org.apache.hadoop.hbase.spark.datasources.JavaBytesEncoderandorg.apache.hadoop.hbase.spark.DynamicLogicExpressionBuilder.The patch has been manually tested.