You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2010/06/16 20:02:28 UTC
[jira] Created: (HBASE-2738) Fix TestTimeRangeMapRed verification
now that we store multiple versions with same TS
Fix TestTimeRangeMapRed verification now that we store multiple versions with same TS
-------------------------------------------------------------------------------------
Key: HBASE-2738
URL: https://issues.apache.org/jira/browse/HBASE-2738
Project: HBase
Issue Type: Bug
Components: test
Affects Versions: 0.21.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
We recently introduced "memstore timestamps" which are internal, and allow a cell to exist twice with the same timestamp, from different puts. TestTimeRangeMapred now fails since it sees both the old and new version of the cells during verification. Setting the max versions of the verification scanner to 1 fixes it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HBASE-2738) Fix TestTimeRangeMapRed verification
now that we store multiple versions with same TS
Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon resolved HBASE-2738.
--------------------------------
Hadoop Flags: [Reviewed]
Resolution: Fixed
> Fix TestTimeRangeMapRed verification now that we store multiple versions with same TS
> -------------------------------------------------------------------------------------
>
> Key: HBASE-2738
> URL: https://issues.apache.org/jira/browse/HBASE-2738
> Project: HBase
> Issue Type: Bug
> Components: test
> Affects Versions: 0.21.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Fix For: 0.21.0
>
> Attachments: hbase-2738.txt
>
>
> We recently introduced "memstore timestamps" which are internal, and allow a cell to exist twice with the same timestamp, from different puts. TestTimeRangeMapred now fails since it sees both the old and new version of the cells during verification. Setting the max versions of the verification scanner to 1 fixes it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-2738) Fix TestTimeRangeMapRed verification
now that we store multiple versions with same TS
Posted by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Daniel Cryans updated HBASE-2738:
--------------------------------------
Fix Version/s: 0.21.0
+1
> Fix TestTimeRangeMapRed verification now that we store multiple versions with same TS
> -------------------------------------------------------------------------------------
>
> Key: HBASE-2738
> URL: https://issues.apache.org/jira/browse/HBASE-2738
> Project: HBase
> Issue Type: Bug
> Components: test
> Affects Versions: 0.21.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Fix For: 0.21.0
>
> Attachments: hbase-2738.txt
>
>
> We recently introduced "memstore timestamps" which are internal, and allow a cell to exist twice with the same timestamp, from different puts. TestTimeRangeMapred now fails since it sees both the old and new version of the cells during verification. Setting the max versions of the verification scanner to 1 fixes it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-2738) Fix TestTimeRangeMapRed verification
now that we store multiple versions with same TS
Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon updated HBASE-2738:
-------------------------------
Attachment: hbase-2738.txt
> Fix TestTimeRangeMapRed verification now that we store multiple versions with same TS
> -------------------------------------------------------------------------------------
>
> Key: HBASE-2738
> URL: https://issues.apache.org/jira/browse/HBASE-2738
> Project: HBase
> Issue Type: Bug
> Components: test
> Affects Versions: 0.21.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Attachments: hbase-2738.txt
>
>
> We recently introduced "memstore timestamps" which are internal, and allow a cell to exist twice with the same timestamp, from different puts. TestTimeRangeMapred now fails since it sees both the old and new version of the cells during verification. Setting the max versions of the verification scanner to 1 fixes it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.