Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.99.5
    • sqoop2-client
    • None

    Description

      Currently, each ResourceRequest hold its own authToken and shared within the ResourceRequest. SqoopClient uses different instance of ResourceRequest according different types of requests. This makes SqoopClient may needs to do Kerberos authentication for different requests even the requests are within one client.

      It is ideal to share the authToken within SqoopClient so that the the Kerberos authentication status can be shared and no redundant authentication process is needed if it is already authenticated by one request.

      Attachments

        1. SQOOP-1960.2.patch
          11 kB
          Richard
        2. SQOOP-1960.3.patch
          11 kB
          Richard
        3. SQOOP-1960.patch
          1 kB
          Richard

        Issue Links

          Activity

            People

              richard_zhou Richard
              jerrychenhf Haifeng Chen
              Votes:
              0 Vote for this issue
              Watchers:
              5 Stop watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Slack

                  Issue deployment