[jira] [Updated] (HDFS-4002) Tool-ize OfflineImageViewer and make sure it returns proper return codes upon exit

2014-09-14 Thread Allen Wittenauer (JIRA)

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

Allen Wittenauer updated HDFS-4002:
---
Fix Version/s: (was: 3.0.0)

 Tool-ize OfflineImageViewer and make sure it returns proper return codes upon 
 exit
 --

 Key: HDFS-4002
 URL: https://issues.apache.org/jira/browse/HDFS-4002
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: tools
Affects Versions: 2.0.0-alpha
Reporter: Harsh J
Assignee: Stephen Chu
Priority: Minor
  Labels: newbie
 Attachments: HDFS-4002.patch.trunk


 We should make OfflineImageViewer structured (code-wise) in the same way as 
 OfflineEditsViewer is. Particularly, OIV must implement the Tool interface, 
 and must return proper exit codes upon success/failure conditions. Right now, 
 it returns 0 in both successful parse and unsuccessful ones.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HDFS-4002) Tool-ize OfflineImageViewer and make sure it returns proper return codes upon exit

2012-11-06 Thread Stephen Chu (JIRA)

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

Stephen Chu updated HDFS-4002:
--

Status: Open  (was: Patch Available)

Removing the 3 members is not necessary for toolizing, so I'm going to upload a 
new patch leaving them in.

 Tool-ize OfflineImageViewer and make sure it returns proper return codes upon 
 exit
 --

 Key: HDFS-4002
 URL: https://issues.apache.org/jira/browse/HDFS-4002
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: tools
Affects Versions: 2.0.0-alpha
Reporter: Harsh J
Assignee: Stephen Chu
Priority: Minor
  Labels: newbie
 Fix For: 3.0.0

 Attachments: HDFS-4002.patch.trunk


 We should make OfflineImageViewer structured (code-wise) in the same way as 
 OfflineEditsViewer is. Particularly, OIV must implement the Tool interface, 
 and must return proper exit codes upon success/failure conditions. Right now, 
 it returns 0 in both successful parse and unsuccessful ones.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (HDFS-4002) Tool-ize OfflineImageViewer and make sure it returns proper return codes upon exit

2012-10-19 Thread Stephen Chu (JIRA)

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

Stephen Chu updated HDFS-4002:
--

Attachment: HDFS-4002.patch.trunk

Submitted a patch for trunk.

OIV now implements the Tool interface.

I added unit tests to test the command line arguments and verify return codes 
for successful and unsuccessful parse.

I manually tested the OIV using all the processors.

 Tool-ize OfflineImageViewer and make sure it returns proper return codes upon 
 exit
 --

 Key: HDFS-4002
 URL: https://issues.apache.org/jira/browse/HDFS-4002
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: tools
Affects Versions: 2.0.0-alpha
Reporter: Harsh J
Assignee: Stephen Chu
Priority: Minor
  Labels: newbie
 Fix For: 3.0.0

 Attachments: HDFS-4002.patch.trunk


 We should make OfflineImageViewer structured (code-wise) in the same way as 
 OfflineEditsViewer is. Particularly, OIV must implement the Tool interface, 
 and must return proper exit codes upon success/failure conditions. Right now, 
 it returns 0 in both successful parse and unsuccessful ones.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (HDFS-4002) Tool-ize OfflineImageViewer and make sure it returns proper return codes upon exit

2012-10-19 Thread Stephen Chu (JIRA)

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

Stephen Chu updated HDFS-4002:
--

Fix Version/s: 3.0.0

 Tool-ize OfflineImageViewer and make sure it returns proper return codes upon 
 exit
 --

 Key: HDFS-4002
 URL: https://issues.apache.org/jira/browse/HDFS-4002
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: tools
Affects Versions: 2.0.0-alpha
Reporter: Harsh J
Assignee: Stephen Chu
Priority: Minor
  Labels: newbie
 Fix For: 3.0.0

 Attachments: HDFS-4002.patch.trunk


 We should make OfflineImageViewer structured (code-wise) in the same way as 
 OfflineEditsViewer is. Particularly, OIV must implement the Tool interface, 
 and must return proper exit codes upon success/failure conditions. Right now, 
 it returns 0 in both successful parse and unsuccessful ones.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (HDFS-4002) Tool-ize OfflineImageViewer and make sure it returns proper return codes upon exit

2012-10-19 Thread Stephen Chu (JIRA)

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

Stephen Chu updated HDFS-4002:
--

Status: Patch Available  (was: Open)

 Tool-ize OfflineImageViewer and make sure it returns proper return codes upon 
 exit
 --

 Key: HDFS-4002
 URL: https://issues.apache.org/jira/browse/HDFS-4002
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: tools
Affects Versions: 2.0.0-alpha
Reporter: Harsh J
Assignee: Stephen Chu
Priority: Minor
  Labels: newbie
 Fix For: 3.0.0

 Attachments: HDFS-4002.patch.trunk


 We should make OfflineImageViewer structured (code-wise) in the same way as 
 OfflineEditsViewer is. Particularly, OIV must implement the Tool interface, 
 and must return proper exit codes upon success/failure conditions. Right now, 
 it returns 0 in both successful parse and unsuccessful ones.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira