You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Wing Yew Poon (JIRA)" <ji...@apache.org> on 2012/07/19 23:09:33 UTC

[jira] [Created] (BIGTOP-678) make hive TestJdbcDriver more robust

Wing Yew Poon created BIGTOP-678:
------------------------------------

             Summary: make hive TestJdbcDriver more robust
                 Key: BIGTOP-678
                 URL: https://issues.apache.org/jira/browse/BIGTOP-678
             Project: Bigtop
          Issue Type: Improvement
          Components: Tests
    Affects Versions: 0.3.0, 0.4.0
            Reporter: Wing Yew Poon
            Assignee: Wing Yew Poon
             Fix For: 0.5.0


I plan to attach a patch to make TestJdbcDriver more robust, by parameterizing the wait time for the hive server to be up (it is currently hardcoded to 1 second, which may not be long enough) and by introducing a timeout to the test method (in my experience, if for some reason hive is not up or otherwise able to respond successfully, the test hangs).


--
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] (BIGTOP-678) make hive TestJdbcDriver more robust

Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BIGTOP-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Shaposhnik updated BIGTOP-678:
------------------------------------

    Fix Version/s:     (was: 0.5.0)
                   0.4.0
    
> make hive TestJdbcDriver more robust
> ------------------------------------
>
>                 Key: BIGTOP-678
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-678
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 0.3.0, 0.4.0
>            Reporter: Wing Yew Poon
>            Assignee: Wing Yew Poon
>             Fix For: 0.4.0
>
>         Attachments: BIGTOP-678.txt
>
>
> I plan to attach a patch to make TestJdbcDriver more robust, by parameterizing the wait time for the hive server to be up (it is currently hardcoded to 1 second, which may not be long enough) and by introducing a timeout to the test method (in my experience, if for some reason hive is not up or otherwise able to respond successfully, the test hangs).

--
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] (BIGTOP-678) make hive TestJdbcDriver more robust

Posted by "Wing Yew Poon (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BIGTOP-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wing Yew Poon updated BIGTOP-678:
---------------------------------

    Attachment: BIGTOP-678.txt
    
> make hive TestJdbcDriver more robust
> ------------------------------------
>
>                 Key: BIGTOP-678
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-678
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 0.3.0, 0.4.0
>            Reporter: Wing Yew Poon
>            Assignee: Wing Yew Poon
>             Fix For: 0.5.0
>
>         Attachments: BIGTOP-678.txt
>
>
> I plan to attach a patch to make TestJdbcDriver more robust, by parameterizing the wait time for the hive server to be up (it is currently hardcoded to 1 second, which may not be long enough) and by introducing a timeout to the test method (in my experience, if for some reason hive is not up or otherwise able to respond successfully, the test hangs).

--
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] [Comment Edited] (BIGTOP-678) make hive TestJdbcDriver more robust

Posted by "Bruno Mahé (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418946#comment-13418946 ] 

Bruno Mahé edited comment on BIGTOP-678 at 7/20/12 6:03 AM:
------------------------------------------------------------

+1.
But wouldn't it have been easier to use Integer.getInteger(value, default) and make 1000 and the property name constants?
                
      was (Author: bmahe):
    +1.
But wouldn't it have been easier to use Integer.getInteger(value, default) and make 1000 a constant?
                  
> make hive TestJdbcDriver more robust
> ------------------------------------
>
>                 Key: BIGTOP-678
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-678
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 0.3.0, 0.4.0
>            Reporter: Wing Yew Poon
>            Assignee: Wing Yew Poon
>             Fix For: 0.5.0
>
>         Attachments: BIGTOP-678.txt
>
>
> I plan to attach a patch to make TestJdbcDriver more robust, by parameterizing the wait time for the hive server to be up (it is currently hardcoded to 1 second, which may not be long enough) and by introducing a timeout to the test method (in my experience, if for some reason hive is not up or otherwise able to respond successfully, the test hangs).

--
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] [Closed] (BIGTOP-678) make hive TestJdbcDriver more robust

Posted by "Bruno Mahé (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BIGTOP-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruno Mahé closed BIGTOP-678.
-----------------------------

    
> make hive TestJdbcDriver more robust
> ------------------------------------
>
>                 Key: BIGTOP-678
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-678
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 0.3.0, 0.4.0
>            Reporter: Wing Yew Poon
>            Assignee: Wing Yew Poon
>             Fix For: 0.5.0
>
>         Attachments: BIGTOP-678.txt
>
>
> I plan to attach a patch to make TestJdbcDriver more robust, by parameterizing the wait time for the hive server to be up (it is currently hardcoded to 1 second, which may not be long enough) and by introducing a timeout to the test method (in my experience, if for some reason hive is not up or otherwise able to respond successfully, the test hangs).

--
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] [Commented] (BIGTOP-678) make hive TestJdbcDriver more robust

Posted by "Wing Yew Poon (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418971#comment-13418971 ] 

Wing Yew Poon commented on BIGTOP-678:
--------------------------------------

Bruno, on second thoughts, I think I'd leave it the way it is for now. Using Integer.getInteger(String, int) would indeed be easier. However, using System.getProperty(String) makes it easier later to find all the properties used by the tests. Right now, we don't have a way in the tests to specify a contract, in particular, what are the inputs (possibly optional) to a test, which typically is done by setting system properties. Until we have some kind of annotation or other way (even just a convention) for specifying such a contract, I'd leave the property in a System.getProperty(String) call.
                
> make hive TestJdbcDriver more robust
> ------------------------------------
>
>                 Key: BIGTOP-678
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-678
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 0.3.0, 0.4.0
>            Reporter: Wing Yew Poon
>            Assignee: Wing Yew Poon
>             Fix For: 0.5.0
>
>         Attachments: BIGTOP-678.txt
>
>
> I plan to attach a patch to make TestJdbcDriver more robust, by parameterizing the wait time for the hive server to be up (it is currently hardcoded to 1 second, which may not be long enough) and by introducing a timeout to the test method (in my experience, if for some reason hive is not up or otherwise able to respond successfully, the test hangs).

--
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] [Commented] (BIGTOP-678) make hive TestJdbcDriver more robust

Posted by "Wing Yew Poon (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13422743#comment-13422743 ] 

Wing Yew Poon commented on BIGTOP-678:
--------------------------------------

Bruno, I'd like this issue to be closed. I am addressing the issue of how to deal with system properties elsewhere, in BIGTOP-685.
                
> make hive TestJdbcDriver more robust
> ------------------------------------
>
>                 Key: BIGTOP-678
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-678
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 0.3.0, 0.4.0
>            Reporter: Wing Yew Poon
>            Assignee: Wing Yew Poon
>             Fix For: 0.5.0
>
>         Attachments: BIGTOP-678.txt
>
>
> I plan to attach a patch to make TestJdbcDriver more robust, by parameterizing the wait time for the hive server to be up (it is currently hardcoded to 1 second, which may not be long enough) and by introducing a timeout to the test method (in my experience, if for some reason hive is not up or otherwise able to respond successfully, the test hangs).

--
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] [Commented] (BIGTOP-678) make hive TestJdbcDriver more robust

Posted by "Wing Yew Poon (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418671#comment-13418671 ] 

Wing Yew Poon commented on BIGTOP-678:
--------------------------------------

I also used "drop table if exists" instead of "drop table".
                
> make hive TestJdbcDriver more robust
> ------------------------------------
>
>                 Key: BIGTOP-678
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-678
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 0.3.0, 0.4.0
>            Reporter: Wing Yew Poon
>            Assignee: Wing Yew Poon
>             Fix For: 0.5.0
>
>         Attachments: BIGTOP-678.txt
>
>
> I plan to attach a patch to make TestJdbcDriver more robust, by parameterizing the wait time for the hive server to be up (it is currently hardcoded to 1 second, which may not be long enough) and by introducing a timeout to the test method (in my experience, if for some reason hive is not up or otherwise able to respond successfully, the test hangs).

--
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] [Commented] (BIGTOP-678) make hive TestJdbcDriver more robust

Posted by "Bruno Mahé (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418946#comment-13418946 ] 

Bruno Mahé commented on BIGTOP-678:
-----------------------------------

+1.
But wouldn't it have been easier to use Integer.getInteger(value, default) and make 1000 a constant?
                
> make hive TestJdbcDriver more robust
> ------------------------------------
>
>                 Key: BIGTOP-678
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-678
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 0.3.0, 0.4.0
>            Reporter: Wing Yew Poon
>            Assignee: Wing Yew Poon
>             Fix For: 0.5.0
>
>         Attachments: BIGTOP-678.txt
>
>
> I plan to attach a patch to make TestJdbcDriver more robust, by parameterizing the wait time for the hive server to be up (it is currently hardcoded to 1 second, which may not be long enough) and by introducing a timeout to the test method (in my experience, if for some reason hive is not up or otherwise able to respond successfully, the test hangs).

--
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] [Comment Edited] (BIGTOP-678) make hive TestJdbcDriver more robust

Posted by "Wing Yew Poon (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418955#comment-13418955 ] 

Wing Yew Poon edited comment on BIGTOP-678 at 7/20/12 6:42 AM:
---------------------------------------------------------------

Bruno, sure, I was about to upload a new patch with your suggestion to use Integer.getInteger(String property, int default) when you closed this.

                
      was (Author: wypoon):
    Bruno, sure, I was about to upload a new patch with your suggestion to Integer.getInteger(String property, int default) when you closed this. I think it is overkill to make 1000 a constant since it is used just once.

                  
> make hive TestJdbcDriver more robust
> ------------------------------------
>
>                 Key: BIGTOP-678
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-678
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 0.3.0, 0.4.0
>            Reporter: Wing Yew Poon
>            Assignee: Wing Yew Poon
>             Fix For: 0.5.0
>
>         Attachments: BIGTOP-678.txt
>
>
> I plan to attach a patch to make TestJdbcDriver more robust, by parameterizing the wait time for the hive server to be up (it is currently hardcoded to 1 second, which may not be long enough) and by introducing a timeout to the test method (in my experience, if for some reason hive is not up or otherwise able to respond successfully, the test hangs).

--
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] [Closed] (BIGTOP-678) make hive TestJdbcDriver more robust

Posted by "Bruno Mahé (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BIGTOP-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruno Mahé closed BIGTOP-678.
-----------------------------

    
> make hive TestJdbcDriver more robust
> ------------------------------------
>
>                 Key: BIGTOP-678
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-678
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 0.3.0, 0.4.0
>            Reporter: Wing Yew Poon
>            Assignee: Wing Yew Poon
>             Fix For: 0.5.0
>
>         Attachments: BIGTOP-678.txt
>
>
> I plan to attach a patch to make TestJdbcDriver more robust, by parameterizing the wait time for the hive server to be up (it is currently hardcoded to 1 second, which may not be long enough) and by introducing a timeout to the test method (in my experience, if for some reason hive is not up or otherwise able to respond successfully, the test hangs).

--
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] [Commented] (BIGTOP-678) make hive TestJdbcDriver more robust

Posted by "Bruno Mahé (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418972#comment-13418972 ] 

Bruno Mahé commented on BIGTOP-678:
-----------------------------------

What about wrapping it in a util function or something similar? If we get this sort of code all over the place, it is not going to be very easy to follow.
                
> make hive TestJdbcDriver more robust
> ------------------------------------
>
>                 Key: BIGTOP-678
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-678
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 0.3.0, 0.4.0
>            Reporter: Wing Yew Poon
>            Assignee: Wing Yew Poon
>             Fix For: 0.5.0
>
>         Attachments: BIGTOP-678.txt
>
>
> I plan to attach a patch to make TestJdbcDriver more robust, by parameterizing the wait time for the hive server to be up (it is currently hardcoded to 1 second, which may not be long enough) and by introducing a timeout to the test method (in my experience, if for some reason hive is not up or otherwise able to respond successfully, the test hangs).

--
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] [Commented] (BIGTOP-678) make hive TestJdbcDriver more robust

Posted by "Bruno Mahé (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418960#comment-13418960 ] 

Bruno Mahé commented on BIGTOP-678:
-----------------------------------

I just reopened the ticket so you can update your patch :)
                
> make hive TestJdbcDriver more robust
> ------------------------------------
>
>                 Key: BIGTOP-678
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-678
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 0.3.0, 0.4.0
>            Reporter: Wing Yew Poon
>            Assignee: Wing Yew Poon
>             Fix For: 0.5.0
>
>         Attachments: BIGTOP-678.txt
>
>
> I plan to attach a patch to make TestJdbcDriver more robust, by parameterizing the wait time for the hive server to be up (it is currently hardcoded to 1 second, which may not be long enough) and by introducing a timeout to the test method (in my experience, if for some reason hive is not up or otherwise able to respond successfully, the test hangs).

--
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] [Commented] (BIGTOP-678) make hive TestJdbcDriver more robust

Posted by "Wing Yew Poon (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13419393#comment-13419393 ] 

Wing Yew Poon commented on BIGTOP-678:
--------------------------------------

What I meant was that, afaik, tests that use or depend on system properties or environment variables to parameterize behavior contain System.getProperty() or System.getenv() calls, so we can currently determine what the set of properties and variables are by grepping for System.getProperty and System.getenv in the test code. If instead, I start using Integer.getInteger(), then that would be one more (less obvious) thing to keep track of to grep for. You can imagine at least writing a tool (script) to come up with the "contract" (set of properties and variables) even in the current imperfect state of things. Changing the code to use Integer.getInteger() makes writing this tool a little more complex.

                
> make hive TestJdbcDriver more robust
> ------------------------------------
>
>                 Key: BIGTOP-678
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-678
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 0.3.0, 0.4.0
>            Reporter: Wing Yew Poon
>            Assignee: Wing Yew Poon
>             Fix For: 0.5.0
>
>         Attachments: BIGTOP-678.txt
>
>
> I plan to attach a patch to make TestJdbcDriver more robust, by parameterizing the wait time for the hive server to be up (it is currently hardcoded to 1 second, which may not be long enough) and by introducing a timeout to the test method (in my experience, if for some reason hive is not up or otherwise able to respond successfully, the test hangs).

--
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] [Commented] (BIGTOP-678) make hive TestJdbcDriver more robust

Posted by "Bruno Mahé (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13419920#comment-13419920 ] 

Bruno Mahé commented on BIGTOP-678:
-----------------------------------

What I meant was that, being able to grep on the properties being used is fair.
But if the cost of it is to have such template copy/pasted in such form all over the place, I am not sure I will go along. It's fine for a one time patch, but wouldn't work if applied to the whole code base.
Hence my suggestion to refactor it or to wrap it up in a util function you could grep on as well.

                
> make hive TestJdbcDriver more robust
> ------------------------------------
>
>                 Key: BIGTOP-678
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-678
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 0.3.0, 0.4.0
>            Reporter: Wing Yew Poon
>            Assignee: Wing Yew Poon
>             Fix For: 0.5.0
>
>         Attachments: BIGTOP-678.txt
>
>
> I plan to attach a patch to make TestJdbcDriver more robust, by parameterizing the wait time for the hive server to be up (it is currently hardcoded to 1 second, which may not be long enough) and by introducing a timeout to the test method (in my experience, if for some reason hive is not up or otherwise able to respond successfully, the test hangs).

--
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] [Commented] (BIGTOP-678) make hive TestJdbcDriver more robust

Posted by "Wing Yew Poon (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418955#comment-13418955 ] 

Wing Yew Poon commented on BIGTOP-678:
--------------------------------------

Bruno, sure, I was about to upload a new patch with your suggestion to Integer.getInteger(String property, int default) when you closed this. I think it is overkill to make 1000 a constant since it is used just once.

                
> make hive TestJdbcDriver more robust
> ------------------------------------
>
>                 Key: BIGTOP-678
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-678
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 0.3.0, 0.4.0
>            Reporter: Wing Yew Poon
>            Assignee: Wing Yew Poon
>             Fix For: 0.5.0
>
>         Attachments: BIGTOP-678.txt
>
>
> I plan to attach a patch to make TestJdbcDriver more robust, by parameterizing the wait time for the hive server to be up (it is currently hardcoded to 1 second, which may not be long enough) and by introducing a timeout to the test method (in my experience, if for some reason hive is not up or otherwise able to respond successfully, the test hangs).

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