Details

    • Technical task
    • Status: Stalled (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • 12.1
    • Server
    • None

    Description

      A normal user should only be able to flush tables in ones own catalog

      • flush table with read lock should only affect tables in the current catalog.

      The 'def' root user should be able flush tables for all catalogs.

      This may be hard to do for first version, so for this one we could just disable the flush for non def root catalog users.

      Attachments

        Activity

          shulga Dmitry Shulga added a comment - - edited

          Lets consider the requirement "A normal user should only be able to flush tables in ones own catalog":
          Does it relate only to the case when no tables listed in the statement. In other words, should we allow flushing of tables in someone's else catalog if these tables are explicitly listed in table_list
          e.g.

           FLUSH TABLES table_in_own_catalog, cat_1.table_1, cat_2.table_2
          


          where cat_1.table_1, cat_2.table_2 - are tables located in not ones owned catalogs?

          The following question is about the requirement "flush table with read lock should only affect tables in the current catalog"
          Do we consider here only the case when no tables listed explicitly for the statement 'FLUSH TABLES WITH READ LOCK'. That is, does this requirement mean that the next statement

          FLUSH TABLES cat_1.table_1, cat_2.table_2  WITH READ LOCK
          

          should work correct notwithstanding the fact that tables table_1 and table_t are from different catalog not ones owned?

          The following question is about the requirement "The 'def' root user should be able flush tables for all catalogs":
           Does 'root user' here mean the user located in the 'def' catalog and that has the privilege SUPER_ACL ?

          shulga Dmitry Shulga added a comment - - edited Lets consider the requirement "A normal user should only be able to flush tables in ones own catalog": Does it relate only to the case when no tables listed in the statement. In other words, should we allow flushing of tables in someone's else catalog if these tables are explicitly listed in table_list e.g. FLUSH TABLES table_in_own_catalog, cat_1.table_1, cat_2.table_2 where cat_1.table_1, cat_2.table_2 - are tables located in not ones owned catalogs? The following question is about the requirement "flush table with read lock should only affect tables in the current catalog" Do we consider here only the case when no tables listed explicitly for the statement 'FLUSH TABLES WITH READ LOCK'. That is, does this requirement mean that the next statement FLUSH TABLES cat_1.table_1, cat_2.table_2 WITH READ LOCK should work correct notwithstanding the fact that tables table_1 and table_t are from different catalog not ones owned? The following question is about the requirement "The 'def' root user should be able flush tables for all catalogs":  Does 'root user' here mean the user located in the 'def' catalog and that has the privilege SUPER_ACL ?

          People

            shulga Dmitry Shulga
            monty Michael Widenius
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.