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.

Sign up for GitHub

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

Jump to bottom

Switch protocol selection to third_party_copy read/write #3254

Closed
bari12 opened this issue Jan 23, 2020 · 0 comments
Closed

Switch protocol selection to third_party_copy read/write #3254

bari12 opened this issue Jan 23, 2020 · 0 comments
Assignees
@bari12 @rcarpa
Labels
enhancement Transfers
Milestone
1.28.0

Comments

@bari12
Copy link
Member

bari12 commented Jan 23, 2020

Motivation

This needs to be changed in various parts of the code from third_party_copy to use third_party_copy_read and third_party_copy_write. In a later feature release, the third_party_copy column can then be removed.
@bari12 bari12 self-assigned this Jan 23, 2020
@cserf cserf mentioned this issue Apr 13, 2021
Merged
rcarpa added a commit to rcarpa/rucio that referenced this issue Mar 3, 2022
@rcarpa
Core & Internals: use third_party_copy_read/write. Closes rucio#3254
4a1f12e 
There is a desire to have different configurations for an RSE
when used as source or destination in a transfer. The old
third_party_copy doesn't allow that, so the _read/_write was
introduced to the database at some moment, but were ignored
by rucio code.

Switch to using these setting by default. Add a database migration
to copy the values from the existing field. Also ensure that
setting third_party_copy only when creating a protocol results in
the population of all 3 fields.
@bari12 bari12 closed this as completed in 63d9c21 Mar 10, 2022
bari12 added a commit that referenced this issue Mar 10, 2022
@bari12
Merge pull request #5315 from rcarpa/patch-3254-third_party_copy_read…
680b888 
…_write

Core & Internals: use third_party_copy_read/write. Closes #3254
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bari12 bari12

@rcarpa rcarpa

Labels
enhancement Transfers
Projects
None yet
Milestone
1.28.0
Development

No branches or pull requests
2 participants
@bari12 @rcarpa