You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Lars George (JIRA)" <ji...@apache.org> on 2009/06/04 21:39:07 UTC
[jira] Created: (HBASE-1482) Provide fast doesExist() method to
avoid get() != null calls
Provide fast doesExist() method to avoid get() != null calls
------------------------------------------------------------
Key: HBASE-1482
URL: https://issues.apache.org/jira/browse/HBASE-1482
Project: Hadoop HBase
Issue Type: Improvement
Affects Versions: 0.19.3
Reporter: Lars George
Fix For: 0.21.0
Currently one has to use get() != null checks to see if a specific column has a value for any given row. But this involves the whole load and transfer stack to shift the data to the client just for it to drop the content. Better would be a server side check and only returning the boolean back to the client, especially if the checked cell is containing MB's of data.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-1482) Provide fast doesExist() method to
avoid get() != null calls
Posted by "Lars George (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716440#action_12716440 ]
Lars George commented on HBASE-1482:
------------------------------------
Oh, HBASE-1102, I see it in the history now. Sorry if this is a dupe and it does the above then please disregard this issue and close accordingly.
> Provide fast doesExist() method to avoid get() != null calls
> ------------------------------------------------------------
>
> Key: HBASE-1482
> URL: https://issues.apache.org/jira/browse/HBASE-1482
> Project: Hadoop HBase
> Issue Type: Improvement
> Affects Versions: 0.19.3
> Reporter: Lars George
> Fix For: 0.21.0
>
>
> Currently one has to use get() != null checks to see if a specific column has a value for any given row. But this involves the whole load and transfer stack to shift the data to the client just for it to drop the content. Better would be a server side check and only returning the boolean back to the client, especially if the checked cell is containing MB's of data.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (HBASE-1482) Provide fast doesExist()
method to avoid get() != null calls
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716382#action_12716382 ]
Andrew Purtell edited comment on HBASE-1482 at 6/4/09 1:07 PM:
---------------------------------------------------------------
HTable.exists() ? It does existence testing server side.
was (Author: apurtell):
HTable.exists() ?
> Provide fast doesExist() method to avoid get() != null calls
> ------------------------------------------------------------
>
> Key: HBASE-1482
> URL: https://issues.apache.org/jira/browse/HBASE-1482
> Project: Hadoop HBase
> Issue Type: Improvement
> Affects Versions: 0.19.3
> Reporter: Lars George
> Fix For: 0.21.0
>
>
> Currently one has to use get() != null checks to see if a specific column has a value for any given row. But this involves the whole load and transfer stack to shift the data to the client just for it to drop the content. Better would be a server side check and only returning the boolean back to the client, especially if the checked cell is containing MB's of data.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-1482) Provide fast doesExist() method to
avoid get() != null calls
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716382#action_12716382 ]
Andrew Purtell commented on HBASE-1482:
---------------------------------------
HTable.exists() ?
> Provide fast doesExist() method to avoid get() != null calls
> ------------------------------------------------------------
>
> Key: HBASE-1482
> URL: https://issues.apache.org/jira/browse/HBASE-1482
> Project: Hadoop HBase
> Issue Type: Improvement
> Affects Versions: 0.19.3
> Reporter: Lars George
> Fix For: 0.21.0
>
>
> Currently one has to use get() != null checks to see if a specific column has a value for any given row. But this involves the whole load and transfer stack to shift the data to the client just for it to drop the content. Better would be a server side check and only returning the boolean back to the client, especially if the checked cell is containing MB's of data.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HBASE-1482) Provide fast doesExist() method to
avoid get() != null calls
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell resolved HBASE-1482.
-----------------------------------
Resolution: Duplicate
> Provide fast doesExist() method to avoid get() != null calls
> ------------------------------------------------------------
>
> Key: HBASE-1482
> URL: https://issues.apache.org/jira/browse/HBASE-1482
> Project: Hadoop HBase
> Issue Type: Improvement
> Affects Versions: 0.19.3
> Reporter: Lars George
> Fix For: 0.21.0
>
>
> Currently one has to use get() != null checks to see if a specific column has a value for any given row. But this involves the whole load and transfer stack to shift the data to the client just for it to drop the content. Better would be a server side check and only returning the boolean back to the client, especially if the checked cell is containing MB's of data.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.