-
Notifications
You must be signed in to change notification settings - Fork 157
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
Refactor payload persistence to its own visitor in Bundle processing #3145
Labels
breaking-change-java
Identifies a change in a method signature that an implementer may use.
technical debt
Comments
lmsurpre
added
the
breaking-change-java
Identifies a change in a method signature that an implementer may use.
label
Jan 26, 2022
punktilious
added a commit
that referenced
this issue
Feb 8, 2022
…r bundle processing Signed-off-by: Robin Arnold <robin.arnold@ibm.com>
punktilious
added a commit
that referenced
this issue
Feb 14, 2022
Signed-off-by: Robin Arnold <robin.arnold@ibm.com>
punktilious
added a commit
that referenced
this issue
Feb 15, 2022
Signed-off-by: Robin Arnold <robin.arnold@ibm.com>
punktilious
added a commit
that referenced
this issue
Feb 15, 2022
…le deleted resources Signed-off-by: Robin Arnold <robin.arnold@ibm.com>
punktilious
added a commit
that referenced
this issue
Feb 16, 2022
Signed-off-by: Robin Arnold <robin.arnold@ibm.com>
lmsurpre
added a commit
that referenced
this issue
Feb 16, 2022
issue #3145 move offload processing to its own interaction visitor
QA for this will be included with the QA for 3293: #3293 (comment) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
breaking-change-java
Identifies a change in a method signature that an implementer may use.
technical debt
Describe the bug
Currently the payload persistence step is invoked within the FHIRRestInteractionVisitorReferenceMapping visitor, which is the last time the resource is modified and therefore the first opportunity to store the payload.
This, is a little obscure. It could be much clearer (with probably very little performance impact) to loop through the Bundle entries again to perform the offload in a dedicated visitor. This would only need to be done if offload were enabled - which requires a FHIRPersistence method to support this check.
Environment
Which version of IBM FHIR Server? main
The text was updated successfully, but these errors were encountered: