Skip to content

Commit 096dd0d

Browse files
Merge pull request #119 from ianf-mongodb/DOCSP-28688
DOCSP-28688 Refresh Data Verification Screenshots
2 parents 49f5f92 + 9cebc28 commit 096dd0d

File tree

5 files changed

+19
-18
lines changed

5 files changed

+19
-18
lines changed
Loading
Binary file not shown.
Loading
Loading

source/jobs/data-verification/use-data-verification.txt

Lines changed: 19 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -10,30 +10,30 @@ Use Data Verification
1010
:depth: 1
1111
:class: singlecol
1212

13-
Data verification runs as a separate process that is tightly
13+
Data verification optionally runs as a separate process that is tightly
1414
coupled to a sync job. Data verification can be enabled for one-time
1515
sync jobs. This page details how to enable and debug the
1616
data verification process.
1717

1818
Enable Data Verification
1919
------------------------
2020

21-
You can enable data verification when :ref:`creating a sync job <rm-create-jobs>`
22-
on the :guilabel:`Data Migration` tab.
21+
You can optionally enable data verification when
22+
:ref:`creating a sync job <rm-create-jobs>` on the :guilabel:`Data Migration` tab.
2323

2424
On the :guilabel:`Migration Options` module, click the
2525
:guilabel:`Verify migrated data` check box for your sync job.
2626

27-
.. note:: Data Verification Duration
27+
.. note::
2828

2929
The Data Verification process can take as long or longer than the data sync job.
3030
You can click :guilabel:`Terminate` to cancel a Data Verification process.
3131

3232
To view status and metadata information about the data verification process
33-
for a sync job, click the :guilabel:`SYNC JOB / DATA VERIFICATION` slider.
33+
for a sync job, click the :guilabel:`Data Verification` drop-down menu:
3434

35-
.. image:: /img/jobs/data-verification/data-verification-click-slider.png
36-
:alt: Click Data Verification Slider
35+
.. image:: /img/jobs/data-verification/data-verification-click-dropdown.png
36+
:alt: Click Data Verification Drop-Down
3737

3838
Data Verification Overview
3939
--------------------------
@@ -72,23 +72,23 @@ A data verification process can be any of the following statuses:
7272
* - Status
7373
- Description
7474
* - ABORTED
75-
- A running data validation was unable to complete due to an error.
75+
- A running data verification was unable to complete due to an error.
7676
* - CANCELLED
77-
- The data validation process was cancelled by clicking :guilabel:`TERMINATE`.
77+
- The data verification process was cancelled by clicking :guilabel:`Terminate`.
7878
* - CANCELLING
79-
- The data validation process is being canceled.
79+
- The data verification process is being canceled.
8080
* - FAILED
81-
- The source and destination databases do not match. The corresponding errors are listed on the :guilabel:`Issues` pane.
81+
- The source and destination databases do not match. The corresponding errors are listed on the :guilabel:`Job Update Log` pane.
8282
* - VERIFIED
83-
- Data validation is successful, the source and destination databases match.
83+
- Data verification is successful, the source and destination databases match.
8484
* - VERIFYING
85-
- The data validation is in progress. Backend SQL and MongoDB query API commands are running to validate the migration.
85+
- The data verification is in progress. Backend SQL and MongoDB query API commands are running to validate the migration.
8686

8787
Successful Data Verification
8888
----------------------------
8989

90-
When a sync job is successful the status updates to :guilabel:`VERIFIED`
91-
and a double checkmark is displayed in the :guilabel:`History` pane.
90+
When a sync job is successful the status updates to :guilabel:`Verified`
91+
and a double checkmark is displayed in the :guilabel:`History` pane:
9292

9393
.. image:: /img/jobs/data-verification/data-verification-double-checkmark.png
9494
:alt: History pane double checkmark
@@ -99,14 +99,15 @@ Data Verification Issues
9999

100100
If the data verification process detects any differences between the
101101
source database and destination collections, the errors are
102-
reported in the Data Verification :guilabel:`Issues` pane.
102+
reported in the Data Verification :guilabel:`Job Update Log` pane.
103103

104104
In this example, the data verification process is detecting that the
105105
number of documents in the target collection do not match the source
106106
database.
107107

108-
#. The Verification status is :guilabel:`FAILED`.
109-
#. The specific issue and error detail is displayed in the :guilabel:`Issues` pane.
108+
#. The Verification status is :guilabel:`Aborted`.
109+
#. The specific issue and error detail is displayed in the
110+
:guilabel:`Job Update Log` pane.
110111

111112
.. image:: /img/jobs/data-verification/data-verification-view-issues.png
112113
:alt: Data verification issues

0 commit comments

Comments
 (0)