HIVE-29488: KryoException: NullPointerException: Cannot invoke "java.util.Collection.isEmpty()" because "this.delegate" is null#6352
Conversation
| assert (genericUDF != null); | ||
| this.genericUDF = genericUDF; | ||
| this.children = children; | ||
| this.children = children == null ? new ArrayList<>() : new ArrayList<>(children); |
There was a problem hiding this comment.
why you need a new ArrayList<>(children) here? why it can't be just
this.children = children == null ? List.of() : children;
There was a problem hiding this comment.
The new ArrayList<>(children) is required, because otherwise the NPE occurs. I've seen that some callers of getChildren modify the list, e.g., DynamicPartitionPruningOptimization, so I've I opted for new ArrayList<>() instead of List.of().
There was a problem hiding this comment.
@ayushtkn if we don't explicitly convert it to ArrayList, kryo cannot determine the actual runtime List object for ExprNodeGenericFuncDesc.children and uses AbstractMapBasedMultimap$WrappedCollection which is throwing NPE at deserializer in Tez Task.
Explicit cast ensure kryo knows its ArrayList and won't use AbstractMapBasedMultimap$WrappedCollection avoiding this NPE.
There was a problem hiding this comment.
@thomasrebele I suspect its more of Kryo-Guava deseralizer issue when children object is not null. Do you think we need to convert null to empty ?
There was a problem hiding this comment.
It is safer to avoid null for children, as there are several places without null check, e.g., in getExprString. The children are exposed to other classes by getChildren(), so it's simpler to just use an empty list instead of adding null checks everywhere.
There was a problem hiding this comment.
Another approach would be to check if children == null and throw NPE or IllegalArgumentException. Anyways, I think that we don't have any such calls currently at the code so choosing between exception, null, or new ArrayList<>() is rather subtle details.
There was a problem hiding this comment.
Indeed, though I'll leave the null-check for another PR.
…util.Collection.isEmpty()" because "this.delegate" is null Based on a fix by Naresh Panchetty Ramanaiah.
3b152b0 to
513255d
Compare
|
The test TestVectorizationContext had failed, because it changed the children list after creating the ExprNodeGenericFuncDesc. I checked the code, and this modification-after-instantiation seems to be limited to the test class. There are a few candidates that in principle could modify the list, but I don't think that happens in the code:
I therefore propose to change TestVectorizationContext so that it takes into account that ExprNodeGenericFuncDesc makes a copy of the children list. |
| assert (genericUDF != null); | ||
| this.genericUDF = genericUDF; | ||
| this.children = children; | ||
| this.children = children == null ? new ArrayList<>() : new ArrayList<>(children); |
There was a problem hiding this comment.
I've seen that some callers of getChildren modify the list, e.g., DynamicPartitionPruningOptimization, so I've I opted for new ArrayList<>() instead of List.of().
There was a problem hiding this comment.
I've created HIVE-29505 to make the children immutable. So I propose to postpone using List.of() until HIVE-29505 has been implemented.
zabetak
left a comment
There was a problem hiding this comment.
I like the fix cause it is generic and improves the encapsulation of ExprNodeGenericFuncDesc class. However, at the same time it changes a bit the existing behavior and increases a bit the memory footprint and GC activity. I saw the comment that changes in this class will not affect the overall behavior of Hive so I am OK to merge the PR as is.
As far as I see there aren't many places where we pass in the constructor something different from an ArrayList so another potential fix would be to change the creation of the IN function call in TypeCheckProcFactory by wrapping children into an ArrayList. This is less general but closer to the root cause that led to this issue.
I am OK with any of the above options so the approval remains no matter which we pick. The remaining comments are mostly nits that we don't necessarily have to address (or defer in follow-up).
| /** | ||
| * Constructor. | ||
| * | ||
| * @param children the children; a copy is made, so later changes to the passed list | ||
| * do not affect the children of this instance | ||
| */ |
There was a problem hiding this comment.
The doc seems a bit repetitive. We could possibly just put the mention about copy once over the field declaration:
private List<ExprNodeDesc> children;There was a problem hiding this comment.
I would prefer to to see such information in the IDE when hovering over the constructor.
| assert (genericUDF != null); | ||
| this.genericUDF = genericUDF; | ||
| this.children = children; | ||
| this.children = children == null ? new ArrayList<>() : new ArrayList<>(children); |
There was a problem hiding this comment.
Another approach would be to check if children == null and throw NPE or IllegalArgumentException. Anyways, I think that we don't have any such calls currently at the code so choosing between exception, null, or new ArrayList<>() is rather subtle details.
| select * from tab t1 left join tab t2 | ||
| on t1.attr = t2.attr and t2.attr in ( trim(t1.attr), '*'); | ||
|
|
||
| DROP TABLE tab; |
There was a problem hiding this comment.
DROP is not needed cause it is taken care by the test framework.
There was a problem hiding this comment.
I added it after seeing such a DROP TABLE statement in another q file. I'll drop it (the statement).
|
|
||
| CREATE TABLE tab(attr varchar(5)); | ||
|
|
||
| -- test case for HIVE-29488 |
There was a problem hiding this comment.
Since the actual problem is in plan serialization/deserialization should we add a unit test in TestSerializationUtilities?
There was a problem hiding this comment.
Indeed, that sounds like a good idea. I've added a test there and removed the q file test.
|



See HIVE-29488.
Thank you @nareshpr for providing an initial version of the q file test and a first version of the fix!
What changes were proposed in this pull request?
Put the children of ExprNodeGenericFuncDesc in their own list object.
Why are the changes needed?
Fixes an NPE due to the Kryo library when CBO is disabled.
Does this PR introduce any user-facing change?
No
How was this patch tested?
A q file test was added.