Conversation
…-- still not fully working
…rovider for tool and index-set
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2454 +/- ##
===========================================
- Coverage 58.20% 29.33% -28.88%
===========================================
Files 1069 1011 -58
Lines 74278 71019 -3259
Branches 2166 1198 -968
===========================================
- Hits 43233 20830 -22403
- Misses 29028 49053 +20025
+ Partials 2017 1136 -881 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
| collection-response (ingest/bulk-update-task-status "PROV1" (:task-id response)) | ||
| collection-statuses (:collection-statuses collection-response)] | ||
| (is (= "COMPLETE" (:task-status collection-response))) | ||
| (is (= "Collection with concept-id [C1200000009-PROV1] is deleted. Can not be updated." |
There was a problem hiding this comment.
because we added a new index-set table which is treated like a concept, when these tests are run they were hardcoded to get the concept id as expected with the number of time the concept_seq_id would increment. Because index-set is also using the concept_seq_id to increment its id, the concept_seq_id was increased by one in all these tests.
| ;; instead. | ||
| [cmr.metadata-db.data.oracle.concepts.generic-documents])) | ||
| [cmr.metadata-db.data.oracle.concepts.generic-documents] | ||
| [cmr.metadata-db.data.oracle.concepts.index-set])) |
There was a problem hiding this comment.
added to allow index set to be seen by metadata db during sys tests later
| (println "cmr.metadata-db.migrations.092-update-cmr-sub-notifications-table up...") | ||
| (h/sql "ALTER TABLE METADATA_DB.CMR_SUB_NOTIFICATIONS DROP COLUMN AWS_ARN") | ||
| (h/sql "ALTER TABLE METADATA_DB.CMR_SUBSCRIPTIONS ADD AWS_ARN VARCHAR(2048) NULL")) | ||
| (when (h/column-exists? "CMR_SUB_NOTIFICATIONS" "AWS_ARN") |
There was a problem hiding this comment.
had to add this because my local had a wrong version of AWS_ARN and had to be replaced. This is helpful to any other dev with local db issues. This will not have adverse affects since the logic still remains the same
| (def ^:private index-sets-column-sql | ||
| "id NUMBER, | ||
| concept_id VARCHAR(255) NOT NULL, | ||
| native_id VARCHAR(1030) NOT NULL, |
There was a problem hiding this comment.
native_id is the id of the index-set
| (let [reshard-start-resp (bootstrap/start-reshard-index "1_small_collections_100_shards" {:synchronous true :num-shards 50 :elastic-name gran-elastic-name}) | ||
| task-id (:task-id reshard-start-resp)] | ||
| task-id (:task-id reshard-start-resp) | ||
| status-check-attempts (range 3)] |
There was a problem hiding this comment.
because some runs of this may be slow, it could take some time for reshard to finish, so I put 3 attempts here to prevent unnecessary failures on non-immediate completes
| :reshard-status "COMPLETE"} | ||
| (bootstrap/get-reshard-status "1_small_collections_100_shards" {:elastic-name gran-elastic-name :task-id task-id}))))) | ||
| (run! (fn [i] | ||
| (Thread/sleep 2000) ;; wait for 2 secs |
There was a problem hiding this comment.
put a wait here in case the reshard takes longer than expected
Overview
What is the objective?
To allow for disaster recovery and keeping track of historical changes of index-set.
What are the changes?
What areas of the application does this impact?
Indexer
Required Checklist
Additional Checklist