Details

    Description

      Make s3_debug dynamic to allow users to enable debug logging of the S3 communication without having to restart mariadbd.

      Attachments

        Activity

          Patch ready for 10.6, just need to get other patches in 10.6 approved so that I can push all at once.

          monty Michael Widenius added a comment - Patch ready for 10.6, just need to get other patches in 10.6 approved so that I can push all at once.

          Fix was easy, but I also had fix a bug in libmarias3, which took some extra time

          monty Michael Widenius added a comment - Fix was easy, but I also had fix a bug in libmarias3, which took some extra time

          Full details for my pull request:

          Monty's update pulled two years of updates for libmarias3 so that he could get the latest commit. This included a bunch of other bug fixes. It was found a long time ago that the API call in libmarias3 that s3_protocol_version used wasn't actually doing anything, this was fixed in libmarias3 but MariaDB Server hadn't picked up that fix.

          Now with the update the fix has been picked up and anyone who might be using "Original" with AWS might find their installation no longer works (and a test will fail), there are exceptions to this, these are us-east-1 which still allows a legacy access method or by using the AWS region in the domain (such as s3.us-east-2.amazonaws.com).

          As "Original" never really worked before, my patch now makes this the same as "Amazon", just in case someone is using it. It adds "Legacy" for the protocol v1 to keep it close to the naming conventions. It also adds "Path" and "Domain" which are really what v1 and v2 are under the hood, a future version should remove the "Legacy", "Original" and "Amazon" options.

          Finally, my patch fixes the the tests around the S3 engine.

          TheLinuxJedi Andrew Hutchings (Inactive) added a comment - Full details for my pull request: Monty's update pulled two years of updates for libmarias3 so that he could get the latest commit. This included a bunch of other bug fixes. It was found a long time ago that the API call in libmarias3 that s3_protocol_version used wasn't actually doing anything, this was fixed in libmarias3 but MariaDB Server hadn't picked up that fix. Now with the update the fix has been picked up and anyone who might be using "Original" with AWS might find their installation no longer works (and a test will fail), there are exceptions to this, these are us-east-1 which still allows a legacy access method or by using the AWS region in the domain (such as s3.us-east-2.amazonaws.com). As "Original" never really worked before, my patch now makes this the same as "Amazon", just in case someone is using it. It adds "Legacy" for the protocol v1 to keep it close to the naming conventions. It also adds "Path" and "Domain" which are really what v1 and v2 are under the hood, a future version should remove the "Legacy", "Original" and "Amazon" options. Finally, my patch fixes the the tests around the S3 engine.

          Monty has reviewed and approved already. Assigned to Daniel for second review.

          TheLinuxJedi Andrew Hutchings (Inactive) added a comment - Monty has reviewed and approved already. Assigned to Daniel for second review.

          I wasn't subscribed to this thread and hence didn't notice the need for the second reviewer's confirmation.

          nikitamalyavin Nikita Malyavin added a comment - I wasn't subscribed to this thread and hence didn't notice the need for the second reviewer's confirmation.

          pushed in 10.6

          serg Sergei Golubchik added a comment - pushed in 10.6

          People

            monty Michael Widenius
            monty Michael Widenius
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

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