[
https://issues.apache.org/jira/browse/HBASE-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613035#action_12613035
]
Jim Kellerman commented on HBASE-737:
-------------------------------------
Crud. I knew I should change the InternalScanner interface, but at the time it
seemed like it wasn't needed.
Ok. I've got this one.
> Scanner: every cell in a row has the same timestamp
> ---------------------------------------------------
>
> Key: HBASE-737
> URL: https://issues.apache.org/jira/browse/HBASE-737
> Project: Hadoop HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.2.0
> Reporter: Izaak Rubin
> Priority: Minor
> Fix For: 0.2.0
>
>
> A row can have multiple cells, and each cell can have a different timestamp.
> The get command in the shell demonstrates that cells are being stored with
> different timestamps:
> {code}
> hbase(main):008:0> get 'table1', 'row2'
> COLUMN CELL
> fam1:letters timestamp=1215707612949, value=def
> fam1:numbers timestamp=1215707629064, value=123
> fam2:letters timestamp=1215711498969, value=abc
> 3 row(s) in 0.0100 seconds
> {code}
> However, using the scanners to retrieve these cells shows that they all have
> the same timestamp:
> {code}
> hbase(main):009:0> scan 'table1'
> ROW COLUMN+CELL
> row2 column=fam1:letters, timestamp=1215711498969,
> value=def
> row2 column=fam1:numbers, timestamp=1215711498969,
> value=123
> row2 column=fam2:letters, timestamp=1215711498969,
> value=abc
> 3 row(s) in 0.0600 seconds
> {code}
> The scanners are losing timestamp information somewhere along the line.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
