[jira] [Updated] (HIVE-3631) script_pipe.q fails when using JDK7

2013-05-06 Thread Owen O'Malley (JIRA)

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

Owen O'Malley updated HIVE-3631:


Fix Version/s: (was: 0.11.0)

 script_pipe.q fails when using JDK7
 ---

 Key: HIVE-3631
 URL: https://issues.apache.org/jira/browse/HIVE-3631
 Project: Hive
  Issue Type: Bug
  Components: Tests
Affects Versions: 0.10.0, 0.9.1, 0.11.0
Reporter: Chris Drome
Assignee: Chris Drome
 Attachments: HIVE-3631-0.10.patch, HIVE-3631-0.9.patch, 
 HIVE-3631-trunk.patch


 Hive Runtime Error while closing operators: Hit error while closing ..
 The MR job fails on this test. Unfortunately, the exception is not all that 
 helpful.
 I tracked this down to a class which attempts to close a stream that is 
 already closed. Broken pipe exceptions are caught and not propagated further, 
 but stream closed exception are not caught.

--
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] (HIVE-3631) script_pipe.q fails when using JDK7

2013-05-06 Thread Owen O'Malley (JIRA)

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

Owen O'Malley updated HIVE-3631:


   Resolution: Fixed
Fix Version/s: 0.11.0
   Status: Resolved  (was: Patch Available)

Probably won't make 0.9 or 0.10 releases.

 script_pipe.q fails when using JDK7
 ---

 Key: HIVE-3631
 URL: https://issues.apache.org/jira/browse/HIVE-3631
 Project: Hive
  Issue Type: Bug
  Components: Tests
Affects Versions: 0.10.0, 0.9.1, 0.11.0
Reporter: Chris Drome
Assignee: Chris Drome
 Fix For: 0.11.0

 Attachments: HIVE-3631-0.10.patch, HIVE-3631-0.9.patch, 
 HIVE-3631-trunk.patch


 Hive Runtime Error while closing operators: Hit error while closing ..
 The MR job fails on this test. Unfortunately, the exception is not all that 
 helpful.
 I tracked this down to a class which attempts to close a stream that is 
 already closed. Broken pipe exceptions are caught and not propagated further, 
 but stream closed exception are not caught.

--
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] (HIVE-3631) script_pipe.q fails when using JDK7

2013-01-03 Thread Chris Drome (JIRA)

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

Chris Drome updated HIVE-3631:
--

Attachment: HIVE-3631-0.10.patch

Added patch for branch-0.10

 script_pipe.q fails when using JDK7
 ---

 Key: HIVE-3631
 URL: https://issues.apache.org/jira/browse/HIVE-3631
 Project: Hive
  Issue Type: Bug
  Components: Tests
Affects Versions: 0.10.0, 0.9.1
Reporter: Chris Drome
Assignee: Chris Drome
 Fix For: 0.11.0

 Attachments: HIVE-3631-0.10.patch, HIVE-3631-0.9.patch, 
 HIVE-3631-trunk.patch


 Hive Runtime Error while closing operators: Hit error while closing ..
 The MR job fails on this test. Unfortunately, the exception is not all that 
 helpful.
 I tracked this down to a class which attempts to close a stream that is 
 already closed. Broken pipe exceptions are caught and not propagated further, 
 but stream closed exception are not caught.

--
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] (HIVE-3631) script_pipe.q fails when using JDK7

2013-01-03 Thread Chris Drome (JIRA)

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

Chris Drome updated HIVE-3631:
--

Affects Version/s: 0.11.0
   Status: Patch Available  (was: Reopened)

Please apply this patch to branch-0.9 and branch-0.10 as well.

 script_pipe.q fails when using JDK7
 ---

 Key: HIVE-3631
 URL: https://issues.apache.org/jira/browse/HIVE-3631
 Project: Hive
  Issue Type: Bug
  Components: Tests
Affects Versions: 0.10.0, 0.9.1, 0.11.0
Reporter: Chris Drome
Assignee: Chris Drome
 Fix For: 0.11.0

 Attachments: HIVE-3631-0.10.patch, HIVE-3631-0.9.patch, 
 HIVE-3631-trunk.patch


 Hive Runtime Error while closing operators: Hit error while closing ..
 The MR job fails on this test. Unfortunately, the exception is not all that 
 helpful.
 I tracked this down to a class which attempts to close a stream that is 
 already closed. Broken pipe exceptions are caught and not propagated further, 
 but stream closed exception are not caught.

--
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] (HIVE-3631) script_pipe.q fails when using JDK7

2012-11-21 Thread Chris Drome (JIRA)

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

Chris Drome updated HIVE-3631:
--

Attachment: HIVE-3631-trunk.patch
HIVE-3631-0.9.patch

Attached branch 0.9 and trunk patches.

 script_pipe.q fails when using JDK7
 ---

 Key: HIVE-3631
 URL: https://issues.apache.org/jira/browse/HIVE-3631
 Project: Hive
  Issue Type: Bug
  Components: Tests
Affects Versions: 0.10.0, 0.9.1
Reporter: Chris Drome
Assignee: Chris Drome
 Attachments: HIVE-3631-0.9.patch, HIVE-3631-trunk.patch


 Hive Runtime Error while closing operators: Hit error while closing ..
 The MR job fails on this test. Unfortunately, the exception is not all that 
 helpful.
 I tracked this down to a class which attempts to close a stream that is 
 already closed. Broken pipe exceptions are caught and not propagated further, 
 but stream closed exception are not caught.

--
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