Skip to content
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

Issue 1683 and 1955 composite search param schema change and implementation of system history #1996

Merged
merged 29 commits into from
Mar 2, 2021

Conversation

punktilious
Copy link
Collaborator

No description provided.

punktilious and others added 20 commits February 19, 2021 11:33
Signed-off-by: Robin Arnold <robin.arnold23@ibm.com>
… to retrieve data

Signed-off-by: Robin Arnold <robin.arnold23@ibm.com>
Signed-off-by: Robin Arnold <robin.arnold23@ibm.com>
Signed-off-by: Robin Arnold <robin.arnold23@ibm.com>
Signed-off-by: Robin Arnold <robin.arnold23@ibm.com>
Issue 1683/1955 share dev work to feature branch
…upgrade if table is empty. Addresses issue 1847.

Signed-off-by: Robin Arnold <robin.arnold23@ibm.com>
Signed-off-by: Robin Arnold <robin.arnold23@ibm.com>
Signed-off-by: Mike Schroeder <mschroed@us.ibm.com>
Issue #1683 - query builder changes for composite search
Signed-off-by: Robin Arnold <robin.arnold23@ibm.com>
Issue 1683 robin merged and fixed broken unit test
Signed-off-by: Robin Arnold <robin.arnold23@ibm.com>
Signed-off-by: Robin Arnold <robin.arnold23@ibm.com>
Signed-off-by: Mike Schroeder <mschroed@us.ibm.com>
Issue #1683 - wrap log.fine stmts, add testcases
…sub parameter. Change postgres tuning default to 7 based on test results

Signed-off-by: Robin Arnold <robin.arnold23@ibm.com>
… flag to logical_resources

Signed-off-by: Robin Arnold <robin.arnold23@ibm.com>
issue 1683 fixed db2 and postgres stored procs. Added 1958 is_deleted…
Signed-off-by: Robin Arnold <robin.arnold23@ibm.com>
…ser guide

Signed-off-by: Robin Arnold <robin.arnold23@ibm.com>
Issue 1683 and 1955 resolved conflicts with main and updated user guide
Copy link
Contributor

@michaelwschroeder michaelwschroeder left a comment

Choose a reason for hiding this comment

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

LGTM - just some copyright/formatting comments

Signed-off-by: Robin Arnold <robin.arnold23@ibm.com>
/**
* Utility to create all the tables associated with a particular resource type
*/
public class FhirResourceTableGroup455 {
Copy link
Member

Choose a reason for hiding this comment

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

It might be a bit cleaner just to download the fhir-persistence-schema cli jar (version 4.5.5) and execute it like an external program

Copy link
Member

Choose a reason for hiding this comment

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

I had originally put in a placeholder hook in the fhir-persistence-schema's pom.xml for doing just that:

<plugin>
    <artifactId>exec-maven-plugin</artifactId>
    <version>1.6.0</version>
    <groupId>org.codehaus.mojo</groupId>
    <executions>
        <execution>
            <id>deployPriorVersions</id>
            <phase>test</phase>
            <goals>
                <goal>exec</goal>
            </goals>
            <configuration>
                <executable>bash</executable>
                <commandlineArgs>deployPriorVersions.sh</commandlineArgs>
            </configuration>
        </execution>
    </executions>
</plugin>

However, at the time the fhir-persistence-schema didn't support the instantiation of derby dbs, and so I had to revert to this pattern where I copy-pasted the old FhirResourceTableGroup into the project as a test dependency.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Worth discussing, especially if we decide to make a breaking change to our schema model apis. But I do like the idea of the build being standalone and not breaking when some old release gets purged from a repo.

Comment on lines +65 to +66
// Type of change C - Create, U - Update, S - Soft Delete. H - Hard Delete
public static final String CHANGE_TYPE = "CHANGE_TYPE";
Copy link
Member

Choose a reason for hiding this comment

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

is this supposed to align with constants in ResourceChangeLogRecord ? I didn't see the distinction between soft delete and hard delete in that one, so wasn't sure if this comment was accurate or not.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

It was a comment for the future when we support hard-delete.

Signed-off-by: Robin Arnold <robin.arnold23@ibm.com>
Signed-off-by: Robin Arnold <robin.arnold23@ibm.com>
issue 1955 use resource subset for all operations in schema tool
Copy link
Member

@lmsurpre lmsurpre left a comment

Choose a reason for hiding this comment

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

LGTM

@punktilious punktilious merged commit 5a3fb1f into main Mar 2, 2021
@punktilious punktilious deleted the issue-1683 branch March 2, 2021 01:00
@@ -419,27 +442,25 @@ public Table addResourceTokenRefs(List<IDatabaseObject> group, String prefix) {
Table tbl = Table.builder(schemaName, tableName)
.setVersion(FhirSchemaVersion.V0008.vid())
Copy link
Member

Choose a reason for hiding this comment

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

This should have been bumped to V0009 here but we missed it :-(

lmsurpre added a commit that referenced this pull request Mar 4, 2021
We missed this as part of #1996, so anyone that has applied these updates to a DB since that change now has the wrong
version of that object.  Since that change was never released, I think we're OK just to fix it now (and help anyone
riding the bleeding edge to manually fix their VERSION_HISTORY table).

Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre added a commit that referenced this pull request Mar 4, 2021
We missed this as part of #1996, so anyone that has applied these updates to a DB since that change now has the wrong
version of that object.  Since that change was never released, I think we're OK just to fix it now (and help anyone
riding the bleeding edge to manually fix their VERSION_HISTORY table).

Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
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.

4 participants