You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2009/09/10 21:28:57 UTC
[jira] Created: (HBASE-1824) [stargate] default timestamp should be
LATEST_TIMESTAMP
[stargate] default timestamp should be LATEST_TIMESTAMP
-------------------------------------------------------
Key: HBASE-1824
URL: https://issues.apache.org/jira/browse/HBASE-1824
Project: Hadoop HBase
Issue Type: Bug
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Fix For: 0.20.1
>From Greg Cottman up on hbase-user@
{quote}
f I don't put the optional "timestamp" attribute in a Cell when I'm inserting data, the timestamp ends up as zero, which caused much confusion because it pre-dates the value I thought I was replacing. I assumed that not specifying this attribute would cause the timestamp to default to the current HBase server time. Instead I found I had to specify the timestamp as "-1" to get this behaviour. Is this a bug or an intentional semantic?
{quote}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-1824) [stargate] default timestamp should be
LATEST_TIMESTAMP
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-1824:
----------------------------------
Attachment: HBASE-1824.patch
> [stargate] default timestamp should be LATEST_TIMESTAMP
> -------------------------------------------------------
>
> Key: HBASE-1824
> URL: https://issues.apache.org/jira/browse/HBASE-1824
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 0.20.1
>
> Attachments: HBASE-1824.patch
>
>
> From Greg Cottman up on hbase-user@
> {quote}
> f I don't put the optional "timestamp" attribute in a Cell when I'm inserting data, the timestamp ends up as zero, which caused much confusion because it pre-dates the value I thought I was replacing. I assumed that not specifying this attribute would cause the timestamp to default to the current HBase server time. Instead I found I had to specify the timestamp as "-1" to get this behaviour. Is this a bug or an intentional semantic?
> {quote}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-1824) [stargate] default timestamp should be
LATEST_TIMESTAMP
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-1824:
----------------------------------
Attachment: (was: HBASE-1824.patch)
> [stargate] default timestamp should be LATEST_TIMESTAMP
> -------------------------------------------------------
>
> Key: HBASE-1824
> URL: https://issues.apache.org/jira/browse/HBASE-1824
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 0.20.1, 0.21.0
>
> Attachments: HBASE-1824.patch
>
>
> From Greg Cottman up on hbase-user@
> {quote}
> f I don't put the optional "timestamp" attribute in a Cell when I'm inserting data, the timestamp ends up as zero, which caused much confusion because it pre-dates the value I thought I was replacing. I assumed that not specifying this attribute would cause the timestamp to default to the current HBase server time. Instead I found I had to specify the timestamp as "-1" to get this behaviour. Is this a bug or an intentional semantic?
> {quote}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-1824) [stargate] default timestamp should
be LATEST_TIMESTAMP
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753805#action_12753805 ]
stack commented on HBASE-1824:
------------------------------
Pardon me. I missed that it had been committed to 0.20.1.
> [stargate] default timestamp should be LATEST_TIMESTAMP
> -------------------------------------------------------
>
> Key: HBASE-1824
> URL: https://issues.apache.org/jira/browse/HBASE-1824
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 0.20.1, 0.21.0
>
> Attachments: HBASE-1824.patch
>
>
> From Greg Cottman up on hbase-user@
> {quote}
> f I don't put the optional "timestamp" attribute in a Cell when I'm inserting data, the timestamp ends up as zero, which caused much confusion because it pre-dates the value I thought I was replacing. I assumed that not specifying this attribute would cause the timestamp to default to the current HBase server time. Instead I found I had to specify the timestamp as "-1" to get this behaviour. Is this a bug or an intentional semantic?
> {quote}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-1824) [stargate] default timestamp should
be LATEST_TIMESTAMP
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753784#action_12753784 ]
stack commented on HBASE-1824:
------------------------------
Do it on the branch too Andrew?
> [stargate] default timestamp should be LATEST_TIMESTAMP
> -------------------------------------------------------
>
> Key: HBASE-1824
> URL: https://issues.apache.org/jira/browse/HBASE-1824
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 0.20.1, 0.21.0
>
> Attachments: HBASE-1824.patch
>
>
> From Greg Cottman up on hbase-user@
> {quote}
> f I don't put the optional "timestamp" attribute in a Cell when I'm inserting data, the timestamp ends up as zero, which caused much confusion because it pre-dates the value I thought I was replacing. I assumed that not specifying this attribute would cause the timestamp to default to the current HBase server time. Instead I found I had to specify the timestamp as "-1" to get this behaviour. Is this a bug or an intentional semantic?
> {quote}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-1824) [stargate] default timestamp should
be LATEST_TIMESTAMP
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753790#action_12753790 ]
Andrew Purtell commented on HBASE-1824:
---------------------------------------
Which branch? Already committed to 0.20.1 and 0.21.0.
> [stargate] default timestamp should be LATEST_TIMESTAMP
> -------------------------------------------------------
>
> Key: HBASE-1824
> URL: https://issues.apache.org/jira/browse/HBASE-1824
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 0.20.1, 0.21.0
>
> Attachments: HBASE-1824.patch
>
>
> From Greg Cottman up on hbase-user@
> {quote}
> f I don't put the optional "timestamp" attribute in a Cell when I'm inserting data, the timestamp ends up as zero, which caused much confusion because it pre-dates the value I thought I was replacing. I assumed that not specifying this attribute would cause the timestamp to default to the current HBase server time. Instead I found I had to specify the timestamp as "-1" to get this behaviour. Is this a bug or an intentional semantic?
> {quote}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HBASE-1824) [stargate] default timestamp should
be LATEST_TIMESTAMP
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell resolved HBASE-1824.
-----------------------------------
Resolution: Fixed
Fix Version/s: 0.21.0
Committed to branch and trunk.
> [stargate] default timestamp should be LATEST_TIMESTAMP
> -------------------------------------------------------
>
> Key: HBASE-1824
> URL: https://issues.apache.org/jira/browse/HBASE-1824
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 0.20.1, 0.21.0
>
> Attachments: HBASE-1824.patch
>
>
> From Greg Cottman up on hbase-user@
> {quote}
> f I don't put the optional "timestamp" attribute in a Cell when I'm inserting data, the timestamp ends up as zero, which caused much confusion because it pre-dates the value I thought I was replacing. I assumed that not specifying this attribute would cause the timestamp to default to the current HBase server time. Instead I found I had to specify the timestamp as "-1" to get this behaviour. Is this a bug or an intentional semantic?
> {quote}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-1824) [stargate] default timestamp should be
LATEST_TIMESTAMP
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-1824:
----------------------------------
Attachment: HBASE-1824.patch
> [stargate] default timestamp should be LATEST_TIMESTAMP
> -------------------------------------------------------
>
> Key: HBASE-1824
> URL: https://issues.apache.org/jira/browse/HBASE-1824
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 0.20.1, 0.21.0
>
> Attachments: HBASE-1824.patch
>
>
> From Greg Cottman up on hbase-user@
> {quote}
> f I don't put the optional "timestamp" attribute in a Cell when I'm inserting data, the timestamp ends up as zero, which caused much confusion because it pre-dates the value I thought I was replacing. I assumed that not specifying this attribute would cause the timestamp to default to the current HBase server time. Instead I found I had to specify the timestamp as "-1" to get this behaviour. Is this a bug or an intentional semantic?
> {quote}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.