You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
results = handler.readData(tableName, subEntityMetadata.getEntityClazz(), subEntityMetadata,
rowId, subEntityMetadata.getRelationNames(), filter, columns);
// Result will not be empty for match sub entity.if (!results.isEmpty()) { <-- NPEherebreak;
}
This happens when query doesn't return any results (for example, I try to find user with non-existent name). See HBaseDataHandler#onRead(): output is null, results is empty.
Reproduced in 2.15.1, but as far as I can see, this is also actual for 2.16.
The text was updated successfully, but these errors were encountered:
@monkegoist
The part of code which you mentioned is for the JPA Inheritence implementation which is yet under development for kundera-hbase-v2. Hence, you might be facing such issues. We are actively working on it and will fix all such issues as soon as possible. Thanks for letting us know about the bug.
@pragalbhgarg I see, thanks for your reply. Any insights on when you're planning to release fix version? So far, I just added null check and this seems to fix the issue.
@monkegoist
We are planning on a patch release by mid April. Also, we have fixed the NPE in the trunk and will fix other related issues soon. We will notify you as we do that.
Null-check is missing in
fetchEntity()
method:This happens when query doesn't return any results (for example, I try to find user with non-existent name). See
HBaseDataHandler#onRead()
:output
is null,results
is empty.Reproduced in 2.15.1, but as far as I can see, this is also actual for 2.16.
The text was updated successfully, but these errors were encountered: