Release update (#636)

* EUGENE: update_kx_cluster_databases parameters which have been updated since last release * Version number and release notes update * add back .u.end to rdbstandard --------- Co-authored-by: eugene temlock <[email protected]>
DataIntellectTech · Mar 5, 2024 · 4c0720d · 4c0720d
1 parent 517fbc9
commit 4c0720d
Show file tree

Hide file tree

Showing 4 changed files with 15 additions and 3 deletions.
diff --git a/README.md b/README.md
@@ -41,12 +41,21 @@ Head to the address it gives you to check if your changes have worked. More info
 ## Licences
 Third party licenses have been used, see Licenses, Apache 2.0 and OpenLDAP, kdbldap.so   
 ## Release Notes
+- **5.0.3, Mar 2024**
+  * Fix defaulting of .save config in rdb
+  * Bug fix for syncexec queries on HTTP/qcon
+  * Bug fix for dataaccess API init
+  * Deferred responce now returns if fails or signals error
+  * Updating finspace.q API parameters to be up to date with AWS documentation
+  * Setting default start params in FinSpace
+  * finspaceservers.q will use the aws.list_kx_clusters direclty instead of matching it against csv
+  * Code restructure/small changes to allign with Finspace changes (unused as of release)
 - **5.0.2, Dec 2023**
   * Removed KDBFINSPACE env variable from required startup variable list
 - **5.0.1, Dec 2023**
   * Renaming TorQ Amazon Finspace project references to TorQ-Amazon-FinSpace-Starter-Pack
 - **5.0.0, Dec 2023**
-  * Updated TorQ to support AWS Finspace when using the new [TorQ-Finspace-Starter-Pack](https://dataintellecttech.github.io/TorQ-Amazon-FinSpace-Starter-Pack/)
+  * Updated TorQ to support AWS Finspace when using the new [TorQ-Amazon-Finspace-Starter-Pack](https://dataintellecttech.github.io/TorQ-Amazon-FinSpace-Starter-Pack/)
   * Updated support email references
   * Updated intall guide
   * log output can now be json file format: add '-jsonlogs true' flag on startup

diff --git a/code/common/finspace.q b/code/common/finspace.q
@@ -39,7 +39,8 @@ notifyhdb:{[cluster;changeset]
       // Ensuring that the changeset has successfully created before doing the HDB reload
       current:.finspace.checkstatus[(`.aws.get_changeset;.finspace.database;changeset[`id]);("COMPLETED";"FAILED");00:01;0wu];
       .lg.o[`notifyhdb;("notifying ",string[cluster]," to repoint to changeset ",changeset[`id])];
-      .aws.update_kx_cluster_databases[string[cluster];.aws.sdbs[.aws.db[.finspace.database;changeset[`id];.aws.cache["CACHE_1000";"/"]]];.aws.sdep["NO_RESTART"]]
+      awsdb:.aws.db[.finspace.database;changeset[`id];.aws.cache["CACHE_1000";"/"];""];
+      .aws.update_kx_cluster_databases[string[cluster];.aws.sdbs[awsdb];.aws.sdep["NO_RESTART"]]
       // TODO - Also need to figure out the ideal logic if a changeset fails to create. Possibly recreate and re-run notifyhd
    }
 

diff --git a/code/rdb/rdbstandard.q b/code/rdb/rdbstandard.q
@@ -18,3 +18,5 @@ upd:@[value;`upd;{insert}];                                 //value of upd
 
 /-set the upd function in the top level namespace
 upd:.rdb.upd
+
+.u.end:{[d] .rdb.endofday[d;()!()]};
diff --git a/config/dependency.csv b/config/dependency.csv
@@ -1,2 +1,2 @@
 app,version,dependency
-TorQ,5.0.2,
+TorQ,5.0.3,
Original file line number	Diff line number	Diff line change
Expand Up		@@ -18,3 +18,5 @@ upd:@[value;`upd;{insert}]; //value of upd

		/-set the upd function in the top level namespace
		upd:.rdb.upd

		.u.end:{[d] .rdb.endofday[d;()!()]};