[jira] [Updated] (HBASE-13561) ITBLL.Verify doesn't actually evaluate counters after job completes
[
https://issues.apache.org/jira/browse/HBASE-13561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-13561:
---
Fix Version/s: (was: 1.0.3)
1.0.2
ITBLL.Verify doesn't actually evaluate counters after job completes
---
Key: HBASE-13561
URL: https://issues.apache.org/jira/browse/HBASE-13561
Project: HBase
Issue Type: Bug
Components: integration tests
Affects Versions: 1.0.0, 2.0.0, 1.1.0, 0.98.12
Reporter: Josh Elser
Assignee: Josh Elser
Fix For: 2.0.0, 0.98.14, 1.0.2, 1.2.0, 1.1.2
Attachments: HBASE-13561-0.98-v2.patch,
HBASE-13561-branch-1.0-v2.patch, HBASE-13561-v1.patch, HBASE-13561-v2.patch
Was digging through ITBLL and noticed this oddity:
The {{Verify}} Tool doesn't actually call {{Verify#verify(long)}} like the
{{Loop}} Tool does. Granted, it doesn't know the total number of KVs that
were written given the current arguments, it's not even checking to see if
there things like UNDEFINED records found.
It seems to me that {{Verify}} should really be doing *some* checking on the
counters like {{Loop}} does and not just leaving it up to the visual
inspection of whomever launched the task.
Am I missing something?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13561) ITBLL.Verify doesn't actually evaluate counters after job completes
[
https://issues.apache.org/jira/browse/HBASE-13561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-13561:
Fix Version/s: (was: 1.2.1)
(was: 1.3.0)
1.2.0
ITBLL.Verify doesn't actually evaluate counters after job completes
---
Key: HBASE-13561
URL: https://issues.apache.org/jira/browse/HBASE-13561
Project: HBase
Issue Type: Bug
Components: integration tests
Affects Versions: 1.0.0, 2.0.0, 1.1.0, 0.98.12
Reporter: Josh Elser
Assignee: Josh Elser
Fix For: 2.0.0, 0.98.14, 1.2.0, 1.1.2, 1.0.3
Attachments: HBASE-13561-0.98-v2.patch,
HBASE-13561-branch-1.0-v2.patch, HBASE-13561-v1.patch, HBASE-13561-v2.patch
Was digging through ITBLL and noticed this oddity:
The {{Verify}} Tool doesn't actually call {{Verify#verify(long)}} like the
{{Loop}} Tool does. Granted, it doesn't know the total number of KVs that
were written given the current arguments, it's not even checking to see if
there things like UNDEFINED records found.
It seems to me that {{Verify}} should really be doing *some* checking on the
counters like {{Loop}} does and not just leaving it up to the visual
inspection of whomever launched the task.
Am I missing something?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13561) ITBLL.Verify doesn't actually evaluate counters after job completes
[
https://issues.apache.org/jira/browse/HBASE-13561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated HBASE-13561:
---
Attachment: HBASE-13561-v2.patch
Verified failure to Verify is reported as expected. Updated usage on ITBLL to
advise that return code is checked in addition to counters.
ITBLL.Verify doesn't actually evaluate counters after job completes
---
Key: HBASE-13561
URL: https://issues.apache.org/jira/browse/HBASE-13561
Project: HBase
Issue Type: Bug
Components: integration tests
Affects Versions: 1.0.0, 2.0.0, 1.1.0, 0.98.12
Reporter: Josh Elser
Assignee: Josh Elser
Fix For: 2.0.0, 0.98.14, 1.1.2, 1.3.0, 1.2.1, 1.0.3
Attachments: HBASE-13561-v1.patch, HBASE-13561-v2.patch
Was digging through ITBLL and noticed this oddity:
The {{Verify}} Tool doesn't actually call {{Verify#verify(long)}} like the
{{Loop}} Tool does. Granted, it doesn't know the total number of KVs that
were written given the current arguments, it's not even checking to see if
there things like UNDEFINED records found.
It seems to me that {{Verify}} should really be doing *some* checking on the
counters like {{Loop}} does and not just leaving it up to the visual
inspection of whomever launched the task.
Am I missing something?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13561) ITBLL.Verify doesn't actually evaluate counters after job completes
[
https://issues.apache.org/jira/browse/HBASE-13561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-13561:
--
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: (was: 1.0.3)
(was: 0.98.14)
Status: Resolved (was: Patch Available)
Pushed to branch-1, branch-1.1, branch-1.2, and master. Did not push to
branch-1.0 or 0.98 (if you put up a backport, I'll apply to these branches too
[~elserj])
ITBLL.Verify doesn't actually evaluate counters after job completes
---
Key: HBASE-13561
URL: https://issues.apache.org/jira/browse/HBASE-13561
Project: HBase
Issue Type: Bug
Components: integration tests
Affects Versions: 1.0.0, 2.0.0, 1.1.0, 0.98.12
Reporter: Josh Elser
Assignee: Josh Elser
Fix For: 2.0.0, 1.1.2, 1.3.0, 1.2.1
Attachments: HBASE-13561-v1.patch, HBASE-13561-v2.patch
Was digging through ITBLL and noticed this oddity:
The {{Verify}} Tool doesn't actually call {{Verify#verify(long)}} like the
{{Loop}} Tool does. Granted, it doesn't know the total number of KVs that
were written given the current arguments, it's not even checking to see if
there things like UNDEFINED records found.
It seems to me that {{Verify}} should really be doing *some* checking on the
counters like {{Loop}} does and not just leaving it up to the visual
inspection of whomever launched the task.
Am I missing something?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13561) ITBLL.Verify doesn't actually evaluate counters after job completes
[
https://issues.apache.org/jira/browse/HBASE-13561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-13561:
--
Fix Version/s: 1.0.3
0.98.14
Pushed the 0.98 and branch-1.0 patches. Thanks [~elserj]
ITBLL.Verify doesn't actually evaluate counters after job completes
---
Key: HBASE-13561
URL: https://issues.apache.org/jira/browse/HBASE-13561
Project: HBase
Issue Type: Bug
Components: integration tests
Affects Versions: 1.0.0, 2.0.0, 1.1.0, 0.98.12
Reporter: Josh Elser
Assignee: Josh Elser
Fix For: 2.0.0, 0.98.14, 1.1.2, 1.3.0, 1.2.1, 1.0.3
Attachments: HBASE-13561-0.98-v2.patch,
HBASE-13561-branch-1.0-v2.patch, HBASE-13561-v1.patch, HBASE-13561-v2.patch
Was digging through ITBLL and noticed this oddity:
The {{Verify}} Tool doesn't actually call {{Verify#verify(long)}} like the
{{Loop}} Tool does. Granted, it doesn't know the total number of KVs that
were written given the current arguments, it's not even checking to see if
there things like UNDEFINED records found.
It seems to me that {{Verify}} should really be doing *some* checking on the
counters like {{Loop}} does and not just leaving it up to the visual
inspection of whomever launched the task.
Am I missing something?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13561) ITBLL.Verify doesn't actually evaluate counters after job completes
[
https://issues.apache.org/jira/browse/HBASE-13561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated HBASE-13561:
---
Attachment: HBASE-13561-branch-1.0-v2.patch
HBASE-13561-0.98-v2.patch
v2 patches for 0.98 and branch-1.0
ITBLL.Verify doesn't actually evaluate counters after job completes
---
Key: HBASE-13561
URL: https://issues.apache.org/jira/browse/HBASE-13561
Project: HBase
Issue Type: Bug
Components: integration tests
Affects Versions: 1.0.0, 2.0.0, 1.1.0, 0.98.12
Reporter: Josh Elser
Assignee: Josh Elser
Fix For: 2.0.0, 1.1.2, 1.3.0, 1.2.1
Attachments: HBASE-13561-0.98-v2.patch,
HBASE-13561-branch-1.0-v2.patch, HBASE-13561-v1.patch, HBASE-13561-v2.patch
Was digging through ITBLL and noticed this oddity:
The {{Verify}} Tool doesn't actually call {{Verify#verify(long)}} like the
{{Loop}} Tool does. Granted, it doesn't know the total number of KVs that
were written given the current arguments, it's not even checking to see if
there things like UNDEFINED records found.
It seems to me that {{Verify}} should really be doing *some* checking on the
counters like {{Loop}} does and not just leaving it up to the visual
inspection of whomever launched the task.
Am I missing something?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13561) ITBLL.Verify doesn't actually evaluate counters after job completes
[
https://issues.apache.org/jira/browse/HBASE-13561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated HBASE-13561:
---
Status: Patch Available (was: Open)
ITBLL.Verify doesn't actually evaluate counters after job completes
---
Key: HBASE-13561
URL: https://issues.apache.org/jira/browse/HBASE-13561
Project: HBase
Issue Type: Bug
Components: integration tests
Affects Versions: 0.98.12, 1.1.0, 1.0.0, 2.0.0
Reporter: Josh Elser
Assignee: Josh Elser
Fix For: 2.0.0, 0.98.14, 1.1.2, 1.3.0, 1.2.1, 1.0.3
Attachments: HBASE-13561-v1.patch
Was digging through ITBLL and noticed this oddity:
The {{Verify}} Tool doesn't actually call {{Verify#verify(long)}} like the
{{Loop}} Tool does. Granted, it doesn't know the total number of KVs that
were written given the current arguments, it's not even checking to see if
there things like UNDEFINED records found.
It seems to me that {{Verify}} should really be doing *some* checking on the
counters like {{Loop}} does and not just leaving it up to the visual
inspection of whomever launched the task.
Am I missing something?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13561) ITBLL.Verify doesn't actually evaluate counters after job completes
[
https://issues.apache.org/jira/browse/HBASE-13561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated HBASE-13561:
---
Attachment: HBASE-13561-v1.patch
Consolidates the verification of the Counters for both {{Verify}} and
{{Loop}}. Ran {{Generator}} and {{Verify}} by hand against master and verified
that they finished successfully.
ITBLL.Verify doesn't actually evaluate counters after job completes
---
Key: HBASE-13561
URL: https://issues.apache.org/jira/browse/HBASE-13561
Project: HBase
Issue Type: Bug
Components: integration tests
Affects Versions: 1.0.0, 2.0.0, 1.1.0, 0.98.12
Reporter: Josh Elser
Assignee: Josh Elser
Fix For: 2.0.0, 0.98.14, 1.1.2, 1.3.0, 1.2.1, 1.0.3
Attachments: HBASE-13561-v1.patch
Was digging through ITBLL and noticed this oddity:
The {{Verify}} Tool doesn't actually call {{Verify#verify(long)}} like the
{{Loop}} Tool does. Granted, it doesn't know the total number of KVs that
were written given the current arguments, it's not even checking to see if
there things like UNDEFINED records found.
It seems to me that {{Verify}} should really be doing *some* checking on the
counters like {{Loop}} does and not just leaving it up to the visual
inspection of whomever launched the task.
Am I missing something?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13561) ITBLL.Verify doesn't actually evaluate counters after job completes
[
https://issues.apache.org/jira/browse/HBASE-13561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated HBASE-13561:
--
Fix Version/s: (was: 1.0.2)
1.0.3
ITBLL.Verify doesn't actually evaluate counters after job completes
---
Key: HBASE-13561
URL: https://issues.apache.org/jira/browse/HBASE-13561
Project: HBase
Issue Type: Bug
Components: integration tests
Affects Versions: 1.0.0, 2.0.0, 1.1.0, 0.98.12
Reporter: Josh Elser
Assignee: Josh Elser
Fix For: 2.0.0, 0.98.14, 1.1.2, 1.3.0, 1.2.1, 1.0.3
Was digging through ITBLL and noticed this oddity:
The {{Verify}} Tool doesn't actually call {{Verify#verify(long)}} like the
{{Loop}} Tool does. Granted, it doesn't know the total number of KVs that
were written given the current arguments, it's not even checking to see if
there things like UNDEFINED records found.
It seems to me that {{Verify}} should really be doing *some* checking on the
counters like {{Loop}} does and not just leaving it up to the visual
inspection of whomever launched the task.
Am I missing something?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13561) ITBLL.Verify doesn't actually evaluate counters after job completes
[
https://issues.apache.org/jira/browse/HBASE-13561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-13561:
Fix Version/s: (was: 1.2.0)
1.2.1
1.3.0
still working on this?
ITBLL.Verify doesn't actually evaluate counters after job completes
---
Key: HBASE-13561
URL: https://issues.apache.org/jira/browse/HBASE-13561
Project: HBase
Issue Type: Bug
Components: integration tests
Affects Versions: 1.0.0, 2.0.0, 1.1.0, 0.98.12
Reporter: Josh Elser
Assignee: Josh Elser
Fix For: 2.0.0, 0.98.14, 1.0.2, 1.1.2, 1.3.0, 1.2.1
Was digging through ITBLL and noticed this oddity:
The {{Verify}} Tool doesn't actually call {{Verify#verify(long)}} like the
{{Loop}} Tool does. Granted, it doesn't know the total number of KVs that
were written given the current arguments, it's not even checking to see if
there things like UNDEFINED records found.
It seems to me that {{Verify}} should really be doing *some* checking on the
counters like {{Loop}} does and not just leaving it up to the visual
inspection of whomever launched the task.
Am I missing something?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13561) ITBLL.Verify doesn't actually evaluate counters after job completes
[
https://issues.apache.org/jira/browse/HBASE-13561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-13561:
-
Fix Version/s: (was: 1.1.1)
1.1.2
ITBLL.Verify doesn't actually evaluate counters after job completes
---
Key: HBASE-13561
URL: https://issues.apache.org/jira/browse/HBASE-13561
Project: HBase
Issue Type: Bug
Components: integration tests
Affects Versions: 1.0.0, 2.0.0, 1.1.0, 0.98.12
Reporter: Josh Elser
Assignee: Josh Elser
Fix For: 2.0.0, 0.98.14, 1.0.2, 1.2.0, 1.1.2
Was digging through ITBLL and noticed this oddity:
The {{Verify}} Tool doesn't actually call {{Verify#verify(long)}} like the
{{Loop}} Tool does. Granted, it doesn't know the total number of KVs that
were written given the current arguments, it's not even checking to see if
there things like UNDEFINED records found.
It seems to me that {{Verify}} should really be doing *some* checking on the
counters like {{Loop}} does and not just leaving it up to the visual
inspection of whomever launched the task.
Am I missing something?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13561) ITBLL.Verify doesn't actually evaluate counters after job completes
[
https://issues.apache.org/jira/browse/HBASE-13561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-13561:
---
Fix Version/s: (was: 0.98.13)
0.98.14
ITBLL.Verify doesn't actually evaluate counters after job completes
---
Key: HBASE-13561
URL: https://issues.apache.org/jira/browse/HBASE-13561
Project: HBase
Issue Type: Bug
Components: integration tests
Affects Versions: 1.0.0, 2.0.0, 1.1.0, 0.98.12
Reporter: Josh Elser
Assignee: Josh Elser
Fix For: 2.0.0, 0.98.14, 1.0.2, 1.2.0, 1.1.1
Was digging through ITBLL and noticed this oddity:
The {{Verify}} Tool doesn't actually call {{Verify#verify(long)}} like the
{{Loop}} Tool does. Granted, it doesn't know the total number of KVs that
were written given the current arguments, it's not even checking to see if
there things like UNDEFINED records found.
It seems to me that {{Verify}} should really be doing *some* checking on the
counters like {{Loop}} does and not just leaving it up to the visual
inspection of whomever launched the task.
Am I missing something?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13561) ITBLL.Verify doesn't actually evaluate counters after job completes
[
https://issues.apache.org/jira/browse/HBASE-13561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-13561:
-
Fix Version/s: 1.2.0
ITBLL.Verify doesn't actually evaluate counters after job completes
---
Key: HBASE-13561
URL: https://issues.apache.org/jira/browse/HBASE-13561
Project: HBase
Issue Type: Bug
Components: integration tests
Affects Versions: 1.0.0, 2.0.0, 1.1.0, 0.98.12
Reporter: Josh Elser
Assignee: Josh Elser
Fix For: 2.0.0, 0.98.13, 1.0.2, 1.2.0, 1.1.1
Was digging through ITBLL and noticed this oddity:
The {{Verify}} Tool doesn't actually call {{Verify#verify(long)}} like the
{{Loop}} Tool does. Granted, it doesn't know the total number of KVs that
were written given the current arguments, it's not even checking to see if
there things like UNDEFINED records found.
It seems to me that {{Verify}} should really be doing *some* checking on the
counters like {{Loop}} does and not just leaving it up to the visual
inspection of whomever launched the task.
Am I missing something?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13561) ITBLL.Verify doesn't actually evaluate counters after job completes
[
https://issues.apache.org/jira/browse/HBASE-13561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-13561:
-
Fix Version/s: (was: 1.1.0)
1.1.1
ITBLL.Verify doesn't actually evaluate counters after job completes
---
Key: HBASE-13561
URL: https://issues.apache.org/jira/browse/HBASE-13561
Project: HBase
Issue Type: Bug
Components: integration tests
Affects Versions: 1.0.0, 2.0.0, 1.1.0, 0.98.12
Reporter: Josh Elser
Assignee: Josh Elser
Fix For: 2.0.0, 0.98.13, 1.0.2, 1.1.1
Was digging through ITBLL and noticed this oddity:
The {{Verify}} Tool doesn't actually call {{Verify#verify(long)}} like the
{{Loop}} Tool does. Granted, it doesn't know the total number of KVs that
were written given the current arguments, it's not even checking to see if
there things like UNDEFINED records found.
It seems to me that {{Verify}} should really be doing *some* checking on the
counters like {{Loop}} does and not just leaving it up to the visual
inspection of whomever launched the task.
Am I missing something?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
