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

Sean Mackrory reassigned BIGTOP-962:
------------------------------------

    Assignee: Sean Mackrory
    
> Bump Sqoop version to 1.99.2
> ----------------------------
>
>                 Key: BIGTOP-962
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-962
>             Project: Bigtop
>          Issue Type: Sub-task
>          Components: Debian, General, RPM
>    Affects Versions: 0.6.0
>            Reporter: Mark Grover
>            Assignee: Sean Mackrory
>            Priority: Blocker
>             Fix For: 0.6.0
>
>
> I would like us to consider bumping version of Sqoop in Bigtop trunk (and 
> Bigtop 0.6) from 1.99.1 to 1.99.2. Here's why:
> As a part of BIGTOP-949, I started playing around with Sqoop in Bigtop trunk. 
> During this process, I found out that even simple commands like {{show 
> connector --all}} fail with an error like:
> {code}
> Exception has occurred during processing command 
> Exception: com.sun.jersey.api.client.UniformInterfaceException Message: GET 
> http://localhost:8080/sqoop/v1/connector/all returned a response status of 
> 400 Bad Request
> {code}
> It turns out that Sqoop's tomcat is trying to bind to port 8080 but MR2 uses 
> the same port 8080 for its shuffle manager (via a property called 
> {{mapreduce.shuffle.port}}), hence the error.
> This makes Sqoop unusable on Bigtop trunk and there not much point in writing 
> integration tests for it. The upstream Sqoop JIRA (SQOOP-881) resolves this 
> issue and changes the default Tomcat port to 12000. However, the first 
> release of Sqoop that contains this fix is 1.99.2. Morever, 1.99.2 contains 
> other many other improvements related to Sqoop2.
> Given the usability of current Sqoop version in trunk, I would suggest we 
> bump up the sqoop version from 1.99.1 to 1.99.2 for Bigtop 0.6. Sorry for the 
> late timing of this request. I would love to hear your thoughts or concerns 
> here, so please share!

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

Reply via email to