[jira] [Updated] (HBASE-5717) Scanner metrics are only reported if you get to the end of a scanner

2012-04-12 Thread Lars Hofhansl (Updated) (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-5717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lars Hofhansl updated HBASE-5717:
-

Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to 0.94 and 0.96.
Thanks for the patch Ian.
Thanks for the review Ted.

 Scanner metrics are only reported if you get to the end of a scanner
 

 Key: HBASE-5717
 URL: https://issues.apache.org/jira/browse/HBASE-5717
 Project: HBase
  Issue Type: Bug
  Components: client, metrics
Reporter: Ian Varley
Assignee: Ian Varley
Priority: Minor
 Fix For: 0.94.0, 0.96.0

 Attachments: 5717-v4.patch, ClientScanner_HBASE_5717-v2.patch, 
 ClientScanner_HBASE_5717-v3.patch, ClientScanner_HBASE_5717.patch

   Original Estimate: 4h
  Remaining Estimate: 4h

 When you turn on Scanner Metrics, the metrics are currently only made 
 available if you run over all records available in the scanner. If you stop 
 iterating before the end, the values are never flushed into the metrics 
 object (in the Scan attribute).
 Will supply a patch with fix and test.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (HBASE-5717) Scanner metrics are only reported if you get to the end of a scanner

2012-04-11 Thread Zhihong Yu (Updated) (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-5717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zhihong Yu updated HBASE-5717:
--

Fix Version/s: 0.96.0
   0.94.0
 Hadoop Flags: Reviewed

@Lars:
Do you want to integrate the patch ?

 Scanner metrics are only reported if you get to the end of a scanner
 

 Key: HBASE-5717
 URL: https://issues.apache.org/jira/browse/HBASE-5717
 Project: HBase
  Issue Type: Bug
  Components: client, metrics
Reporter: Ian Varley
Priority: Minor
 Fix For: 0.94.0, 0.96.0

 Attachments: ClientScanner_HBASE_5717-v2.patch, 
 ClientScanner_HBASE_5717-v3.patch, ClientScanner_HBASE_5717.patch

   Original Estimate: 4h
  Remaining Estimate: 4h

 When you turn on Scanner Metrics, the metrics are currently only made 
 available if you run over all records available in the scanner. If you stop 
 iterating before the end, the values are never flushed into the metrics 
 object (in the Scan attribute).
 Will supply a patch with fix and test.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (HBASE-5717) Scanner metrics are only reported if you get to the end of a scanner

2012-04-05 Thread Ian Varley (Updated) (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-5717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ian Varley updated HBASE-5717:
--

Attachment: ClientScanner_HBASE_5717-v3.patch

Added additional test cases for running off the end of the available results 
without closing the scanner, and also doing so with closing the scanner (so, 
all 3 permutations are covered).

 Scanner metrics are only reported if you get to the end of a scanner
 

 Key: HBASE-5717
 URL: https://issues.apache.org/jira/browse/HBASE-5717
 Project: HBase
  Issue Type: Bug
  Components: client, metrics
Reporter: Ian Varley
Priority: Minor
 Attachments: ClientScanner_HBASE_5717-v2.patch, 
 ClientScanner_HBASE_5717-v3.patch, ClientScanner_HBASE_5717.patch

   Original Estimate: 4h
  Remaining Estimate: 4h

 When you turn on Scanner Metrics, the metrics are currently only made 
 available if you run over all records available in the scanner. If you stop 
 iterating before the end, the values are never flushed into the metrics 
 object (in the Scan attribute).
 Will supply a patch with fix and test.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (HBASE-5717) Scanner metrics are only reported if you get to the end of a scanner

2012-04-04 Thread Ian Varley (Updated) (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-5717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ian Varley updated HBASE-5717:
--

Attachment: ClientScanner_HBASE_5717.patch

Patch to fix scanner metrics propagation when not exhausting all records in a 
scan

 Scanner metrics are only reported if you get to the end of a scanner
 

 Key: HBASE-5717
 URL: https://issues.apache.org/jira/browse/HBASE-5717
 Project: HBase
  Issue Type: Bug
  Components: client, metrics
Reporter: Ian Varley
Priority: Minor
 Attachments: ClientScanner_HBASE_5717.patch

   Original Estimate: 4h
  Remaining Estimate: 4h

 When you turn on Scanner Metrics, the metrics are currently only made 
 available if you run over all records available in the scanner. If you stop 
 iterating before the end, the values are never flushed into the metrics 
 object (in the Scan attribute).
 Will supply a patch with fix and test.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira