You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Daniel Ploeg (JIRA)" <ji...@apache.org> on 2009/10/25 22:01:59 UTC
[jira] Created: (HBASE-1934) NullPointerException in ClientScanner
NullPointerException in ClientScanner
-------------------------------------
Key: HBASE-1934
URL: https://issues.apache.org/jira/browse/HBASE-1934
Project: Hadoop HBase
Issue Type: Bug
Affects Versions: 0.20.1
Reporter: Daniel Ploeg
Fix For: 0.20.2, 0.21.0
The following stack trace was observed whilst loading a large volume of data into Hbase:
Caused by: java.lang.NullPointerException
at org.apache.hadoop.hbase.client.HTable$ClientScanner.next(HTable.java:2008)
at org.apache.hadoop.hbase.client.HTable$ClientScanner$1.hasNext(HTable.java:2089)
It appears that lastResult is initialized to be null, however in the exception handling code there isn't any null checking before the field is accessed for get row:
this.scan.setStartRow(this.lastResult.getRow());
There should be some additional null checking logic here.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-1934) NullPointerException in ClientScanner
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-1934:
----------------------------------
Status: Patch Available (was: Open)
> NullPointerException in ClientScanner
> -------------------------------------
>
> Key: HBASE-1934
> URL: https://issues.apache.org/jira/browse/HBASE-1934
> Project: Hadoop HBase
> Issue Type: Bug
> Affects Versions: 0.20.1
> Reporter: Daniel Ploeg
> Fix For: 0.20.2, 0.21.0
>
> Attachments: HBASE-1934.patch
>
>
> The following stack trace was observed whilst loading a large volume of data into Hbase:
> Caused by: java.lang.NullPointerException
> at org.apache.hadoop.hbase.client.HTable$ClientScanner.next(HTable.java:2008)
> at org.apache.hadoop.hbase.client.HTable$ClientScanner$1.hasNext(HTable.java:2089)
> It appears that lastResult is initialized to be null, however in the exception handling code there isn't any null checking before the field is accessed for get row:
> this.scan.setStartRow(this.lastResult.getRow());
> There should be some additional null checking logic here.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HBASE-1934) NullPointerException in ClientScanner
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack reassigned HBASE-1934:
----------------------------
Assignee: Andrew Purtell
> NullPointerException in ClientScanner
> -------------------------------------
>
> Key: HBASE-1934
> URL: https://issues.apache.org/jira/browse/HBASE-1934
> Project: Hadoop HBase
> Issue Type: Bug
> Affects Versions: 0.20.1
> Reporter: Daniel Ploeg
> Assignee: Andrew Purtell
> Fix For: 0.20.2, 0.21.0
>
> Attachments: HBASE-1934.patch
>
>
> The following stack trace was observed whilst loading a large volume of data into Hbase:
> Caused by: java.lang.NullPointerException
> at org.apache.hadoop.hbase.client.HTable$ClientScanner.next(HTable.java:2008)
> at org.apache.hadoop.hbase.client.HTable$ClientScanner$1.hasNext(HTable.java:2089)
> It appears that lastResult is initialized to be null, however in the exception handling code there isn't any null checking before the field is accessed for get row:
> this.scan.setStartRow(this.lastResult.getRow());
> There should be some additional null checking logic here.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-1934) NullPointerException in ClientScanner
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-1934:
----------------------------------
Attachment: HBASE-1934.patch
Seems an NSRE on first next invocation could cause this. Thanks for the bug report Daniel.
> NullPointerException in ClientScanner
> -------------------------------------
>
> Key: HBASE-1934
> URL: https://issues.apache.org/jira/browse/HBASE-1934
> Project: Hadoop HBase
> Issue Type: Bug
> Affects Versions: 0.20.1
> Reporter: Daniel Ploeg
> Fix For: 0.20.2, 0.21.0
>
> Attachments: HBASE-1934.patch
>
>
> The following stack trace was observed whilst loading a large volume of data into Hbase:
> Caused by: java.lang.NullPointerException
> at org.apache.hadoop.hbase.client.HTable$ClientScanner.next(HTable.java:2008)
> at org.apache.hadoop.hbase.client.HTable$ClientScanner$1.hasNext(HTable.java:2089)
> It appears that lastResult is initialized to be null, however in the exception handling code there isn't any null checking before the field is accessed for get row:
> this.scan.setStartRow(this.lastResult.getRow());
> There should be some additional null checking logic here.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-1934) NullPointerException in ClientScanner
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-1934:
-------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed branch and trunk. Thanks for the patch Daniel. Removed unused method filterSaysStop just above it while committing...
> NullPointerException in ClientScanner
> -------------------------------------
>
> Key: HBASE-1934
> URL: https://issues.apache.org/jira/browse/HBASE-1934
> Project: Hadoop HBase
> Issue Type: Bug
> Affects Versions: 0.20.1
> Reporter: Daniel Ploeg
> Fix For: 0.20.2, 0.21.0
>
> Attachments: HBASE-1934.patch
>
>
> The following stack trace was observed whilst loading a large volume of data into Hbase:
> Caused by: java.lang.NullPointerException
> at org.apache.hadoop.hbase.client.HTable$ClientScanner.next(HTable.java:2008)
> at org.apache.hadoop.hbase.client.HTable$ClientScanner$1.hasNext(HTable.java:2089)
> It appears that lastResult is initialized to be null, however in the exception handling code there isn't any null checking before the field is accessed for get row:
> this.scan.setStartRow(this.lastResult.getRow());
> There should be some additional null checking logic here.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-1934) NullPointerException in
ClientScanner
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770228#action_12770228 ]
stack commented on HBASE-1934:
------------------------------
Sorry, thanks Andrew for making the patch.
> NullPointerException in ClientScanner
> -------------------------------------
>
> Key: HBASE-1934
> URL: https://issues.apache.org/jira/browse/HBASE-1934
> Project: Hadoop HBase
> Issue Type: Bug
> Affects Versions: 0.20.1
> Reporter: Daniel Ploeg
> Assignee: Andrew Purtell
> Fix For: 0.20.2, 0.21.0
>
> Attachments: HBASE-1934.patch
>
>
> The following stack trace was observed whilst loading a large volume of data into Hbase:
> Caused by: java.lang.NullPointerException
> at org.apache.hadoop.hbase.client.HTable$ClientScanner.next(HTable.java:2008)
> at org.apache.hadoop.hbase.client.HTable$ClientScanner$1.hasNext(HTable.java:2089)
> It appears that lastResult is initialized to be null, however in the exception handling code there isn't any null checking before the field is accessed for get row:
> this.scan.setStartRow(this.lastResult.getRow());
> There should be some additional null checking logic here.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.