Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-9903

Queries on a Kudu table call openTable multiple times

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • Impala 3.4.0
    • Impala 4.0.0
    • Frontend
    • ghx-label-1

    Description

      When testing the results of KUDU-1802 I saw that each query ran would result in 5 GetTableSchema requests to the Kudu master server. The request comes from each KuduClient.openTable call in the Impala frontend.
      https://github.com/apache/impala/search?l=Java&q=openTable

      Ideally Impala would only call KuduClient.openTable once and then use the returned KuduTable object for the length of the query. That would result in 5x fewer remote RPC calls to the Kudu master server per query.

      Attachments

        Issue Links

        relates to

        Improvement - An improvement or enhancement to an existing feature or task. KUDU-1802 Deserializing scan tokens should avoid round-trip to master

        • Major - Major loss of function.
        • Resolved

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            granthenke Grant Henke
            granthenke Grant Henke
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment