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

Extend Rucio to generic checksum column #2410

Open
bari12 opened this issue Mar 29, 2019 · 3 comments
Open

Extend Rucio to generic checksum column #2410

bari12 opened this issue Mar 29, 2019 · 3 comments

Comments

@bari12
Copy link
Member

bari12 commented Mar 29, 2019

Motivation

Right now Rucio only supports adler32 and md5 checksums via two specific columns for these checksums. This creates problems if a community has different checksums (e.g. CMS historically used crc checksums) and wants to store them. On the dev meeting on 2019-03-28 it was discussed to extend Rucio with a generic checksum column of string type. Multiple checksums can be added (comma-separated) to this column, always specifying the checksum type. E.g. md5:1234,adler32:5678,crc:123

We would have to specify a strategy in migrating to this new checksum column.

@mlassnig
Copy link
Contributor

Alternatively, a json column? I don't like string parsing too much

@bziemons
Copy link
Member

is #3538 related to this?

@bari12
Copy link
Member Author

bari12 commented Sep 21, 2020

Not really. We do provide already adler32 and md5 columns in the database. #3538 is just about an issue that at some parts of the code adler32 is falsly required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants