Uploaded image for project: 'Calcite'
  1. Calcite
  2. CALCITE-2503

AvaticaCommonsHttpClientImpl client needs to set user-token on HttpClientContext before sending the request

Rank to TopRank to BottomVotersStop watchingWatchersConvert to sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: avatica-1.13.0
    • Component/s: None
    • Labels:
      None

      Description

      One of the Avatica client implementations, AvaticaCommonsHttpClientImpl, uses a PoolingHttpClientConnectionManager. When using mutual authentication on the client pool, we need to ensure that we are setting a user-token on the HttpClientContext, otherwise it ends up creating a new connection everytime and not reusing it. See:  https://hc.apache.org/httpcomponents-client-ga/tutorial/html/advanced.html for more details

      This results in significant perf degradation since every new connection tries to complete a SSL handshake (which is expensive)

      See: https://stackoverflow.com/questions/548029/how-much-overhead-does-ssl-impose

        Attachments

          Activity

          $i18n.getText('security.level.explanation', $currentSelection) Viewable by All Users
          Cancel

            People

            • Assignee:
              karanmehta93 Karan Mehta
              Reporter:
              karanmehta93 Karan Mehta

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment