Skip to content

Credit for #6224 #6418

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Oct 30, 2024
Merged

Credit for #6224 #6418

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions ...esources/ca/uhn/hapi/fhir/changelog/7_8_0/6224-resolve-tag-definition-in-same-thread.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
---
type: perf
issue: 6224
title: "The JPA server will no longer use a separate thread and database connection
to resolve tag definitions. This should improve performance in some cases, and
resolves compatibility issues for some environments. Thanks to Ibrahim (Trifork A/S)
for the pull request!"
5 changes: 5 additions & 0 deletions pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -952,6 +952,11 @@
<id>SevcikMichal</id>
<name>Michal Sevcik</name>
</developer>
<developer>
<id>iyt-trifork</id>
<name>Ibrahim</name>
<organization>Trifork A/S</organization>
</developer>
</developers>

<licenses>
Expand Down
Loading