FAQ
Hi,

Sqoop App in hue is unresponsive while sqoop2 is running fine,


[cloudera@localhost pawan]$ wget -qO - localhost:12000/sqoop/version
{"revision":"","protocols":["1"],"date":"Mon May 27 20:29:47 PDT
2013","user":"jenkins","url":"git:\/\/ubuntu-slave02\/var\/lib\/jenkins\/workspace\/CDH4.3.0-Packaging-Sqoop2\/build\/cdh4\/sqoop2\/1.99.1-cdh4.3.0\/source\/common","version":"1.99.1-cdh4.3.0"}

looking at the logs i found that:

*HUE LOG:

*[11/Oct/2013 07:05:50 +0000] http_client DEBUG *GET
http://localhost:12000/sqoop/v1/submission/history/all*
[11/Oct/2013 07:05:50 +0000] middleware INFO Processing exception:
'HTTPError' object has no attribute 'reason': Traceback (most recent call
last):
   File
"/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/core/handlers/base.py",
line 100, in get_response
     response = callback(request, *callback_args, **callback_kwargs)
   File
"/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
line 69, in _wrapped_view_func
     response = view_func(request, *args, **kwargs)
   File
"/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
60, in submissions
     return get_submissions(request)
   File
"/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
line 69, in _wrapped_view_func
     response = view_func(request, *args, **kwargs)
   File
"/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
54, in get_submissions
     response.update(handle_rest_exception(e, _('Could not get
submissions.')))
   File
"/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/exception.py", line
31, in handle_rest_exception
     reason = e.get_parent_ex().reason
AttributeError: 'HTTPError' object has no attribute 'reason'




*Sqoop LOG:

*2013-10-11 10:05:50,843 ERROR server.SqoopProtocolServlet
[org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:53)]
*Exception in GET http://localhost:12000/sqoop/v1/submission/history/all*
org.apache.sqoop.common.SqoopException: SERVER_0003:Invalid HTTP request -
Do not know what to do.
     at
org.apache.sqoop.handler.SubmissionRequestHandler.handleEvent(SubmissionRequestHandler.java:75)
     at
org.apache.sqoop.server.v1.SubmissionServlet.handleGetRequest(SubmissionServlet.java:39)
     at
org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:48)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
     at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
     at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
     at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
     at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
     at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
     at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
     at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
     at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
     at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
     at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
     at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
     at java.lang.Thread.run(Thread.java:662)*

*

--
*Thanks and Regards:*
Pawan Kumar Singh
Mob: +91- 9654515202

To unsubscribe from this group and stop receiving emails from it, send an email to hue-user+unsubscribe@cloudera.org.

Search Discussions

  • Romain Rigaux at Oct 11, 2013 at 2:46 pm
    Which Hue version are you using?

    I see cdh4.3.0 for Sqoop2. As Sqoop2 is quickly evolving and its API
    changing, the version needs to be CDH4.4 is using Hue 2.5.

    Romain

    On Fri, Oct 11, 2013 at 7:13 AM, pawan singh wrote:

    Hi,

    Sqoop App in hue is unresponsive while sqoop2 is running fine,


    [cloudera@localhost pawan]$ wget -qO - localhost:12000/sqoop/version
    {"revision":"","protocols":["1"],"date":"Mon May 27 20:29:47 PDT
    2013","user":"jenkins","url":"git:\/\/ubuntu-slave02\/var\/lib\/jenkins\/workspace\/CDH4.3.0-Packaging-Sqoop2\/build\/cdh4\/sqoop2\/1.99.1-cdh4.3.0\/source\/common","version":"1.99.1-cdh4.3.0"}

    looking at the logs i found that:

    *HUE LOG:

    *[11/Oct/2013 07:05:50 +0000] http_client DEBUG *GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    [11/Oct/2013 07:05:50 +0000] middleware INFO Processing exception:
    'HTTPError' object has no attribute 'reason': Traceback (most recent call
    last):
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/core/handlers/base.py",
    line 100, in get_response
    response = callback(request, *callback_args, **callback_kwargs)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    60, in submissions
    return get_submissions(request)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    54, in get_submissions
    response.update(handle_rest_exception(e, _('Could not get
    submissions.')))
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/exception.py", line
    31, in handle_rest_exception
    reason = e.get_parent_ex().reason
    AttributeError: 'HTTPError' object has no attribute 'reason'




    *Sqoop LOG:

    *2013-10-11 10:05:50,843 ERROR server.SqoopProtocolServlet
    [org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:53)]
    *Exception in GET http://localhost:12000/sqoop/v1/submission/history/all*
    org.apache.sqoop.common.SqoopException: SERVER_0003:Invalid HTTP request -
    Do not know what to do.
    at
    org.apache.sqoop.handler.SubmissionRequestHandler.handleEvent(SubmissionRequestHandler.java:75)
    at
    org.apache.sqoop.server.v1.SubmissionServlet.handleGetRequest(SubmissionServlet.java:39)
    at
    org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:48)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at
    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at
    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at
    org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at
    org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at
    org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at
    org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at
    org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at
    org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
    at
    org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
    at
    org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
    at
    org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    at java.lang.Thread.run(Thread.java:662)*

    *

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from it, send an
    email to hue-user+unsubscribe@cloudera.org.
    To unsubscribe from this group and stop receiving emails from it, send an email to hue-user+unsubscribe@cloudera.org.
  • Pawan singh at Oct 14, 2013 at 7:27 am
    Thanks Romain,

    That was the reason. How could we set job properties.

    On Fri, Oct 11, 2013 at 8:15 PM, Romain Rigaux wrote:

    Which Hue version are you using?

    I see cdh4.3.0 for Sqoop2. As Sqoop2 is quickly evolving and its API
    changing, the version needs to be CDH4.4 is using Hue 2.5.

    Romain

    On Fri, Oct 11, 2013 at 7:13 AM, pawan singh wrote:

    Hi,

    Sqoop App in hue is unresponsive while sqoop2 is running fine,


    [cloudera@localhost pawan]$ wget -qO - localhost:12000/sqoop/version
    {"revision":"","protocols":["1"],"date":"Mon May 27 20:29:47 PDT
    2013","user":"jenkins","url":"git:\/\/ubuntu-slave02\/var\/lib\/jenkins\/workspace\/CDH4.3.0-Packaging-Sqoop2\/build\/cdh4\/sqoop2\/1.99.1-cdh4.3.0\/source\/common","version":"1.99.1-cdh4.3.0"}

    looking at the logs i found that:

    *HUE LOG:

    *[11/Oct/2013 07:05:50 +0000] http_client DEBUG *GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    [11/Oct/2013 07:05:50 +0000] middleware INFO Processing exception:
    'HTTPError' object has no attribute 'reason': Traceback (most recent call
    last):
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/core/handlers/base.py",
    line 100, in get_response
    response = callback(request, *callback_args, **callback_kwargs)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    60, in submissions
    return get_submissions(request)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    54, in get_submissions
    response.update(handle_rest_exception(e, _('Could not get
    submissions.')))
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/exception.py", line
    31, in handle_rest_exception
    reason = e.get_parent_ex().reason
    AttributeError: 'HTTPError' object has no attribute 'reason'




    *Sqoop LOG:

    *2013-10-11 10:05:50,843 ERROR server.SqoopProtocolServlet
    [org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:53)]
    *Exception in GET http://localhost:12000/sqoop/v1/submission/history/all*
    org.apache.sqoop.common.SqoopException: SERVER_0003:Invalid HTTP request
    - Do not know what to do.
    at
    org.apache.sqoop.handler.SubmissionRequestHandler.handleEvent(SubmissionRequestHandler.java:75)
    at
    org.apache.sqoop.server.v1.SubmissionServlet.handleGetRequest(SubmissionServlet.java:39)
    at
    org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:48)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at
    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at
    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at
    org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at
    org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at
    org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at
    org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at
    org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at
    org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
    at
    org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
    at
    org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
    at
    org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    at java.lang.Thread.run(Thread.java:662)*

    *

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from it, send an
    email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from it, send an email to hue-user+unsubscribe@cloudera.org.
  • Romain Rigaux at Oct 14, 2013 at 8:48 am
    Do you mean some Hadoop job properties from the Sqoop job?

    Romain

    On Mon, Oct 14, 2013 at 4:27 PM, pawan singh wrote:

    Thanks Romain,

    That was the reason. How could we set job properties.

    On Fri, Oct 11, 2013 at 8:15 PM, Romain Rigaux wrote:

    Which Hue version are you using?

    I see cdh4.3.0 for Sqoop2. As Sqoop2 is quickly evolving and its API
    changing, the version needs to be CDH4.4 is using Hue 2.5.

    Romain

    On Fri, Oct 11, 2013 at 7:13 AM, pawan singh wrote:

    Hi,

    Sqoop App in hue is unresponsive while sqoop2 is running fine,


    [cloudera@localhost pawan]$ wget -qO - localhost:12000/sqoop/version
    {"revision":"","protocols":["1"],"date":"Mon May 27 20:29:47 PDT
    2013","user":"jenkins","url":"git:\/\/ubuntu-slave02\/var\/lib\/jenkins\/workspace\/CDH4.3.0-Packaging-Sqoop2\/build\/cdh4\/sqoop2\/1.99.1-cdh4.3.0\/source\/common","version":"1.99.1-cdh4.3.0"}

    looking at the logs i found that:

    *HUE LOG:

    *[11/Oct/2013 07:05:50 +0000] http_client DEBUG *GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    [11/Oct/2013 07:05:50 +0000] middleware INFO Processing exception:
    'HTTPError' object has no attribute 'reason': Traceback (most recent call
    last):
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/core/handlers/base.py",
    line 100, in get_response
    response = callback(request, *callback_args, **callback_kwargs)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    60, in submissions
    return get_submissions(request)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    54, in get_submissions
    response.update(handle_rest_exception(e, _('Could not get
    submissions.')))
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/exception.py", line
    31, in handle_rest_exception
    reason = e.get_parent_ex().reason
    AttributeError: 'HTTPError' object has no attribute 'reason'




    *Sqoop LOG:

    *2013-10-11 10:05:50,843 ERROR server.SqoopProtocolServlet
    [org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:53)]
    *Exception in GET http://localhost:12000/sqoop/v1/submission/history/all
    *
    org.apache.sqoop.common.SqoopException: SERVER_0003:Invalid HTTP request
    - Do not know what to do.
    at
    org.apache.sqoop.handler.SubmissionRequestHandler.handleEvent(SubmissionRequestHandler.java:75)
    at
    org.apache.sqoop.server.v1.SubmissionServlet.handleGetRequest(SubmissionServlet.java:39)
    at
    org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:48)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at
    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at
    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at
    org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at
    org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at
    org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at
    org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at
    org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at
    org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
    at
    org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
    at
    org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
    at
    org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    at java.lang.Thread.run(Thread.java:662)*

    *

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from it, send
    an email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202
    To unsubscribe from this group and stop receiving emails from it, send an email to hue-user+unsubscribe@cloudera.org.
  • Pawan singh at Oct 14, 2013 at 11:57 am
    Yes. Hadoop Job properties for sqoop jobs.

    On Mon, Oct 14, 2013 at 2:17 PM, Romain Rigaux wrote:

    Do you mean some Hadoop job properties from the Sqoop job?

    Romain

    On Mon, Oct 14, 2013 at 4:27 PM, pawan singh wrote:

    Thanks Romain,

    That was the reason. How could we set job properties.

    On Fri, Oct 11, 2013 at 8:15 PM, Romain Rigaux wrote:

    Which Hue version are you using?

    I see cdh4.3.0 for Sqoop2. As Sqoop2 is quickly evolving and its API
    changing, the version needs to be CDH4.4 is using Hue 2.5.

    Romain

    On Fri, Oct 11, 2013 at 7:13 AM, pawan singh wrote:

    Hi,

    Sqoop App in hue is unresponsive while sqoop2 is running fine,


    [cloudera@localhost pawan]$ wget -qO - localhost:12000/sqoop/version
    {"revision":"","protocols":["1"],"date":"Mon May 27 20:29:47 PDT
    2013","user":"jenkins","url":"git:\/\/ubuntu-slave02\/var\/lib\/jenkins\/workspace\/CDH4.3.0-Packaging-Sqoop2\/build\/cdh4\/sqoop2\/1.99.1-cdh4.3.0\/source\/common","version":"1.99.1-cdh4.3.0"}

    looking at the logs i found that:

    *HUE LOG:

    *[11/Oct/2013 07:05:50 +0000] http_client DEBUG *GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    [11/Oct/2013 07:05:50 +0000] middleware INFO Processing
    exception: 'HTTPError' object has no attribute 'reason': Traceback (most
    recent call last):
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/core/handlers/base.py",
    line 100, in get_response
    response = callback(request, *callback_args, **callback_kwargs)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    60, in submissions
    return get_submissions(request)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    54, in get_submissions
    response.update(handle_rest_exception(e, _('Could not get
    submissions.')))
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/exception.py", line
    31, in handle_rest_exception
    reason = e.get_parent_ex().reason
    AttributeError: 'HTTPError' object has no attribute 'reason'




    *Sqoop LOG:

    *2013-10-11 10:05:50,843 ERROR server.SqoopProtocolServlet
    [org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:53)]
    *Exception in GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    org.apache.sqoop.common.SqoopException: SERVER_0003:Invalid HTTP
    request - Do not know what to do.
    at
    org.apache.sqoop.handler.SubmissionRequestHandler.handleEvent(SubmissionRequestHandler.java:75)
    at
    org.apache.sqoop.server.v1.SubmissionServlet.handleGetRequest(SubmissionServlet.java:39)
    at
    org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:48)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at
    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at
    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at
    org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at
    org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at
    org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at
    org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at
    org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at
    org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
    at
    org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
    at
    org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
    at
    org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    at java.lang.Thread.run(Thread.java:662)*

    *

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from it, send
    an email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from it, send an email to hue-user+unsubscribe@cloudera.org.
  • Abraham Elmahrek at Oct 14, 2013 at 5:38 pm
    What job property would you like to set? I don't think you can set Hadoop
    Job properties unfortunately... but that's a question for the sqoop mailing
    list user@sqoop.apache.org.

    -Abe

    On Mon, Oct 14, 2013 at 4:57 AM, pawan singh wrote:

    Yes. Hadoop Job properties for sqoop jobs.

    On Mon, Oct 14, 2013 at 2:17 PM, Romain Rigaux wrote:

    Do you mean some Hadoop job properties from the Sqoop job?

    Romain

    On Mon, Oct 14, 2013 at 4:27 PM, pawan singh wrote:

    Thanks Romain,

    That was the reason. How could we set job properties.

    On Fri, Oct 11, 2013 at 8:15 PM, Romain Rigaux wrote:

    Which Hue version are you using?

    I see cdh4.3.0 for Sqoop2. As Sqoop2 is quickly evolving and its API
    changing, the version needs to be CDH4.4 is using Hue 2.5.

    Romain

    On Fri, Oct 11, 2013 at 7:13 AM, pawan singh wrote:

    Hi,

    Sqoop App in hue is unresponsive while sqoop2 is running fine,


    [cloudera@localhost pawan]$ wget -qO - localhost:12000/sqoop/version
    {"revision":"","protocols":["1"],"date":"Mon May 27 20:29:47 PDT
    2013","user":"jenkins","url":"git:\/\/ubuntu-slave02\/var\/lib\/jenkins\/workspace\/CDH4.3.0-Packaging-Sqoop2\/build\/cdh4\/sqoop2\/1.99.1-cdh4.3.0\/source\/common","version":"1.99.1-cdh4.3.0"}

    looking at the logs i found that:

    *HUE LOG:

    *[11/Oct/2013 07:05:50 +0000] http_client DEBUG *GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    [11/Oct/2013 07:05:50 +0000] middleware INFO Processing
    exception: 'HTTPError' object has no attribute 'reason': Traceback (most
    recent call last):
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/core/handlers/base.py",
    line 100, in get_response
    response = callback(request, *callback_args, **callback_kwargs)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    60, in submissions
    return get_submissions(request)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    54, in get_submissions
    response.update(handle_rest_exception(e, _('Could not get
    submissions.')))
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/exception.py", line
    31, in handle_rest_exception
    reason = e.get_parent_ex().reason
    AttributeError: 'HTTPError' object has no attribute 'reason'




    *Sqoop LOG:

    *2013-10-11 10:05:50,843 ERROR server.SqoopProtocolServlet
    [org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:53)]
    *Exception in GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    org.apache.sqoop.common.SqoopException: SERVER_0003:Invalid HTTP
    request - Do not know what to do.
    at
    org.apache.sqoop.handler.SubmissionRequestHandler.handleEvent(SubmissionRequestHandler.java:75)
    at
    org.apache.sqoop.server.v1.SubmissionServlet.handleGetRequest(SubmissionServlet.java:39)
    at
    org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:48)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at
    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at
    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at
    org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at
    org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at
    org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at
    org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at
    org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at
    org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
    at
    org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
    at
    org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
    at
    org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    at java.lang.Thread.run(Thread.java:662)*

    *

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from it, send
    an email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from it, send an
    email to hue-user+unsubscribe@cloudera.org.
    To unsubscribe from this group and stop receiving emails from it, send an email to hue-user+unsubscribe@cloudera.org.
  • Pawan singh at Oct 14, 2013 at 6:02 pm
    Sqoop supports hadoop job properties with -D option, like job queue(
    mapred.job.queue.name)

    On Mon, Oct 14, 2013 at 11:08 PM, Abraham Elmahrek wrote:

    What job property would you like to set? I don't think you can set Hadoop
    Job properties unfortunately... but that's a question for the sqoop mailing
    list user@sqoop.apache.org.

    -Abe

    On Mon, Oct 14, 2013 at 4:57 AM, pawan singh wrote:

    Yes. Hadoop Job properties for sqoop jobs.

    On Mon, Oct 14, 2013 at 2:17 PM, Romain Rigaux wrote:

    Do you mean some Hadoop job properties from the Sqoop job?

    Romain

    On Mon, Oct 14, 2013 at 4:27 PM, pawan singh wrote:

    Thanks Romain,

    That was the reason. How could we set job properties.

    On Fri, Oct 11, 2013 at 8:15 PM, Romain Rigaux wrote:

    Which Hue version are you using?

    I see cdh4.3.0 for Sqoop2. As Sqoop2 is quickly evolving and its API
    changing, the version needs to be CDH4.4 is using Hue 2.5.

    Romain

    On Fri, Oct 11, 2013 at 7:13 AM, pawan singh wrote:

    Hi,

    Sqoop App in hue is unresponsive while sqoop2 is running fine,


    [cloudera@localhost pawan]$ wget -qO - localhost:12000/sqoop/version
    {"revision":"","protocols":["1"],"date":"Mon May 27 20:29:47 PDT
    2013","user":"jenkins","url":"git:\/\/ubuntu-slave02\/var\/lib\/jenkins\/workspace\/CDH4.3.0-Packaging-Sqoop2\/build\/cdh4\/sqoop2\/1.99.1-cdh4.3.0\/source\/common","version":"1.99.1-cdh4.3.0"}

    looking at the logs i found that:

    *HUE LOG:

    *[11/Oct/2013 07:05:50 +0000] http_client DEBUG *GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    [11/Oct/2013 07:05:50 +0000] middleware INFO Processing
    exception: 'HTTPError' object has no attribute 'reason': Traceback (most
    recent call last):
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/core/handlers/base.py",
    line 100, in get_response
    response = callback(request, *callback_args, **callback_kwargs)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    60, in submissions
    return get_submissions(request)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    54, in get_submissions
    response.update(handle_rest_exception(e, _('Could not get
    submissions.')))
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/exception.py", line
    31, in handle_rest_exception
    reason = e.get_parent_ex().reason
    AttributeError: 'HTTPError' object has no attribute 'reason'




    *Sqoop LOG:

    *2013-10-11 10:05:50,843 ERROR server.SqoopProtocolServlet
    [org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:53)]
    *Exception in GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    org.apache.sqoop.common.SqoopException: SERVER_0003:Invalid HTTP
    request - Do not know what to do.
    at
    org.apache.sqoop.handler.SubmissionRequestHandler.handleEvent(SubmissionRequestHandler.java:75)
    at
    org.apache.sqoop.server.v1.SubmissionServlet.handleGetRequest(SubmissionServlet.java:39)
    at
    org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:48)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at
    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at
    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at
    org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at
    org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at
    org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at
    org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at
    org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at
    org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
    at
    org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
    at
    org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
    at
    org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    at java.lang.Thread.run(Thread.java:662)*

    *

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from it,
    send an email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from it, send an
    email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from it, send an email to hue-user+unsubscribe@cloudera.org.
  • Abraham Elmahrek at Oct 14, 2013 at 6:03 pm
    Ah yes, but the difference is that we're using sqoop2, which does not
    support that. You may be able to add that to the sqoop server.

    -Abe

    On Mon, Oct 14, 2013 at 11:02 AM, pawan singh wrote:

    Sqoop supports hadoop job properties with -D option, like job queue(
    mapred.job.queue.name)

    On Mon, Oct 14, 2013 at 11:08 PM, Abraham Elmahrek wrote:

    What job property would you like to set? I don't think you can set Hadoop
    Job properties unfortunately... but that's a question for the sqoop mailing
    list user@sqoop.apache.org.

    -Abe

    On Mon, Oct 14, 2013 at 4:57 AM, pawan singh wrote:

    Yes. Hadoop Job properties for sqoop jobs.

    On Mon, Oct 14, 2013 at 2:17 PM, Romain Rigaux wrote:

    Do you mean some Hadoop job properties from the Sqoop job?

    Romain

    On Mon, Oct 14, 2013 at 4:27 PM, pawan singh wrote:

    Thanks Romain,

    That was the reason. How could we set job properties.

    On Fri, Oct 11, 2013 at 8:15 PM, Romain Rigaux wrote:

    Which Hue version are you using?

    I see cdh4.3.0 for Sqoop2. As Sqoop2 is quickly evolving and its API
    changing, the version needs to be CDH4.4 is using Hue 2.5.

    Romain

    On Fri, Oct 11, 2013 at 7:13 AM, pawan singh wrote:

    Hi,

    Sqoop App in hue is unresponsive while sqoop2 is running fine,


    [cloudera@localhost pawan]$ wget -qO -
    localhost:12000/sqoop/version
    {"revision":"","protocols":["1"],"date":"Mon May 27 20:29:47 PDT
    2013","user":"jenkins","url":"git:\/\/ubuntu-slave02\/var\/lib\/jenkins\/workspace\/CDH4.3.0-Packaging-Sqoop2\/build\/cdh4\/sqoop2\/1.99.1-cdh4.3.0\/source\/common","version":"1.99.1-cdh4.3.0"}

    looking at the logs i found that:

    *HUE LOG:

    *[11/Oct/2013 07:05:50 +0000] http_client DEBUG *GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    [11/Oct/2013 07:05:50 +0000] middleware INFO Processing
    exception: 'HTTPError' object has no attribute 'reason': Traceback (most
    recent call last):
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/core/handlers/base.py",
    line 100, in get_response
    response = callback(request, *callback_args, **callback_kwargs)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    60, in submissions
    return get_submissions(request)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    54, in get_submissions
    response.update(handle_rest_exception(e, _('Could not get
    submissions.')))
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/exception.py", line
    31, in handle_rest_exception
    reason = e.get_parent_ex().reason
    AttributeError: 'HTTPError' object has no attribute 'reason'




    *Sqoop LOG:

    *2013-10-11 10:05:50,843 ERROR server.SqoopProtocolServlet
    [org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:53)]
    *Exception in GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    org.apache.sqoop.common.SqoopException: SERVER_0003:Invalid HTTP
    request - Do not know what to do.
    at
    org.apache.sqoop.handler.SubmissionRequestHandler.handleEvent(SubmissionRequestHandler.java:75)
    at
    org.apache.sqoop.server.v1.SubmissionServlet.handleGetRequest(SubmissionServlet.java:39)
    at
    org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:48)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at
    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at
    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at
    org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at
    org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at
    org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at
    org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at
    org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at
    org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
    at
    org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
    at
    org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
    at
    org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    at java.lang.Thread.run(Thread.java:662)*

    *

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from it,
    send an email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from it, send
    an email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202
    To unsubscribe from this group and stop receiving emails from it, send an email to hue-user+unsubscribe@cloudera.org.
  • Abraham Elmahrek at Oct 14, 2013 at 6:41 pm
    Pawan,

    The Sqoop app in Hue is a front end for the Sqoop2 application. The sqoop1
    and sqoop2 applications differ greatly:

        1. Sqoop 2 is the successor to Sqoop 1.
        2. Sqoop 2 has a client - server architecture.
        3. MR jobs are submitted from the Sqoop server in Sqoop2. In Sqoop1,
        they are submitted from the client.
        4. Connectors are much lighter and generic components have been handled
        in the "framework" component of Sqoop 2.
        5. Sqoop 2 is intended on being more secure than Sqoop 1. It starts off
        by managing connections so that information isn't provided over the command
        line.

    The list really does go on... there are several improvements to the design
    in Sqoop 2.

    What this means is that Java arguments are no longer simply passed to the
    MR job from the client. This is intentionally done. I believe you can
    provide a custom start script for the server to add Java arguments and
    those will be passed to the MR job, though I'm unsure.

    What are you doing with Sqoop that requires Hadoop properties to be set?
    Your feedback is extremely important and can potentially impact project
    direction!

    -Abe

    On Mon, Oct 14, 2013 at 11:03 AM, Abraham Elmahrek wrote:

    Ah yes, but the difference is that we're using sqoop2, which does not
    support that. You may be able to add that to the sqoop server.

    -Abe

    On Mon, Oct 14, 2013 at 11:02 AM, pawan singh wrote:

    Sqoop supports hadoop job properties with -D option, like job queue(
    mapred.job.queue.name)

    On Mon, Oct 14, 2013 at 11:08 PM, Abraham Elmahrek wrote:

    What job property would you like to set? I don't think you can set
    Hadoop Job properties unfortunately... but that's a question for the sqoop
    mailing list user@sqoop.apache.org.

    -Abe

    On Mon, Oct 14, 2013 at 4:57 AM, pawan singh wrote:

    Yes. Hadoop Job properties for sqoop jobs.

    On Mon, Oct 14, 2013 at 2:17 PM, Romain Rigaux wrote:

    Do you mean some Hadoop job properties from the Sqoop job?

    Romain

    On Mon, Oct 14, 2013 at 4:27 PM, pawan singh wrote:

    Thanks Romain,

    That was the reason. How could we set job properties.

    On Fri, Oct 11, 2013 at 8:15 PM, Romain Rigaux wrote:

    Which Hue version are you using?

    I see cdh4.3.0 for Sqoop2. As Sqoop2 is quickly evolving and its API
    changing, the version needs to be CDH4.4 is using Hue 2.5.

    Romain


    On Fri, Oct 11, 2013 at 7:13 AM, pawan singh <jeet27.pawan@gmail.com
    wrote:
    Hi,

    Sqoop App in hue is unresponsive while sqoop2 is running fine,


    [cloudera@localhost pawan]$ wget -qO -
    localhost:12000/sqoop/version
    {"revision":"","protocols":["1"],"date":"Mon May 27 20:29:47 PDT
    2013","user":"jenkins","url":"git:\/\/ubuntu-slave02\/var\/lib\/jenkins\/workspace\/CDH4.3.0-Packaging-Sqoop2\/build\/cdh4\/sqoop2\/1.99.1-cdh4.3.0\/source\/common","version":"1.99.1-cdh4.3.0"}

    looking at the logs i found that:

    *HUE LOG:

    *[11/Oct/2013 07:05:50 +0000] http_client DEBUG *GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    [11/Oct/2013 07:05:50 +0000] middleware INFO Processing
    exception: 'HTTPError' object has no attribute 'reason': Traceback (most
    recent call last):
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/core/handlers/base.py",
    line 100, in get_response
    response = callback(request, *callback_args, **callback_kwargs)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    60, in submissions
    return get_submissions(request)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    54, in get_submissions
    response.update(handle_rest_exception(e, _('Could not get
    submissions.')))
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/exception.py", line
    31, in handle_rest_exception
    reason = e.get_parent_ex().reason
    AttributeError: 'HTTPError' object has no attribute 'reason'




    *Sqoop LOG:

    *2013-10-11 10:05:50,843 ERROR server.SqoopProtocolServlet
    [org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:53)]
    *Exception in GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    org.apache.sqoop.common.SqoopException: SERVER_0003:Invalid HTTP
    request - Do not know what to do.
    at
    org.apache.sqoop.handler.SubmissionRequestHandler.handleEvent(SubmissionRequestHandler.java:75)
    at
    org.apache.sqoop.server.v1.SubmissionServlet.handleGetRequest(SubmissionServlet.java:39)
    at
    org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:48)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at
    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at
    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at
    org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at
    org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at
    org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at
    org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at
    org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at
    org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
    at
    org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
    at
    org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
    at
    org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    at java.lang.Thread.run(Thread.java:662)*

    *

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from it,
    send an email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from it, send
    an email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202
    To unsubscribe from this group and stop receiving emails from it, send an email to hue-user+unsubscribe@cloudera.org.
  • Romain Rigaux at Oct 14, 2013 at 11:12 pm
    I think the idea is to have the MapReduce jobs being executed in a certain
    JT queue.

    Romain

    On Tue, Oct 15, 2013 at 3:41 AM, Abraham Elmahrek wrote:

    Pawan,

    The Sqoop app in Hue is a front end for the Sqoop2 application. The sqoop1
    and sqoop2 applications differ greatly:

    1. Sqoop 2 is the successor to Sqoop 1.
    2. Sqoop 2 has a client - server architecture.
    3. MR jobs are submitted from the Sqoop server in Sqoop2. In Sqoop1,
    they are submitted from the client.
    4. Connectors are much lighter and generic components have been
    handled in the "framework" component of Sqoop 2.
    5. Sqoop 2 is intended on being more secure than Sqoop 1. It starts
    off by managing connections so that information isn't provided over the
    command line.

    The list really does go on... there are several improvements to the design
    in Sqoop 2.

    What this means is that Java arguments are no longer simply passed to the
    MR job from the client. This is intentionally done. I believe you can
    provide a custom start script for the server to add Java arguments and
    those will be passed to the MR job, though I'm unsure.

    What are you doing with Sqoop that requires Hadoop properties to be set?
    Your feedback is extremely important and can potentially impact project
    direction!

    -Abe

    On Mon, Oct 14, 2013 at 11:03 AM, Abraham Elmahrek wrote:

    Ah yes, but the difference is that we're using sqoop2, which does not
    support that. You may be able to add that to the sqoop server.

    -Abe

    On Mon, Oct 14, 2013 at 11:02 AM, pawan singh wrote:

    Sqoop supports hadoop job properties with -D option, like job queue(
    mapred.job.queue.name)

    On Mon, Oct 14, 2013 at 11:08 PM, Abraham Elmahrek wrote:

    What job property would you like to set? I don't think you can set
    Hadoop Job properties unfortunately... but that's a question for the sqoop
    mailing list user@sqoop.apache.org.

    -Abe

    On Mon, Oct 14, 2013 at 4:57 AM, pawan singh wrote:

    Yes. Hadoop Job properties for sqoop jobs.

    On Mon, Oct 14, 2013 at 2:17 PM, Romain Rigaux wrote:

    Do you mean some Hadoop job properties from the Sqoop job?

    Romain

    On Mon, Oct 14, 2013 at 4:27 PM, pawan singh wrote:

    Thanks Romain,

    That was the reason. How could we set job properties.

    On Fri, Oct 11, 2013 at 8:15 PM, Romain Rigaux wrote:

    Which Hue version are you using?

    I see cdh4.3.0 for Sqoop2. As Sqoop2 is quickly evolving and its
    API changing, the version needs to be CDH4.4 is using Hue 2.5.

    Romain


    On Fri, Oct 11, 2013 at 7:13 AM, pawan singh <
    jeet27.pawan@gmail.com> wrote:
    Hi,

    Sqoop App in hue is unresponsive while sqoop2 is running fine,


    [cloudera@localhost pawan]$ wget -qO -
    localhost:12000/sqoop/version
    {"revision":"","protocols":["1"],"date":"Mon May 27 20:29:47 PDT
    2013","user":"jenkins","url":"git:\/\/ubuntu-slave02\/var\/lib\/jenkins\/workspace\/CDH4.3.0-Packaging-Sqoop2\/build\/cdh4\/sqoop2\/1.99.1-cdh4.3.0\/source\/common","version":"1.99.1-cdh4.3.0"}

    looking at the logs i found that:

    *HUE LOG:

    *[11/Oct/2013 07:05:50 +0000] http_client DEBUG *GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    [11/Oct/2013 07:05:50 +0000] middleware INFO Processing
    exception: 'HTTPError' object has no attribute 'reason': Traceback (most
    recent call last):
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/core/handlers/base.py",
    line 100, in get_response
    response = callback(request, *callback_args, **callback_kwargs)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    60, in submissions
    return get_submissions(request)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    54, in get_submissions
    response.update(handle_rest_exception(e, _('Could not get
    submissions.')))
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/exception.py", line
    31, in handle_rest_exception
    reason = e.get_parent_ex().reason
    AttributeError: 'HTTPError' object has no attribute 'reason'




    *Sqoop LOG:

    *2013-10-11 10:05:50,843 ERROR server.SqoopProtocolServlet
    [org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:53)]
    *Exception in GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    org.apache.sqoop.common.SqoopException: SERVER_0003:Invalid HTTP
    request - Do not know what to do.
    at
    org.apache.sqoop.handler.SubmissionRequestHandler.handleEvent(SubmissionRequestHandler.java:75)
    at
    org.apache.sqoop.server.v1.SubmissionServlet.handleGetRequest(SubmissionServlet.java:39)
    at
    org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:48)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at
    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at
    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at
    org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at
    org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at
    org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at
    org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at
    org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at
    org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
    at
    org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
    at
    org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
    at
    org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    at java.lang.Thread.run(Thread.java:662)*

    *

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from it,
    send an email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from it, send
    an email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202
    To unsubscribe from this group and stop receiving emails from it, send an email to hue-user+unsubscribe@cloudera.org.
  • Pawan singh at Oct 15, 2013 at 10:33 am
    Hi Romain/Abraham,

    Idea is of fair utilization of resources, I am not very sure about sqoop-2
    but hadoop properties were available with sqoop1.
    restricting reducers
    restricting mappers
    restricting job queue

    I believe these parameters should be configurable from client instead of
    server and it should be configurable though "framework".

    On Tue, Oct 15, 2013 at 4:41 AM, Romain Rigaux wrote:

    I think the idea is to have the MapReduce jobs being executed in a certain
    JT queue.

    Romain

    On Tue, Oct 15, 2013 at 3:41 AM, Abraham Elmahrek wrote:

    Pawan,

    The Sqoop app in Hue is a front end for the Sqoop2 application. The
    sqoop1 and sqoop2 applications differ greatly:

    1. Sqoop 2 is the successor to Sqoop 1.
    2. Sqoop 2 has a client - server architecture.
    3. MR jobs are submitted from the Sqoop server in Sqoop2. In Sqoop1,
    they are submitted from the client.
    4. Connectors are much lighter and generic components have been
    handled in the "framework" component of Sqoop 2.
    5. Sqoop 2 is intended on being more secure than Sqoop 1. It starts
    off by managing connections so that information isn't provided over the
    command line.

    The list really does go on... there are several improvements to the
    design in Sqoop 2.

    What this means is that Java arguments are no longer simply passed to the
    MR job from the client. This is intentionally done. I believe you can
    provide a custom start script for the server to add Java arguments and
    those will be passed to the MR job, though I'm unsure.

    What are you doing with Sqoop that requires Hadoop properties to be set?
    Your feedback is extremely important and can potentially impact project
    direction!

    -Abe

    On Mon, Oct 14, 2013 at 11:03 AM, Abraham Elmahrek wrote:

    Ah yes, but the difference is that we're using sqoop2, which does not
    support that. You may be able to add that to the sqoop server.

    -Abe

    On Mon, Oct 14, 2013 at 11:02 AM, pawan singh wrote:

    Sqoop supports hadoop job properties with -D option, like job queue(
    mapred.job.queue.name)

    On Mon, Oct 14, 2013 at 11:08 PM, Abraham Elmahrek wrote:

    What job property would you like to set? I don't think you can set
    Hadoop Job properties unfortunately... but that's a question for the sqoop
    mailing list user@sqoop.apache.org.

    -Abe

    On Mon, Oct 14, 2013 at 4:57 AM, pawan singh wrote:

    Yes. Hadoop Job properties for sqoop jobs.

    On Mon, Oct 14, 2013 at 2:17 PM, Romain Rigaux wrote:

    Do you mean some Hadoop job properties from the Sqoop job?

    Romain


    On Mon, Oct 14, 2013 at 4:27 PM, pawan singh <jeet27.pawan@gmail.com
    wrote:
    Thanks Romain,

    That was the reason. How could we set job properties.


    On Fri, Oct 11, 2013 at 8:15 PM, Romain Rigaux <romain@cloudera.com
    wrote:
    Which Hue version are you using?

    I see cdh4.3.0 for Sqoop2. As Sqoop2 is quickly evolving and its
    API changing, the version needs to be CDH4.4 is using Hue 2.5.

    Romain


    On Fri, Oct 11, 2013 at 7:13 AM, pawan singh <
    jeet27.pawan@gmail.com> wrote:
    Hi,

    Sqoop App in hue is unresponsive while sqoop2 is running fine,


    [cloudera@localhost pawan]$ wget -qO -
    localhost:12000/sqoop/version
    {"revision":"","protocols":["1"],"date":"Mon May 27 20:29:47 PDT
    2013","user":"jenkins","url":"git:\/\/ubuntu-slave02\/var\/lib\/jenkins\/workspace\/CDH4.3.0-Packaging-Sqoop2\/build\/cdh4\/sqoop2\/1.99.1-cdh4.3.0\/source\/common","version":"1.99.1-cdh4.3.0"}

    looking at the logs i found that:

    *HUE LOG:

    *[11/Oct/2013 07:05:50 +0000] http_client DEBUG *GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    [11/Oct/2013 07:05:50 +0000] middleware INFO Processing
    exception: 'HTTPError' object has no attribute 'reason': Traceback (most
    recent call last):
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/core/handlers/base.py",
    line 100, in get_response
    response = callback(request, *callback_args,
    **callback_kwargs)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    60, in submissions
    return get_submissions(request)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    54, in get_submissions
    response.update(handle_rest_exception(e, _('Could not get
    submissions.')))
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/exception.py", line
    31, in handle_rest_exception
    reason = e.get_parent_ex().reason
    AttributeError: 'HTTPError' object has no attribute 'reason'




    *Sqoop LOG:

    *2013-10-11 10:05:50,843 ERROR server.SqoopProtocolServlet
    [org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:53)]
    *Exception in GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    org.apache.sqoop.common.SqoopException: SERVER_0003:Invalid HTTP
    request - Do not know what to do.
    at
    org.apache.sqoop.handler.SubmissionRequestHandler.handleEvent(SubmissionRequestHandler.java:75)
    at
    org.apache.sqoop.server.v1.SubmissionServlet.handleGetRequest(SubmissionServlet.java:39)
    at
    org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:48)
    at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
    at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at
    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at
    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at
    org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at
    org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at
    org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at
    org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at
    org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at
    org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
    at
    org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
    at
    org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
    at
    org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    at java.lang.Thread.run(Thread.java:662)*

    *

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from it,
    send an email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from it,
    send an email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from it, send an email to hue-user+unsubscribe@cloudera.org.
  • Romain Rigaux at Oct 15, 2013 at 1:27 pm

    On Tue, Oct 15, 2013 at 7:33 PM, pawan singh wrote:

    Hi Romain/Abraham,

    Idea is of fair utilization of resources, I am not very sure about sqoop-2
    but hadoop properties were available with sqoop1.
    restricting reducers
    restricting mappers
    restricting job queue

    I believe these parameters should be configurable from client instead of
    server and it should be configurable though "framework".

    On Tue, Oct 15, 2013 at 4:41 AM, Romain Rigaux wrote:

    I think the idea is to have the MapReduce jobs being executed in a
    certain JT queue.

    Romain

    On Tue, Oct 15, 2013 at 3:41 AM, Abraham Elmahrek wrote:

    Pawan,

    The Sqoop app in Hue is a front end for the Sqoop2 application. The
    sqoop1 and sqoop2 applications differ greatly:

    1. Sqoop 2 is the successor to Sqoop 1.
    2. Sqoop 2 has a client - server architecture.
    3. MR jobs are submitted from the Sqoop server in Sqoop2. In Sqoop1,
    they are submitted from the client.
    4. Connectors are much lighter and generic components have been
    handled in the "framework" component of Sqoop 2.
    5. Sqoop 2 is intended on being more secure than Sqoop 1. It starts
    off by managing connections so that information isn't provided over the
    command line.

    The list really does go on... there are several improvements to the
    design in Sqoop 2.

    What this means is that Java arguments are no longer simply passed to
    the MR job from the client. This is intentionally done. I believe you can
    provide a custom start script for the server to add Java arguments and
    those will be passed to the MR job, though I'm unsure.

    What are you doing with Sqoop that requires Hadoop properties to be set?
    Your feedback is extremely important and can potentially impact project
    direction!

    -Abe

    On Mon, Oct 14, 2013 at 11:03 AM, Abraham Elmahrek wrote:

    Ah yes, but the difference is that we're using sqoop2, which does not
    support that. You may be able to add that to the sqoop server.

    -Abe

    On Mon, Oct 14, 2013 at 11:02 AM, pawan singh wrote:

    Sqoop supports hadoop job properties with -D option, like job queue(
    mapred.job.queue.name)

    On Mon, Oct 14, 2013 at 11:08 PM, Abraham Elmahrek wrote:

    What job property would you like to set? I don't think you can set
    Hadoop Job properties unfortunately... but that's a question for the sqoop
    mailing list user@sqoop.apache.org.

    -Abe

    On Mon, Oct 14, 2013 at 4:57 AM, pawan singh wrote:

    Yes. Hadoop Job properties for sqoop jobs.

    On Mon, Oct 14, 2013 at 2:17 PM, Romain Rigaux wrote:

    Do you mean some Hadoop job properties from the Sqoop job?

    Romain


    On Mon, Oct 14, 2013 at 4:27 PM, pawan singh <
    jeet27.pawan@gmail.com> wrote:
    Thanks Romain,

    That was the reason. How could we set job properties.


    On Fri, Oct 11, 2013 at 8:15 PM, Romain Rigaux <
    romain@cloudera.com> wrote:
    Which Hue version are you using?

    I see cdh4.3.0 for Sqoop2. As Sqoop2 is quickly evolving and its
    API changing, the version needs to be CDH4.4 is using Hue 2.5.

    Romain


    On Fri, Oct 11, 2013 at 7:13 AM, pawan singh <
    jeet27.pawan@gmail.com> wrote:
    Hi,

    Sqoop App in hue is unresponsive while sqoop2 is running fine,


    [cloudera@localhost pawan]$ wget -qO -
    localhost:12000/sqoop/version
    {"revision":"","protocols":["1"],"date":"Mon May 27 20:29:47 PDT
    2013","user":"jenkins","url":"git:\/\/ubuntu-slave02\/var\/lib\/jenkins\/workspace\/CDH4.3.0-Packaging-Sqoop2\/build\/cdh4\/sqoop2\/1.99.1-cdh4.3.0\/source\/common","version":"1.99.1-cdh4.3.0"}

    looking at the logs i found that:

    *HUE LOG:

    *[11/Oct/2013 07:05:50 +0000] http_client DEBUG *GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    [11/Oct/2013 07:05:50 +0000] middleware INFO Processing
    exception: 'HTTPError' object has no attribute 'reason': Traceback (most
    recent call last):
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/core/handlers/base.py",
    line 100, in get_response
    response = callback(request, *callback_args,
    **callback_kwargs)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    60, in submissions
    return get_submissions(request)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    54, in get_submissions
    response.update(handle_rest_exception(e, _('Could not get
    submissions.')))
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/exception.py", line
    31, in handle_rest_exception
    reason = e.get_parent_ex().reason
    AttributeError: 'HTTPError' object has no attribute 'reason'




    *Sqoop LOG:

    *2013-10-11 10:05:50,843 ERROR server.SqoopProtocolServlet
    [org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:53)]
    *Exception in GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    org.apache.sqoop.common.SqoopException: SERVER_0003:Invalid HTTP
    request - Do not know what to do.
    at
    org.apache.sqoop.handler.SubmissionRequestHandler.handleEvent(SubmissionRequestHandler.java:75)
    at
    org.apache.sqoop.server.v1.SubmissionServlet.handleGetRequest(SubmissionServlet.java:39)
    at
    org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:48)
    at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
    at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at
    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at
    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at
    org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at
    org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at
    org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at
    org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at
    org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at
    org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
    at
    org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
    at
    org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
    at
    org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    at java.lang.Thread.run(Thread.java:662)*

    *

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from
    it, send an email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from it,
    send an email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202
    To unsubscribe from this group and stop receiving emails from it, send an email to hue-user+unsubscribe@cloudera.org.
  • Jarek Jarcec Cecho at Oct 15, 2013 at 3:24 pm
    Hi Pawan,
    I'm excited to see your interest in Sqoop 2!

    As Abe mentioned earlier, Sqoop2 has been completely redesigned to overcome some limitations of the previous Sqoop 1 architecture. One of the shortcomings that were removed is the tight coupling with mapreduce. Even though that currently mapreduce is the only way how to transfer the data with Sqoop 2, we've open the infrastructure to different transport mechanisms. For example we are thinking about directly using YARN without MR layer for Hadoop 2. As a result no mapreduce specific options are exposed via the client as you can't expect that mapreduce will be always there.

    Instead Sqoop2 is exposing configuration options that are specific to the data transfer. In the original Sqoop 1, by specifying number of mappers you were directly throttling load on the database. This was achieve by the fact that each mapper opened exactly one connection to the database and thus by setting number of mappers, you know how many connections will be used. This make complete sense from technical point of view, but it's very confusing for users who do not necessary know the underlaying implementation. As a result Sqoop2 is trying to expose the configuration in a more straightforward manner and the number of concurrent connections is being throttled by the configuration options "Extractors" (mainly for import job) and "Loaders" (mainly for export job).

    Jarcec
    On Tue, Oct 15, 2013 at 11:18:18PM +0900, Romain Rigaux wrote:
    On Tue, Oct 15, 2013 at 7:33 PM, pawan singh wrote:

    Hi Romain/Abraham,

    Idea is of fair utilization of resources, I am not very sure about sqoop-2
    but hadoop properties were available with sqoop1.
    restricting reducers
    restricting mappers
    restricting job queue

    I believe these parameters should be configurable from client instead of
    server and it should be configurable though "framework".

    On Tue, Oct 15, 2013 at 4:41 AM, Romain Rigaux wrote:

    I think the idea is to have the MapReduce jobs being executed in a
    certain JT queue.

    Romain

    On Tue, Oct 15, 2013 at 3:41 AM, Abraham Elmahrek wrote:

    Pawan,

    The Sqoop app in Hue is a front end for the Sqoop2 application. The
    sqoop1 and sqoop2 applications differ greatly:

    1. Sqoop 2 is the successor to Sqoop 1.
    2. Sqoop 2 has a client - server architecture.
    3. MR jobs are submitted from the Sqoop server in Sqoop2. In Sqoop1,
    they are submitted from the client.
    4. Connectors are much lighter and generic components have been
    handled in the "framework" component of Sqoop 2.
    5. Sqoop 2 is intended on being more secure than Sqoop 1. It starts
    off by managing connections so that information isn't provided over the
    command line.

    The list really does go on... there are several improvements to the
    design in Sqoop 2.

    What this means is that Java arguments are no longer simply passed to
    the MR job from the client. This is intentionally done. I believe you can
    provide a custom start script for the server to add Java arguments and
    those will be passed to the MR job, though I'm unsure.

    What are you doing with Sqoop that requires Hadoop properties to be set?
    Your feedback is extremely important and can potentially impact project
    direction!

    -Abe

    On Mon, Oct 14, 2013 at 11:03 AM, Abraham Elmahrek wrote:

    Ah yes, but the difference is that we're using sqoop2, which does not
    support that. You may be able to add that to the sqoop server.

    -Abe

    On Mon, Oct 14, 2013 at 11:02 AM, pawan singh wrote:

    Sqoop supports hadoop job properties with -D option, like job queue(
    mapred.job.queue.name)

    On Mon, Oct 14, 2013 at 11:08 PM, Abraham Elmahrek wrote:

    What job property would you like to set? I don't think you can set
    Hadoop Job properties unfortunately... but that's a question for the sqoop
    mailing list user@sqoop.apache.org.

    -Abe

    On Mon, Oct 14, 2013 at 4:57 AM, pawan singh wrote:

    Yes. Hadoop Job properties for sqoop jobs.

    On Mon, Oct 14, 2013 at 2:17 PM, Romain Rigaux wrote:

    Do you mean some Hadoop job properties from the Sqoop job?

    Romain


    On Mon, Oct 14, 2013 at 4:27 PM, pawan singh <
    jeet27.pawan@gmail.com> wrote:
    Thanks Romain,

    That was the reason. How could we set job properties.


    On Fri, Oct 11, 2013 at 8:15 PM, Romain Rigaux <
    romain@cloudera.com> wrote:
    Which Hue version are you using?

    I see cdh4.3.0 for Sqoop2. As Sqoop2 is quickly evolving and its
    API changing, the version needs to be CDH4.4 is using Hue 2.5.

    Romain


    On Fri, Oct 11, 2013 at 7:13 AM, pawan singh <
    jeet27.pawan@gmail.com> wrote:
    Hi,

    Sqoop App in hue is unresponsive while sqoop2 is running fine,


    [cloudera@localhost pawan]$ wget -qO -
    localhost:12000/sqoop/version
    {"revision":"","protocols":["1"],"date":"Mon May 27 20:29:47 PDT
    2013","user":"jenkins","url":"git:\/\/ubuntu-slave02\/var\/lib\/jenkins\/workspace\/CDH4.3.0-Packaging-Sqoop2\/build\/cdh4\/sqoop2\/1.99.1-cdh4.3.0\/source\/common","version":"1.99.1-cdh4.3.0"}

    looking at the logs i found that:

    *HUE LOG:

    *[11/Oct/2013 07:05:50 +0000] http_client DEBUG *GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    [11/Oct/2013 07:05:50 +0000] middleware INFO Processing
    exception: 'HTTPError' object has no attribute 'reason': Traceback (most
    recent call last):
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/core/handlers/base.py",
    line 100, in get_response
    response = callback(request, *callback_args,
    **callback_kwargs)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    60, in submissions
    return get_submissions(request)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    54, in get_submissions
    response.update(handle_rest_exception(e, _('Could not get
    submissions.')))
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/exception.py", line
    31, in handle_rest_exception
    reason = e.get_parent_ex().reason
    AttributeError: 'HTTPError' object has no attribute 'reason'




    *Sqoop LOG:

    *2013-10-11 10:05:50,843 ERROR server.SqoopProtocolServlet
    [org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:53)]
    *Exception in GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    org.apache.sqoop.common.SqoopException: SERVER_0003:Invalid HTTP
    request - Do not know what to do.
    at
    org.apache.sqoop.handler.SubmissionRequestHandler.handleEvent(SubmissionRequestHandler.java:75)
    at
    org.apache.sqoop.server.v1.SubmissionServlet.handleGetRequest(SubmissionServlet.java:39)
    at
    org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:48)
    at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
    at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at
    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at
    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at
    org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at
    org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at
    org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at
    org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at
    org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at
    org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
    at
    org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
    at
    org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
    at
    org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    at java.lang.Thread.run(Thread.java:662)*

    *

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from
    it, send an email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from it,
    send an email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202
    --

    ---
    You received this message because you are subscribed to the Google Groups "CDH Users" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to cdh-user+unsubscribe@cloudera.org.
    For more options, visit https://groups.google.com/a/cloudera.org/groups/opt_out.
  • Pawan singh at Oct 15, 2013 at 4:39 pm
    Hi Jarek,

    Thank you very much for giving clarity on sqoop-2 design and future plan.
    I'll explore YARN for further understanding.
    I understand extractors and loaders and their usage, for now do we have a
    way to set job queue, if not client side than can we hard code some where
    at server side for MR implementation.

    On Tue, Oct 15, 2013 at 8:54 PM, Jarek Jarcec Cecho wrote:

    Hi Pawan,
    I'm excited to see your interest in Sqoop 2!

    As Abe mentioned earlier, Sqoop2 has been completely redesigned to
    overcome some limitations of the previous Sqoop 1 architecture. One of the
    shortcomings that were removed is the tight coupling with mapreduce. Even
    though that currently mapreduce is the only way how to transfer the data
    with Sqoop 2, we've open the infrastructure to different transport
    mechanisms. For example we are thinking about directly using YARN without
    MR layer for Hadoop 2. As a result no mapreduce specific options are
    exposed via the client as you can't expect that mapreduce will be always
    there.

    Instead Sqoop2 is exposing configuration options that are specific to the
    data transfer. In the original Sqoop 1, by specifying number of mappers you
    were directly throttling load on the database. This was achieve by the fact
    that each mapper opened exactly one connection to the database and thus by
    setting number of mappers, you know how many connections will be used. This
    make complete sense from technical point of view, but it's very confusing
    for users who do not necessary know the underlaying implementation. As a
    result Sqoop2 is trying to expose the configuration in a more
    straightforward manner and the number of concurrent connections is being
    throttled by the configuration options "Extractors" (mainly for import job)
    and "Loaders" (mainly for export job).

    Jarcec
    On Tue, Oct 15, 2013 at 11:18:18PM +0900, Romain Rigaux wrote:
    On Tue, Oct 15, 2013 at 7:33 PM, pawan singh wrote:

    Hi Romain/Abraham,

    Idea is of fair utilization of resources, I am not very sure about
    sqoop-2
    but hadoop properties were available with sqoop1.
    restricting reducers
    restricting mappers
    restricting job queue

    I believe these parameters should be configurable from client instead
    of
    server and it should be configurable though "framework".


    On Tue, Oct 15, 2013 at 4:41 AM, Romain Rigaux <romain@cloudera.com
    wrote:
    I think the idea is to have the MapReduce jobs being executed in a
    certain JT queue.

    Romain


    On Tue, Oct 15, 2013 at 3:41 AM, Abraham Elmahrek <abe@cloudera.com
    wrote:
    Pawan,

    The Sqoop app in Hue is a front end for the Sqoop2 application. The
    sqoop1 and sqoop2 applications differ greatly:

    1. Sqoop 2 is the successor to Sqoop 1.
    2. Sqoop 2 has a client - server architecture.
    3. MR jobs are submitted from the Sqoop server in Sqoop2. In
    Sqoop1,
    they are submitted from the client.
    4. Connectors are much lighter and generic components have been
    handled in the "framework" component of Sqoop 2.
    5. Sqoop 2 is intended on being more secure than Sqoop 1. It
    starts
    off by managing connections so that information isn't provided
    over the
    command line.

    The list really does go on... there are several improvements to the
    design in Sqoop 2.

    What this means is that Java arguments are no longer simply passed to
    the MR job from the client. This is intentionally done. I believe
    you can
    provide a custom start script for the server to add Java arguments
    and
    those will be passed to the MR job, though I'm unsure.

    What are you doing with Sqoop that requires Hadoop properties to be
    set?
    Your feedback is extremely important and can potentially impact
    project
    direction!

    -Abe


    On Mon, Oct 14, 2013 at 11:03 AM, Abraham Elmahrek <abe@cloudera.com
    wrote:
    Ah yes, but the difference is that we're using sqoop2, which does
    not
    support that. You may be able to add that to the sqoop server.

    -Abe


    On Mon, Oct 14, 2013 at 11:02 AM, pawan singh <
    jeet27.pawan@gmail.com>wrote:
    Sqoop supports hadoop job properties with -D option, like job
    queue(
    mapred.job.queue.name)


    On Mon, Oct 14, 2013 at 11:08 PM, Abraham Elmahrek <
    abe@cloudera.com>wrote:
    What job property would you like to set? I don't think you can set
    Hadoop Job properties unfortunately... but that's a question for
    the sqoop
    mailing list user@sqoop.apache.org.

    -Abe


    On Mon, Oct 14, 2013 at 4:57 AM, pawan singh <
    jeet27.pawan@gmail.com>wrote:
    Yes. Hadoop Job properties for sqoop jobs.


    On Mon, Oct 14, 2013 at 2:17 PM, Romain Rigaux <
    romain@cloudera.com>wrote:
    Do you mean some Hadoop job properties from the Sqoop job?

    Romain


    On Mon, Oct 14, 2013 at 4:27 PM, pawan singh <
    jeet27.pawan@gmail.com> wrote:
    Thanks Romain,

    That was the reason. How could we set job properties.


    On Fri, Oct 11, 2013 at 8:15 PM, Romain Rigaux <
    romain@cloudera.com> wrote:
    Which Hue version are you using?

    I see cdh4.3.0 for Sqoop2. As Sqoop2 is quickly evolving and
    its
    API changing, the version needs to be CDH4.4 is using Hue 2.5.

    Romain


    On Fri, Oct 11, 2013 at 7:13 AM, pawan singh <
    jeet27.pawan@gmail.com> wrote:
    Hi,

    Sqoop App in hue is unresponsive while sqoop2 is running
    fine,

    [cloudera@localhost pawan]$ wget -qO -
    localhost:12000/sqoop/version
    {"revision":"","protocols":["1"],"date":"Mon May 27 20:29:47
    PDT
    2013","user":"jenkins","url":"git:\/\/ubuntu-slave02\/var\/lib\/jenkins\/workspace\/CDH4.3.0-Packaging-Sqoop2\/build\/cdh4\/sqoop2\/1.99.1-cdh4.3.0\/source\/common","version":"1.99.1-cdh4.3.0"}
    looking at the logs i found that:

    *HUE LOG:

    *[11/Oct/2013 07:05:50 +0000] http_client DEBUG *GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    [11/Oct/2013 07:05:50 +0000] middleware INFO Processing
    exception: 'HTTPError' object has no attribute 'reason':
    Traceback (most
    recent call last):
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/core/handlers/base.py",
    line 100, in get_response
    response = callback(request, *callback_args,
    **callback_kwargs)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    60, in submissions
    return get_submissions(request)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    54, in get_submissions
    response.update(handle_rest_exception(e, _('Could not get
    submissions.')))
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/exception.py", line
    31, in handle_rest_exception
    reason = e.get_parent_ex().reason
    AttributeError: 'HTTPError' object has no attribute 'reason'




    *Sqoop LOG:

    *2013-10-11 10:05:50,843 ERROR server.SqoopProtocolServlet
    [org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:53)]
    *Exception in GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    org.apache.sqoop.common.SqoopException: SERVER_0003:Invalid
    HTTP
    request - Do not know what to do.
    at
    org.apache.sqoop.handler.SubmissionRequestHandler.handleEvent(SubmissionRequestHandler.java:75)
    at
    org.apache.sqoop.server.v1.SubmissionServlet.handleGetRequest(SubmissionServlet.java:39)
    at
    org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:48)
    at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
    at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at
    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at
    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at
    org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at
    org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at
    org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at
    org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at
    org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at
    org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
    at
    org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
    at
    org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
    at
    org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    at java.lang.Thread.run(Thread.java:662)*

    *

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from
    it, send an email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from it,
    send an email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202
    --

    ---
    You received this message because you are subscribed to the Google
    Groups "CDH Users" group.
    To unsubscribe from this group and stop receiving emails from it, send
    an email to cdh-user+unsubscribe@cloudera.org.
    For more options, visit
    https://groups.google.com/a/cloudera.org/groups/opt_out.


    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from it, send an email to hue-user+unsubscribe@cloudera.org.
  • Pawan singh at Oct 30, 2013 at 7:21 am
    Hi Romain/Jarek,

    Sqoop2 app in hue writes data in HDFS as sqoop2 user that others could not
    read. How possibly it could write data with the user it has been submitted
    with, or with read all permission?


    On Tue, Oct 15, 2013 at 10:09 PM, pawan singh wrote:

    Hi Jarek,

    Thank you very much for giving clarity on sqoop-2 design and future plan.
    I'll explore YARN for further understanding.
    I understand extractors and loaders and their usage, for now do we have a
    way to set job queue, if not client side than can we hard code some where
    at server side for MR implementation.

    On Tue, Oct 15, 2013 at 8:54 PM, Jarek Jarcec Cecho wrote:

    Hi Pawan,
    I'm excited to see your interest in Sqoop 2!

    As Abe mentioned earlier, Sqoop2 has been completely redesigned to
    overcome some limitations of the previous Sqoop 1 architecture. One of the
    shortcomings that were removed is the tight coupling with mapreduce. Even
    though that currently mapreduce is the only way how to transfer the data
    with Sqoop 2, we've open the infrastructure to different transport
    mechanisms. For example we are thinking about directly using YARN without
    MR layer for Hadoop 2. As a result no mapreduce specific options are
    exposed via the client as you can't expect that mapreduce will be always
    there.

    Instead Sqoop2 is exposing configuration options that are specific to the
    data transfer. In the original Sqoop 1, by specifying number of mappers you
    were directly throttling load on the database. This was achieve by the fact
    that each mapper opened exactly one connection to the database and thus by
    setting number of mappers, you know how many connections will be used. This
    make complete sense from technical point of view, but it's very confusing
    for users who do not necessary know the underlaying implementation. As a
    result Sqoop2 is trying to expose the configuration in a more
    straightforward manner and the number of concurrent connections is being
    throttled by the configuration options "Extractors" (mainly for import job)
    and "Loaders" (mainly for export job).

    Jarcec
    On Tue, Oct 15, 2013 at 11:18:18PM +0900, Romain Rigaux wrote:
    On Tue, Oct 15, 2013 at 7:33 PM, pawan singh <jeet27.pawan@gmail.com>
    wrote:
    Hi Romain/Abraham,

    Idea is of fair utilization of resources, I am not very sure about
    sqoop-2
    but hadoop properties were available with sqoop1.
    restricting reducers
    restricting mappers
    restricting job queue

    I believe these parameters should be configurable from client instead
    of
    server and it should be configurable though "framework".


    On Tue, Oct 15, 2013 at 4:41 AM, Romain Rigaux <romain@cloudera.com
    wrote:
    I think the idea is to have the MapReduce jobs being executed in a
    certain JT queue.

    Romain


    On Tue, Oct 15, 2013 at 3:41 AM, Abraham Elmahrek <abe@cloudera.com
    wrote:
    Pawan,

    The Sqoop app in Hue is a front end for the Sqoop2 application. The
    sqoop1 and sqoop2 applications differ greatly:

    1. Sqoop 2 is the successor to Sqoop 1.
    2. Sqoop 2 has a client - server architecture.
    3. MR jobs are submitted from the Sqoop server in Sqoop2. In
    Sqoop1,
    they are submitted from the client.
    4. Connectors are much lighter and generic components have been
    handled in the "framework" component of Sqoop 2.
    5. Sqoop 2 is intended on being more secure than Sqoop 1. It
    starts
    off by managing connections so that information isn't provided
    over the
    command line.

    The list really does go on... there are several improvements to the
    design in Sqoop 2.

    What this means is that Java arguments are no longer simply passed
    to
    the MR job from the client. This is intentionally done. I believe
    you can
    provide a custom start script for the server to add Java arguments
    and
    those will be passed to the MR job, though I'm unsure.

    What are you doing with Sqoop that requires Hadoop properties to be
    set?
    Your feedback is extremely important and can potentially impact
    project
    direction!

    -Abe


    On Mon, Oct 14, 2013 at 11:03 AM, Abraham Elmahrek <
    abe@cloudera.com>wrote:
    Ah yes, but the difference is that we're using sqoop2, which does
    not
    support that. You may be able to add that to the sqoop server.

    -Abe


    On Mon, Oct 14, 2013 at 11:02 AM, pawan singh <
    jeet27.pawan@gmail.com>wrote:
    Sqoop supports hadoop job properties with -D option, like job
    queue(
    mapred.job.queue.name)


    On Mon, Oct 14, 2013 at 11:08 PM, Abraham Elmahrek <
    abe@cloudera.com>wrote:
    What job property would you like to set? I don't think you can
    set
    Hadoop Job properties unfortunately... but that's a question for
    the sqoop
    mailing list user@sqoop.apache.org.

    -Abe


    On Mon, Oct 14, 2013 at 4:57 AM, pawan singh <
    jeet27.pawan@gmail.com>wrote:
    Yes. Hadoop Job properties for sqoop jobs.


    On Mon, Oct 14, 2013 at 2:17 PM, Romain Rigaux <
    romain@cloudera.com>wrote:
    Do you mean some Hadoop job properties from the Sqoop job?

    Romain


    On Mon, Oct 14, 2013 at 4:27 PM, pawan singh <
    jeet27.pawan@gmail.com> wrote:
    Thanks Romain,

    That was the reason. How could we set job properties.


    On Fri, Oct 11, 2013 at 8:15 PM, Romain Rigaux <
    romain@cloudera.com> wrote:
    Which Hue version are you using?

    I see cdh4.3.0 for Sqoop2. As Sqoop2 is quickly evolving and
    its
    API changing, the version needs to be CDH4.4 is using Hue
    2.5.
    Romain


    On Fri, Oct 11, 2013 at 7:13 AM, pawan singh <
    jeet27.pawan@gmail.com> wrote:
    Hi,

    Sqoop App in hue is unresponsive while sqoop2 is running
    fine,

    [cloudera@localhost pawan]$ wget -qO -
    localhost:12000/sqoop/version
    {"revision":"","protocols":["1"],"date":"Mon May 27
    20:29:47 PDT
    2013","user":"jenkins","url":"git:\/\/ubuntu-slave02\/var\/lib\/jenkins\/workspace\/CDH4.3.0-Packaging-Sqoop2\/build\/cdh4\/sqoop2\/1.99.1-cdh4.3.0\/source\/common","version":"1.99.1-cdh4.3.0"}
    looking at the logs i found that:

    *HUE LOG:

    *[11/Oct/2013 07:05:50 +0000] http_client DEBUG *GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    [11/Oct/2013 07:05:50 +0000] middleware INFO
    Processing
    exception: 'HTTPError' object has no attribute 'reason':
    Traceback (most
    recent call last):
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/core/handlers/base.py",
    line 100, in get_response
    response = callback(request, *callback_args,
    **callback_kwargs)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    60, in submissions
    return get_submissions(request)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    54, in get_submissions
    response.update(handle_rest_exception(e, _('Could not
    get
    submissions.')))
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/exception.py", line
    31, in handle_rest_exception
    reason = e.get_parent_ex().reason
    AttributeError: 'HTTPError' object has no attribute 'reason'




    *Sqoop LOG:

    *2013-10-11 10:05:50,843 ERROR server.SqoopProtocolServlet
    [org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:53)]
    *Exception in GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    org.apache.sqoop.common.SqoopException: SERVER_0003:Invalid
    HTTP
    request - Do not know what to do.
    at
    org.apache.sqoop.handler.SubmissionRequestHandler.handleEvent(SubmissionRequestHandler.java:75)
    at
    org.apache.sqoop.server.v1.SubmissionServlet.handleGetRequest(SubmissionServlet.java:39)
    at
    org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:48)
    at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
    at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at
    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at
    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at
    org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at
    org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at
    org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at
    org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at
    org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at
    org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
    at
    org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
    at
    org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
    at
    org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    at java.lang.Thread.run(Thread.java:662)*

    *

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails
    from
    it, send an email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from
    it,
    send an email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202
    --

    ---
    You received this message because you are subscribed to the Google
    Groups "CDH Users" group.
    To unsubscribe from this group and stop receiving emails from it, send
    an email to cdh-user+unsubscribe@cloudera.org.
    For more options, visit
    https://groups.google.com/a/cloudera.org/groups/opt_out.


    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202


    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from it, send an email to hue-user+unsubscribe@cloudera.org.
  • Jarek Jarcec Cecho at Nov 3, 2013 at 9:33 pm
    Hi Pawan,
    Sqoop2 currently writes data as the user who is running Sqoop2 server. This behaviour will change in near future, but for the time being you can change the user who is running Sqoop2 server to import the data as a different user.

    Jarcec
    On Wed, Oct 30, 2013 at 12:51:09PM +0530, pawan singh wrote:
    Hi Romain/Jarek,

    Sqoop2 app in hue writes data in HDFS as sqoop2 user that others could not
    read. How possibly it could write data with the user it has been submitted
    with, or with read all permission?


    On Tue, Oct 15, 2013 at 10:09 PM, pawan singh wrote:

    Hi Jarek,

    Thank you very much for giving clarity on sqoop-2 design and future plan.
    I'll explore YARN for further understanding.
    I understand extractors and loaders and their usage, for now do we have a
    way to set job queue, if not client side than can we hard code some where
    at server side for MR implementation.

    On Tue, Oct 15, 2013 at 8:54 PM, Jarek Jarcec Cecho wrote:

    Hi Pawan,
    I'm excited to see your interest in Sqoop 2!

    As Abe mentioned earlier, Sqoop2 has been completely redesigned to
    overcome some limitations of the previous Sqoop 1 architecture. One of the
    shortcomings that were removed is the tight coupling with mapreduce. Even
    though that currently mapreduce is the only way how to transfer the data
    with Sqoop 2, we've open the infrastructure to different transport
    mechanisms. For example we are thinking about directly using YARN without
    MR layer for Hadoop 2. As a result no mapreduce specific options are
    exposed via the client as you can't expect that mapreduce will be always
    there.

    Instead Sqoop2 is exposing configuration options that are specific to the
    data transfer. In the original Sqoop 1, by specifying number of mappers you
    were directly throttling load on the database. This was achieve by the fact
    that each mapper opened exactly one connection to the database and thus by
    setting number of mappers, you know how many connections will be used. This
    make complete sense from technical point of view, but it's very confusing
    for users who do not necessary know the underlaying implementation. As a
    result Sqoop2 is trying to expose the configuration in a more
    straightforward manner and the number of concurrent connections is being
    throttled by the configuration options "Extractors" (mainly for import job)
    and "Loaders" (mainly for export job).

    Jarcec
    On Tue, Oct 15, 2013 at 11:18:18PM +0900, Romain Rigaux wrote:
    On Tue, Oct 15, 2013 at 7:33 PM, pawan singh <jeet27.pawan@gmail.com>
    wrote:
    Hi Romain/Abraham,

    Idea is of fair utilization of resources, I am not very sure about
    sqoop-2
    but hadoop properties were available with sqoop1.
    restricting reducers
    restricting mappers
    restricting job queue

    I believe these parameters should be configurable from client instead
    of
    server and it should be configurable though "framework".


    On Tue, Oct 15, 2013 at 4:41 AM, Romain Rigaux <romain@cloudera.com
    wrote:
    I think the idea is to have the MapReduce jobs being executed in a
    certain JT queue.

    Romain


    On Tue, Oct 15, 2013 at 3:41 AM, Abraham Elmahrek <abe@cloudera.com
    wrote:
    Pawan,

    The Sqoop app in Hue is a front end for the Sqoop2 application. The
    sqoop1 and sqoop2 applications differ greatly:

    1. Sqoop 2 is the successor to Sqoop 1.
    2. Sqoop 2 has a client - server architecture.
    3. MR jobs are submitted from the Sqoop server in Sqoop2. In
    Sqoop1,
    they are submitted from the client.
    4. Connectors are much lighter and generic components have been
    handled in the "framework" component of Sqoop 2.
    5. Sqoop 2 is intended on being more secure than Sqoop 1. It
    starts
    off by managing connections so that information isn't provided
    over the
    command line.

    The list really does go on... there are several improvements to the
    design in Sqoop 2.

    What this means is that Java arguments are no longer simply passed
    to
    the MR job from the client. This is intentionally done. I believe
    you can
    provide a custom start script for the server to add Java arguments
    and
    those will be passed to the MR job, though I'm unsure.

    What are you doing with Sqoop that requires Hadoop properties to be
    set?
    Your feedback is extremely important and can potentially impact
    project
    direction!

    -Abe


    On Mon, Oct 14, 2013 at 11:03 AM, Abraham Elmahrek <
    abe@cloudera.com>wrote:
    Ah yes, but the difference is that we're using sqoop2, which does
    not
    support that. You may be able to add that to the sqoop server.

    -Abe


    On Mon, Oct 14, 2013 at 11:02 AM, pawan singh <
    jeet27.pawan@gmail.com>wrote:
    Sqoop supports hadoop job properties with -D option, like job
    queue(
    mapred.job.queue.name)


    On Mon, Oct 14, 2013 at 11:08 PM, Abraham Elmahrek <
    abe@cloudera.com>wrote:
    What job property would you like to set? I don't think you can
    set
    Hadoop Job properties unfortunately... but that's a question for
    the sqoop
    mailing list user@sqoop.apache.org.

    -Abe


    On Mon, Oct 14, 2013 at 4:57 AM, pawan singh <
    jeet27.pawan@gmail.com>wrote:
    Yes. Hadoop Job properties for sqoop jobs.


    On Mon, Oct 14, 2013 at 2:17 PM, Romain Rigaux <
    romain@cloudera.com>wrote:
    Do you mean some Hadoop job properties from the Sqoop job?

    Romain


    On Mon, Oct 14, 2013 at 4:27 PM, pawan singh <
    jeet27.pawan@gmail.com> wrote:
    Thanks Romain,

    That was the reason. How could we set job properties.


    On Fri, Oct 11, 2013 at 8:15 PM, Romain Rigaux <
    romain@cloudera.com> wrote:
    Which Hue version are you using?

    I see cdh4.3.0 for Sqoop2. As Sqoop2 is quickly evolving and
    its
    API changing, the version needs to be CDH4.4 is using Hue
    2.5.
    Romain


    On Fri, Oct 11, 2013 at 7:13 AM, pawan singh <
    jeet27.pawan@gmail.com> wrote:
    Hi,

    Sqoop App in hue is unresponsive while sqoop2 is running
    fine,

    [cloudera@localhost pawan]$ wget -qO -
    localhost:12000/sqoop/version
    {"revision":"","protocols":["1"],"date":"Mon May 27
    20:29:47 PDT
    2013","user":"jenkins","url":"git:\/\/ubuntu-slave02\/var\/lib\/jenkins\/workspace\/CDH4.3.0-Packaging-Sqoop2\/build\/cdh4\/sqoop2\/1.99.1-cdh4.3.0\/source\/common","version":"1.99.1-cdh4.3.0"}
    looking at the logs i found that:

    *HUE LOG:

    *[11/Oct/2013 07:05:50 +0000] http_client DEBUG *GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    [11/Oct/2013 07:05:50 +0000] middleware INFO
    Processing
    exception: 'HTTPError' object has no attribute 'reason':
    Traceback (most
    recent call last):
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/core/handlers/base.py",
    line 100, in get_response
    response = callback(request, *callback_args,
    **callback_kwargs)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    60, in submissions
    return get_submissions(request)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    54, in get_submissions
    response.update(handle_rest_exception(e, _('Could not
    get
    submissions.')))
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/exception.py", line
    31, in handle_rest_exception
    reason = e.get_parent_ex().reason
    AttributeError: 'HTTPError' object has no attribute 'reason'




    *Sqoop LOG:

    *2013-10-11 10:05:50,843 ERROR server.SqoopProtocolServlet
    [org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:53)]
    *Exception in GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    org.apache.sqoop.common.SqoopException: SERVER_0003:Invalid
    HTTP
    request - Do not know what to do.
    at
    org.apache.sqoop.handler.SubmissionRequestHandler.handleEvent(SubmissionRequestHandler.java:75)
    at
    org.apache.sqoop.server.v1.SubmissionServlet.handleGetRequest(SubmissionServlet.java:39)
    at
    org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:48)
    at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
    at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at
    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at
    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at
    org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at
    org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at
    org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at
    org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at
    org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at
    org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
    at
    org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
    at
    org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
    at
    org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    at java.lang.Thread.run(Thread.java:662)*

    *

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails
    from
    it, send an email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from
    it,
    send an email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202
    --

    ---
    You received this message because you are subscribed to the Google
    Groups "CDH Users" group.
    To unsubscribe from this group and stop receiving emails from it, send
    an email to cdh-user+unsubscribe@cloudera.org.
    For more options, visit
    https://groups.google.com/a/cloudera.org/groups/opt_out.


    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202


    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202
  • Pawan singh at Nov 25, 2013 at 7:53 am
    Hi Jarek/Romain,

    Sqoop-2 application does not restricts managing connection only to admin
    privileges and anyone could create /edit or drop connections. While as per
    architecture of sqoop-2 it should be restricted to server administrators
    only.

    On Mon, Nov 4, 2013 at 3:03 AM, Jarek Jarcec Cecho wrote:

    Hi Pawan,
    Sqoop2 currently writes data as the user who is running Sqoop2 server.
    This behaviour will change in near future, but for the time being you can
    change the user who is running Sqoop2 server to import the data as a
    different user.

    Jarcec
    On Wed, Oct 30, 2013 at 12:51:09PM +0530, pawan singh wrote:
    Hi Romain/Jarek,

    Sqoop2 app in hue writes data in HDFS as sqoop2 user that others could not
    read. How possibly it could write data with the user it has been submitted
    with, or with read all permission?



    On Tue, Oct 15, 2013 at 10:09 PM, pawan singh <jeet27.pawan@gmail.com
    wrote:
    Hi Jarek,

    Thank you very much for giving clarity on sqoop-2 design and future
    plan.
    I'll explore YARN for further understanding.
    I understand extractors and loaders and their usage, for now do we
    have a
    way to set job queue, if not client side than can we hard code some
    where
    at server side for MR implementation.


    On Tue, Oct 15, 2013 at 8:54 PM, Jarek Jarcec Cecho <
    jarcec@cloudera.com>wrote:
    Hi Pawan,
    I'm excited to see your interest in Sqoop 2!

    As Abe mentioned earlier, Sqoop2 has been completely redesigned to
    overcome some limitations of the previous Sqoop 1 architecture. One
    of the
    shortcomings that were removed is the tight coupling with mapreduce.
    Even
    though that currently mapreduce is the only way how to transfer the
    data
    with Sqoop 2, we've open the infrastructure to different transport
    mechanisms. For example we are thinking about directly using YARN
    without
    MR layer for Hadoop 2. As a result no mapreduce specific options are
    exposed via the client as you can't expect that mapreduce will be
    always
    there.

    Instead Sqoop2 is exposing configuration options that are specific to
    the
    data transfer. In the original Sqoop 1, by specifying number of
    mappers you
    were directly throttling load on the database. This was achieve by
    the fact
    that each mapper opened exactly one connection to the database and
    thus by
    setting number of mappers, you know how many connections will be
    used. This
    make complete sense from technical point of view, but it's very
    confusing
    for users who do not necessary know the underlaying implementation.
    As a
    result Sqoop2 is trying to expose the configuration in a more
    straightforward manner and the number of concurrent connections is
    being
    throttled by the configuration options "Extractors" (mainly for
    import job)
    and "Loaders" (mainly for export job).

    Jarcec
    On Tue, Oct 15, 2013 at 11:18:18PM +0900, Romain Rigaux wrote:
    On Tue, Oct 15, 2013 at 7:33 PM, pawan singh <
    jeet27.pawan@gmail.com>
    wrote:
    Hi Romain/Abraham,

    Idea is of fair utilization of resources, I am not very sure about
    sqoop-2
    but hadoop properties were available with sqoop1.
    restricting reducers
    restricting mappers
    restricting job queue

    I believe these parameters should be configurable from client
    instead
    of
    server and it should be configurable though "framework".


    On Tue, Oct 15, 2013 at 4:41 AM, Romain Rigaux <
    romain@cloudera.com
    wrote:
    I think the idea is to have the MapReduce jobs being executed in
    a
    certain JT queue.

    Romain


    On Tue, Oct 15, 2013 at 3:41 AM, Abraham Elmahrek <
    abe@cloudera.com
    wrote:
    Pawan,

    The Sqoop app in Hue is a front end for the Sqoop2 application.
    The
    sqoop1 and sqoop2 applications differ greatly:

    1. Sqoop 2 is the successor to Sqoop 1.
    2. Sqoop 2 has a client - server architecture.
    3. MR jobs are submitted from the Sqoop server in Sqoop2. In
    Sqoop1,
    they are submitted from the client.
    4. Connectors are much lighter and generic components have
    been
    handled in the "framework" component of Sqoop 2.
    5. Sqoop 2 is intended on being more secure than Sqoop 1. It
    starts
    off by managing connections so that information isn't
    provided
    over the
    command line.

    The list really does go on... there are several improvements to
    the
    design in Sqoop 2.

    What this means is that Java arguments are no longer simply
    passed
    to
    the MR job from the client. This is intentionally done. I
    believe
    you can
    provide a custom start script for the server to add Java
    arguments
    and
    those will be passed to the MR job, though I'm unsure.

    What are you doing with Sqoop that requires Hadoop properties
    to be
    set?
    Your feedback is extremely important and can potentially impact
    project
    direction!

    -Abe


    On Mon, Oct 14, 2013 at 11:03 AM, Abraham Elmahrek <
    abe@cloudera.com>wrote:
    Ah yes, but the difference is that we're using sqoop2, which
    does
    not
    support that. You may be able to add that to the sqoop server.

    -Abe


    On Mon, Oct 14, 2013 at 11:02 AM, pawan singh <
    jeet27.pawan@gmail.com>wrote:
    Sqoop supports hadoop job properties with -D option, like job
    queue(
    mapred.job.queue.name)


    On Mon, Oct 14, 2013 at 11:08 PM, Abraham Elmahrek <
    abe@cloudera.com>wrote:
    What job property would you like to set? I don't think you
    can
    set
    Hadoop Job properties unfortunately... but that's a question
    for
    the sqoop
    mailing list user@sqoop.apache.org.

    -Abe


    On Mon, Oct 14, 2013 at 4:57 AM, pawan singh <
    jeet27.pawan@gmail.com>wrote:
    Yes. Hadoop Job properties for sqoop jobs.


    On Mon, Oct 14, 2013 at 2:17 PM, Romain Rigaux <
    romain@cloudera.com>wrote:
    Do you mean some Hadoop job properties from the Sqoop job?

    Romain


    On Mon, Oct 14, 2013 at 4:27 PM, pawan singh <
    jeet27.pawan@gmail.com> wrote:
    Thanks Romain,

    That was the reason. How could we set job properties.


    On Fri, Oct 11, 2013 at 8:15 PM, Romain Rigaux <
    romain@cloudera.com> wrote:
    Which Hue version are you using?

    I see cdh4.3.0 for Sqoop2. As Sqoop2 is quickly evolving
    and
    its
    API changing, the version needs to be CDH4.4 is using Hue
    2.5.
    Romain


    On Fri, Oct 11, 2013 at 7:13 AM, pawan singh <
    jeet27.pawan@gmail.com> wrote:
    Hi,

    Sqoop App in hue is unresponsive while sqoop2 is running
    fine,

    [cloudera@localhost pawan]$ wget -qO -
    localhost:12000/sqoop/version
    {"revision":"","protocols":["1"],"date":"Mon May 27
    20:29:47 PDT
    2013","user":"jenkins","url":"git:\/\/ubuntu-slave02\/var\/lib\/jenkins\/workspace\/CDH4.3.0-Packaging-Sqoop2\/build\/cdh4\/sqoop2\/1.99.1-cdh4.3.0\/source\/common","version":"1.99.1-cdh4.3.0"}
    looking at the logs i found that:

    *HUE LOG:

    *[11/Oct/2013 07:05:50 +0000] http_client DEBUG *GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    [11/Oct/2013 07:05:50 +0000] middleware INFO
    Processing
    exception: 'HTTPError' object has no attribute 'reason':
    Traceback (most
    recent call last):
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/core/handlers/base.py",
    line 100, in get_response
    response = callback(request, *callback_args,
    **callback_kwargs)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    60, in submissions
    return get_submissions(request)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    54, in get_submissions
    response.update(handle_rest_exception(e, _('Could
    not
    get
    submissions.')))
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/exception.py",
    line
    31, in handle_rest_exception
    reason = e.get_parent_ex().reason
    AttributeError: 'HTTPError' object has no attribute
    'reason'



    *Sqoop LOG:

    *2013-10-11 10:05:50,843 ERROR
    server.SqoopProtocolServlet
    [org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:53)]
    *Exception in GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    org.apache.sqoop.common.SqoopException:
    SERVER_0003:Invalid
    HTTP
    request - Do not know what to do.
    at
    org.apache.sqoop.handler.SubmissionRequestHandler.handleEvent(SubmissionRequestHandler.java:75)
    at
    org.apache.sqoop.server.v1.SubmissionServlet.handleGetRequest(SubmissionServlet.java:39)
    at
    org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:48)
    at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
    at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at
    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at
    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at
    org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at
    org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at
    org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at
    org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at
    org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at
    org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
    at
    org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
    at
    org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
    at
    org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    at java.lang.Thread.run(Thread.java:662)*

    *

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails
    from
    it, send an email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails
    from
    it,
    send an email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202
    --

    ---
    You received this message because you are subscribed to the Google
    Groups "CDH Users" group.
    To unsubscribe from this group and stop receiving emails from it,
    send
    an email to cdh-user+unsubscribe@cloudera.org.
    For more options, visit
    https://groups.google.com/a/cloudera.org/groups/opt_out.


    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202


    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202


    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails from it, send an email to hue-user+unsubscribe@cloudera.org.
  • Jarek Jarcec Cecho at Nov 25, 2013 at 4:08 pm
    Hi Pawan,
    you are correct, the new Sqoop 2 architecture allows us to differentiate between different roles such as "administrator" and "operator". The Sqoop 2 server itself currently do not have the ability to enforce their distinction and thus the Hue app can't do that either. This is a functionality that will be added.

    Jarcec
    On Mon, Nov 25, 2013 at 01:23:15PM +0530, pawan singh wrote:
    Hi Jarek/Romain,

    Sqoop-2 application does not restricts managing connection only to admin
    privileges and anyone could create /edit or drop connections. While as per
    architecture of sqoop-2 it should be restricted to server administrators
    only.

    On Mon, Nov 4, 2013 at 3:03 AM, Jarek Jarcec Cecho wrote:

    Hi Pawan,
    Sqoop2 currently writes data as the user who is running Sqoop2 server.
    This behaviour will change in near future, but for the time being you can
    change the user who is running Sqoop2 server to import the data as a
    different user.

    Jarcec
    On Wed, Oct 30, 2013 at 12:51:09PM +0530, pawan singh wrote:
    Hi Romain/Jarek,

    Sqoop2 app in hue writes data in HDFS as sqoop2 user that others could not
    read. How possibly it could write data with the user it has been submitted
    with, or with read all permission?



    On Tue, Oct 15, 2013 at 10:09 PM, pawan singh <jeet27.pawan@gmail.com
    wrote:
    Hi Jarek,

    Thank you very much for giving clarity on sqoop-2 design and future
    plan.
    I'll explore YARN for further understanding.
    I understand extractors and loaders and their usage, for now do we
    have a
    way to set job queue, if not client side than can we hard code some
    where
    at server side for MR implementation.


    On Tue, Oct 15, 2013 at 8:54 PM, Jarek Jarcec Cecho <
    jarcec@cloudera.com>wrote:
    Hi Pawan,
    I'm excited to see your interest in Sqoop 2!

    As Abe mentioned earlier, Sqoop2 has been completely redesigned to
    overcome some limitations of the previous Sqoop 1 architecture. One
    of the
    shortcomings that were removed is the tight coupling with mapreduce.
    Even
    though that currently mapreduce is the only way how to transfer the
    data
    with Sqoop 2, we've open the infrastructure to different transport
    mechanisms. For example we are thinking about directly using YARN
    without
    MR layer for Hadoop 2. As a result no mapreduce specific options are
    exposed via the client as you can't expect that mapreduce will be
    always
    there.

    Instead Sqoop2 is exposing configuration options that are specific to
    the
    data transfer. In the original Sqoop 1, by specifying number of
    mappers you
    were directly throttling load on the database. This was achieve by
    the fact
    that each mapper opened exactly one connection to the database and
    thus by
    setting number of mappers, you know how many connections will be
    used. This
    make complete sense from technical point of view, but it's very
    confusing
    for users who do not necessary know the underlaying implementation.
    As a
    result Sqoop2 is trying to expose the configuration in a more
    straightforward manner and the number of concurrent connections is
    being
    throttled by the configuration options "Extractors" (mainly for
    import job)
    and "Loaders" (mainly for export job).

    Jarcec
    On Tue, Oct 15, 2013 at 11:18:18PM +0900, Romain Rigaux wrote:
    On Tue, Oct 15, 2013 at 7:33 PM, pawan singh <
    jeet27.pawan@gmail.com>
    wrote:
    Hi Romain/Abraham,

    Idea is of fair utilization of resources, I am not very sure about
    sqoop-2
    but hadoop properties were available with sqoop1.
    restricting reducers
    restricting mappers
    restricting job queue

    I believe these parameters should be configurable from client
    instead
    of
    server and it should be configurable though "framework".


    On Tue, Oct 15, 2013 at 4:41 AM, Romain Rigaux <
    romain@cloudera.com
    wrote:
    I think the idea is to have the MapReduce jobs being executed in
    a
    certain JT queue.

    Romain


    On Tue, Oct 15, 2013 at 3:41 AM, Abraham Elmahrek <
    abe@cloudera.com
    wrote:
    Pawan,

    The Sqoop app in Hue is a front end for the Sqoop2 application.
    The
    sqoop1 and sqoop2 applications differ greatly:

    1. Sqoop 2 is the successor to Sqoop 1.
    2. Sqoop 2 has a client - server architecture.
    3. MR jobs are submitted from the Sqoop server in Sqoop2. In
    Sqoop1,
    they are submitted from the client.
    4. Connectors are much lighter and generic components have
    been
    handled in the "framework" component of Sqoop 2.
    5. Sqoop 2 is intended on being more secure than Sqoop 1. It
    starts
    off by managing connections so that information isn't
    provided
    over the
    command line.

    The list really does go on... there are several improvements to
    the
    design in Sqoop 2.

    What this means is that Java arguments are no longer simply
    passed
    to
    the MR job from the client. This is intentionally done. I
    believe
    you can
    provide a custom start script for the server to add Java
    arguments
    and
    those will be passed to the MR job, though I'm unsure.

    What are you doing with Sqoop that requires Hadoop properties
    to be
    set?
    Your feedback is extremely important and can potentially impact
    project
    direction!

    -Abe


    On Mon, Oct 14, 2013 at 11:03 AM, Abraham Elmahrek <
    abe@cloudera.com>wrote:
    Ah yes, but the difference is that we're using sqoop2, which
    does
    not
    support that. You may be able to add that to the sqoop server.

    -Abe


    On Mon, Oct 14, 2013 at 11:02 AM, pawan singh <
    jeet27.pawan@gmail.com>wrote:
    Sqoop supports hadoop job properties with -D option, like job
    queue(
    mapred.job.queue.name)


    On Mon, Oct 14, 2013 at 11:08 PM, Abraham Elmahrek <
    abe@cloudera.com>wrote:
    What job property would you like to set? I don't think you
    can
    set
    Hadoop Job properties unfortunately... but that's a question
    for
    the sqoop
    mailing list user@sqoop.apache.org.

    -Abe


    On Mon, Oct 14, 2013 at 4:57 AM, pawan singh <
    jeet27.pawan@gmail.com>wrote:
    Yes. Hadoop Job properties for sqoop jobs.


    On Mon, Oct 14, 2013 at 2:17 PM, Romain Rigaux <
    romain@cloudera.com>wrote:
    Do you mean some Hadoop job properties from the Sqoop job?

    Romain


    On Mon, Oct 14, 2013 at 4:27 PM, pawan singh <
    jeet27.pawan@gmail.com> wrote:
    Thanks Romain,

    That was the reason. How could we set job properties.


    On Fri, Oct 11, 2013 at 8:15 PM, Romain Rigaux <
    romain@cloudera.com> wrote:
    Which Hue version are you using?

    I see cdh4.3.0 for Sqoop2. As Sqoop2 is quickly evolving
    and
    its
    API changing, the version needs to be CDH4.4 is using Hue
    2.5.
    Romain


    On Fri, Oct 11, 2013 at 7:13 AM, pawan singh <
    jeet27.pawan@gmail.com> wrote:
    Hi,

    Sqoop App in hue is unresponsive while sqoop2 is running
    fine,

    [cloudera@localhost pawan]$ wget -qO -
    localhost:12000/sqoop/version
    {"revision":"","protocols":["1"],"date":"Mon May 27
    20:29:47 PDT
    2013","user":"jenkins","url":"git:\/\/ubuntu-slave02\/var\/lib\/jenkins\/workspace\/CDH4.3.0-Packaging-Sqoop2\/build\/cdh4\/sqoop2\/1.99.1-cdh4.3.0\/source\/common","version":"1.99.1-cdh4.3.0"}
    looking at the logs i found that:

    *HUE LOG:

    *[11/Oct/2013 07:05:50 +0000] http_client DEBUG *GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    [11/Oct/2013 07:05:50 +0000] middleware INFO
    Processing
    exception: 'HTTPError' object has no attribute 'reason':
    Traceback (most
    recent call last):
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/core/handlers/base.py",
    line 100, in get_response
    response = callback(request, *callback_args,
    **callback_kwargs)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    60, in submissions
    return get_submissions(request)
    File
    "/home/cloudera/workspace/hue/build/env/lib/python2.6/site-packages/Django-1.2.3-py2.6.egg/django/views/decorators/cache.py",
    line 69, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/submission.py", line
    54, in get_submissions
    response.update(handle_rest_exception(e, _('Could
    not
    get
    submissions.')))
    File
    "/home/cloudera/workspace/hue/apps/sqoop/src/sqoop/api/exception.py",
    line
    31, in handle_rest_exception
    reason = e.get_parent_ex().reason
    AttributeError: 'HTTPError' object has no attribute
    'reason'



    *Sqoop LOG:

    *2013-10-11 10:05:50,843 ERROR
    server.SqoopProtocolServlet
    [org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:53)]
    *Exception in GET
    http://localhost:12000/sqoop/v1/submission/history/all*
    org.apache.sqoop.common.SqoopException:
    SERVER_0003:Invalid
    HTTP
    request - Do not know what to do.
    at
    org.apache.sqoop.handler.SubmissionRequestHandler.handleEvent(SubmissionRequestHandler.java:75)
    at
    org.apache.sqoop.server.v1.SubmissionServlet.handleGetRequest(SubmissionServlet.java:39)
    at
    org.apache.sqoop.server.SqoopProtocolServlet.doGet(SqoopProtocolServlet.java:48)
    at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
    at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at
    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at
    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at
    org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at
    org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at
    org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at
    org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at
    org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at
    org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
    at
    org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
    at
    org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
    at
    org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    at java.lang.Thread.run(Thread.java:662)*

    *

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails
    from
    it, send an email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    To unsubscribe from this group and stop receiving emails
    from
    it,
    send an email to hue-user+unsubscribe@cloudera.org.

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202
    --

    ---
    You received this message because you are subscribed to the Google
    Groups "CDH Users" group.
    To unsubscribe from this group and stop receiving emails from it,
    send
    an email to cdh-user+unsubscribe@cloudera.org.
    For more options, visit
    https://groups.google.com/a/cloudera.org/groups/opt_out.


    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202


    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202


    --
    *Thanks and Regards:*
    Pawan Kumar Singh
    Mob: +91- 9654515202

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouphue-user @
categorieshadoop
postedOct 11, '13 at 2:13p
activeNov 25, '13 at 4:08p
posts18
users4
websitecloudera.com
irc#hadoop

People

Translate

site design / logo © 2022 Grokbase