Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
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
Attachments
Issue Links
- links to