[
https://issues.apache.org/jira/browse/AIRAVATA-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15947379#comment-15947379
]
Marcus Christie commented on AIRAVATA-2350:
-------------------------------------------
I updated the dev database on gw62 and also updated the jetstream testing
database at 149.165.172.163
{code:sql}
MySQL [master_app_catalog]> alter table USER_RESOURCE_PROFILE drop primary key,
add primary key (USER_ID, GATEWAY_ID);
MySQL [master_app_catalog]> alter table USER_COMPUTE_RESOURCE_PREFERENCE drop
primary key, add primary key (RESOURCE_ID, USER_ID, GATEWAY_ID);
MySQL [master_app_catalog]> alter table USER_STORAGE_PREFERENCE drop primary
key, add primary key (STORAGE_RESOURCE_ID, USER_ID, GATEWAY_ID);
{code}
As you can see I'm also updating the keys of USER_COMPUTE_RESOURCE_PREFERENCE
and USER_STORAGE_PREFERENCE to include GATEWAY_ID, which also required some
code changes.
> USER_RESOURCE_PROFILE DB Primary Key should include the gateway_id
> ------------------------------------------------------------------
>
> Key: AIRAVATA-2350
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2350
> Project: Airavata
> Issue Type: Bug
> Components: Registry API
> Affects Versions: 0.17
> Reporter: Marcus Christie
> Fix For: 0.17
>
>
> If I recall correctly, the problem that this caused was that a user with the
> same username in two gateways was not able to create a USER_RESOURCE_PROFILE
> in the second gateway because of the PK violation.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
