-
Notifications
You must be signed in to change notification settings - Fork 301
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
Decide on Message format for ActiveMQ Message to AMI #70
Comments
Is it related to the INCOMPLETE message ? Do we have another issue related to it ? Motivation:
|
Yes, the epic issue for this is #69. I just noticed though, we added the INCOMPLETE state in the schema.sql, but not in models.py or constants.py yet. |
I checked on next and could not find the constants change ? models.py is not necessary. |
Yes, as I said, it's not there 😄 |
but I did the merge request (100% sure)... |
It doesn't seem to be in there. Only schema.sql and the migrate_repo file. |
But just coming back to the original question. I think one message is enough, no need to have one for DATASET and one for CONTAINER. |
did_type in the message ? |
Yes, I think so. To some extent it is redundant, as e.g. AMI would know it anyway, but maybe this is consumed by other services too which do not necessarily know. |
issue #68 is about 'Protect storage from too many requests ' ? |
Do we need two different messages? One for Dataset one for Container or is the same one sufficient?
Migrated from JIRA RUCIO-2810
The text was updated successfully, but these errors were encountered: