Skip to content

7152 - Add resource type to HFJ_RESOURCE_MODIFIED's PK to avoid conflicts #7154

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

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

another-luis
Copy link
Contributor

No description provided.

@robogary
Copy link
Contributor

Formatting check succeeded!

@another-luis another-luis requested a review from a team as a code owner July 29, 2025 19:25
Copy link
Collaborator

@tadgh tadgh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved pending minor stuff. Probably good to get a second set of eyes on this too.

type: fix
issue: 7152
jira: SMILE-10226
title: "Modified resources could potentially be removed from the subscription list of they shared ID and Version with
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

issue: rewrite this changelog. There's a typo in it, and it should be written from a user failure scenario point of view. Something like:

Previously, subscriptions could occasionally fail to be delivered if a resource had the same ID as a resource of another type, (e.g. `Patient/abc-123` and `Observation/abc-123`), as well as the same version number. This has been corrected, and now the resource type is part of the primary key, ensuring uniqueness during clearing of the table. 

{
version.onTable("HFJ_RESOURCE_MODIFIED").dropPrimaryKey("20250729.1");
version.onTable("HFJ_RESOURCE_MODIFIED").addPrimaryKey("20250729.2", "RES_ID", "RES_VER", "RESOURCE_TYPE");
}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question: is this not making it into 8.4.0? Check with the support person/the ticket to ensure that this is known to them, and it isn't expected for 8.4.0

@another-luis another-luis changed the base branch from master to rel_8_4 July 31, 2025 16:09
@another-luis another-luis changed the base branch from rel_8_4 to master July 31, 2025 16:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants