Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bugfix: S3C-2899 support v1 in Delimiter, DelimiterMaster #1028

Merged
merged 1 commit into from
May 20, 2020

Conversation

jonathan-gramain
Copy link
Contributor

@jonathan-gramain jonathan-gramain commented May 19, 2020

The two listing methods Delimiter and DelimiterMaster now support v1
versioning key format in addition to v0.

Modify the listing algo classes to support buckets in v1 versioning
key format, in addition to v0.

Enhance existing unit tests to check the result of getMDParams()

Requires merging PR #1018 first.

@bert-e
Copy link
Contributor

bert-e commented May 19, 2020

Hello jonathan-gramain,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Status report is not available.

@bert-e
Copy link
Contributor

bert-e commented May 19, 2020

Integration data created

I have created the integration data for the additional destination branches.

The following branches will NOT be impacted:

  • development/6.4
  • stabilization/7.4.6

Follow integration pull requests if you would like to be notified of
build statuses by email.

@bert-e
Copy link
Contributor

bert-e commented May 19, 2020

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

Peer approvals must include a mandatory approval from @jonathan-gramain.

skipping() {
if (this.vFormat === BucketVersioningKeyFormat.v0) {
Copy link
Contributor

@miniscruff miniscruff May 19, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just want to mention the idea of having each version be either a class or an object instead of putting a bunch of these if's around. Could have just one if in a factory method somewhere then everything else is standard.
Mabye a base Bucket Version class if there is a lot of similarities.
Alternatively, an object that maps the v0 and v1 methods around in one place.
Something along the lines of:

const versionRouter = {
  [BucketVersioningKeyFormat.v0]: {
    skipping: this.skippingV0,
    other: this.otherv0,
  },
  [BucketVersioningKeyFormat.v1]: { etc }
}

// then map through this:
versionRouter[this.vFormat].skipping()
// make wrap it with a check the version exists if required

Anyway, just ideas.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It sounds better indeed since there is a common pattern, especially after the migration states are introduced (v0 to v1)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated

},
},
];
testCases.forEach(testCase => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am pretty sure you can reduce some typing here by doing this:

testCases.forEach(({v0Params, v1Params}) => {
    // can then just use v0Params instead of testCase.v0Params
}

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah yeah, did not think about using object deconstruction here

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated

@bert-e
Copy link
Contributor

bert-e commented May 19, 2020

History mismatch

Merge commit #24faf5e6ba5698a10bf0037b71ca8e6ec93fe2d1 on the integration branch
w/7.7/bugfix/S3C-2899-vformatV1delimiterMaster is merging a branch which is neither the current
branch bugfix/S3C-2899-vformatV1delimiterMaster nor the development branch
development/7.7.

It is likely due to a rebase of the branch bugfix/S3C-2899-vformatV1delimiterMaster and the
merge is not possible until all related w/* branches are deleted or updated.

Please use the reset command to have me reinitialize these branches.

@jonathan-gramain jonathan-gramain force-pushed the bugfix/S3C-2899-vformatV1delimiterMaster branch from a3e73fe to 334c2bf Compare May 19, 2020 23:38
@jonathan-gramain
Copy link
Contributor Author

@bert-e reset

@bert-e
Copy link
Contributor

bert-e commented May 19, 2020

Reset complete

I have successfully deleted this pull request's integration branches.

@bert-e
Copy link
Contributor

bert-e commented May 19, 2020

Integration data created

I have created the integration data for the additional destination branches.

The following branches will NOT be impacted:

  • development/6.4
  • stabilization/7.4.6

Follow integration pull requests if you would like to be notified of
build statuses by email.

@bert-e
Copy link
Contributor

bert-e commented May 19, 2020

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

Peer approvals must include a mandatory approval from @jonathan-gramain.

The two listing methods Delimiter and DelimiterMaster now support v1
versioning key format in addition to v0.

Modify the listing algo classes to support buckets in v1 versioning
key format, in addition to v0.

Enhance existing unit tests to check the result of getMDParams()
@jonathan-gramain jonathan-gramain force-pushed the bugfix/S3C-2899-vformatV1delimiterMaster branch from 334c2bf to fb89b4e Compare May 19, 2020 23:45
@bert-e
Copy link
Contributor

bert-e commented May 19, 2020

History mismatch

Merge commit #b431e35857eb1715ad5038b817bad58dd18c94cf on the integration branch
w/7.7/bugfix/S3C-2899-vformatV1delimiterMaster is merging a branch which is neither the current
branch bugfix/S3C-2899-vformatV1delimiterMaster nor the development branch
development/7.7.

It is likely due to a rebase of the branch bugfix/S3C-2899-vformatV1delimiterMaster and the
merge is not possible until all related w/* branches are deleted or updated.

Please use the reset command to have me reinitialize these branches.

@jonathan-gramain
Copy link
Contributor Author

@bert-e reset

@bert-e
Copy link
Contributor

bert-e commented May 19, 2020

Reset complete

I have successfully deleted this pull request's integration branches.

@bert-e
Copy link
Contributor

bert-e commented May 19, 2020

Integration data created

I have created the integration data for the additional destination branches.

The following branches will NOT be impacted:

  • development/6.4
  • stabilization/7.4.6

Follow integration pull requests if you would like to be notified of
build statuses by email.

@bert-e
Copy link
Contributor

bert-e commented May 19, 2020

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

Peer approvals must include a mandatory approval from @jonathan-gramain.

@jonathan-gramain jonathan-gramain changed the base branch from development/7.4 to development/8.1 May 20, 2020 05:40
@bert-e
Copy link
Contributor

bert-e commented May 20, 2020

Branches have diverged

This pull request's source branch bugfix/S3C-2899-vformatV1delimiterMaster has diverged from
development/8.1 by more than 50 commits.

To avoid any integration risks, please re-synchronize them using one of the
following solutions:

  • Merge origin/development/8.1 into bugfix/S3C-2899-vformatV1delimiterMaster
  • Rebase bugfix/S3C-2899-vformatV1delimiterMaster onto origin/development/8.1

Note: If you choose to rebase, you may have to ask me to rebuild
integration branches using the reset command.

@jonathan-gramain jonathan-gramain changed the base branch from development/8.1 to development/7.4 May 20, 2020 05:40
@bert-e
Copy link
Contributor

bert-e commented May 20, 2020

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

Peer approvals must include a mandatory approval from @jonathan-gramain.

@jonathan-gramain
Copy link
Contributor Author

@bert-e approve

@bert-e
Copy link
Contributor

bert-e commented May 20, 2020

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

  • ✔️ development/7.4

  • ✔️ development/7.7

  • ✔️ development/8.1

The following branches will NOT be impacted:

  • development/6.4
  • stabilization/7.4.6

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

  • Any commit you add on the source branch will trigger a new cycle after the
    current queue is merged.
  • Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented May 20, 2020

I have successfully merged the changeset of this pull request
into targetted development branches:

  • ✔️ development/7.4

  • ✔️ development/7.7

  • ✔️ development/8.1

The following branches have NOT changed:

  • development/6.4
  • stabilization/7.4.6

Please check the status of the associated issue S3C-2899.

Goodbye jonathan-gramain.

@bert-e bert-e merged commit cd9bdcf into development/7.4 May 20, 2020
@bert-e bert-e deleted the bugfix/S3C-2899-vformatV1delimiterMaster branch May 20, 2020 22:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants