[
https://issues.apache.org/jira/browse/AIRAVATA-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15947499#comment-15947499
]
Marcus Christie edited comment on AIRAVATA-2350 at 3/29/17 5:09 PM:
--------------------------------------------------------------------
Found a problem with the join from USER_COMPUTE_RESOURCE_PREFERENCE ->
USER_RESOURCE_PROFILE. In JPA it is joining only on the USER_ID. This can
result in duplicate records when querying USER_COMPUTE_RESOURCE_PREFERENCE when
joining to USER_RESOURCE_PROFILE if a user with a USER_ID has multiple accounts
in different gateways.
----
This is fixed now
was (Author: marcuschristie):
Found a problem with the join from USER_COMPUTE_RESOURCE_PREFERENCE ->
USER_RESOURCE_PROFILE. In JPA it is joining only on the USER_ID. This can
result in duplicate records when querying USER_COMPUTE_RESOURCE_PREFERENCE when
joining to USER_RESOURCE_PROFILE if a user with a USER_ID has multiple accounts
in different gateways.
---
This is fixed now
> 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
> Assignee: 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)
