Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-3833

Create system schema fails on namespace-mapping table for unprivileged user.

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

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Not A Problem
    • None
    • None
    • None
    • None

    Description

      Follow-on from PHOENIX-3652

      We found another case where a user without ADMIN permission tried to connect to Phoenix and failed because they tried to obtain the namespace descriptor.

      This one was coming out of the CREATE SCHEMA IF EXISTS call, kudos to Sergey Soldatov for getting to the bottom of this one.

      My existing test case had a bug which was masking this failure condition. Fixing that reproduces the issue.

      Attachments

        Issue Links

        Activity

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

          People

            elserj Josh Elser
            elserj Josh Elser
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment