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

Decouple getConstraintsInformation from hive.ql.metadata.Table

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

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • Impala 4.1.0
    • Frontend
    • None
    • ghx-label-8

    Description

      After HIVE-22782, ql.metadata.Table object has no methods to set PrimaryKeyInfo and ForeignKeyInfo alone. However, we call these two functions In DescribeResultFactory to set constraints and pass the table into HiveMetadataFormatUtils. Instead of calling the methods from table, we can directly pass PrimaryKeyInfo and ForeignKeyInfo to HiveMetadataFormatUtils so that Impala won't be influenced even though the table class changes interface.

      Additionally, we can get rid of ql.metadata.Table for getTableInformation altogether since it just needs metastore.api.Table internally.

      Attachments

        Activity

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

          People

            hsnusonic Yu-Wen Lai
            hsnusonic Yu-Wen Lai
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment