Uploaded image for project: 'Hive'
  1. Hive
  2. HIVE-6754

Inconsistent default for hive.exec.drop.ignorenonexistent

Log workAgile BoardRank to TopRank to BottomBulk Copy AttachmentsBulk Move AttachmentsAdd voteVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Patch Available
    • Trivial
    • Resolution: Unresolved
    • 0.12.0
    • None
    • Configuration
    • None

    Description

      Dropping a non existing table returns no errors

      • when IF EXISTS is added
      • when hive.exec.drop.ignorenonexistent is set to true

      The default configuration in hive-default.xml.template sets hive.exec.drop.ignorenonexistent to true.

      However this create a inconsistent default behaviour when DROP TABLE is executed on a non existing table, when the if exists clause is not used.

      My suggestion would be to have the default set to false, to align the behavior to the way it's used in SQL.

      Attachments

        1. HIVE-6754.01.patch
          1.0 kB
          Reuben Kuhnert

        Issue Links

        Activity

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

          People

            sircodesalot Reuben Kuhnert Assign to me
            natalinobusa Natalino Busa

            Dates

              Created:
              Updated:

              Slack

                Issue deployment