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

KuduTableSink spends a lot of CPU copying KuduColumnSchemas

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

Details

    • ghx-label-8

    Description

      I noticed Impala spending a significant amount of CPU time in KuduTableSink::Send creating and destroying KuduColumnSchemas.

      See KUDU-2731 for more information.

      Impala could wait for a better option from the Kudu API, or could cache information about nullability of columns outside the hot loop in Send.

      Attachments

        Issue Links

        Activity

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

          People

            tlipcon Todd Lipcon
            wdberkeley William Berkeley
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment