Updates for cloud Data Export and migration pipelines. #1527
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes three issues.
JobDataset.phpfile. Thesession_recordstable has thestart_time_tsandend_time_tscolumns that should be used for the start time and end time parameters. It was trying to use the instance table which does not have those columns.hosttable to have a single autoincrement column instead of a composite autoincrement. In PR Change account, instance and instance_type tables to have single unique auto increment column #1263 we changed most of the cloud realm dimension tables that use a composite autoincrement key to use a single unique column for the autoincrement key. At the time thehosttable was not used for anything so it was not converted. It is now being used in the cloud instance viewer and Data Export and should be changed to match the other cloud realm dimension tables so it can provide accurate data. The changes for thehosttable match changes made for theinstance,account, andinstance_typetables in PR Change account, instance and instance_type tables to have single unique auto increment column #1263 and changing account, instance and instance_type tables to have global un… #1272 including a SQL statement that is run during the migration to add the new autoincrement key and update rows in the event table with the appropriatehost_id.migration-9_0_0-9_5_0in them meant they automatically ran. We do not want that as not all XDMoD installations may be using the cloud realm.Tests performed
Tested fresh install and upgrade in docker
Checklist: