This topic describes how to run an Incremental update operation.
This procedure assumes that the data set has been configured for Incremental updates (that is, a record identifier has been configured).
Note that the example in the procedure does not use the --table and --database flags, which means that the command will run against the original Hive table from which the data set was created.
To run an Incremental update on a data set:
... jobId: b6a9fab0-7ca0-4d35-9950-a066520dd948 data_processing_CLI finished with state SUCCESS
EDP: IncrementalUpdateConfig{collectionId=MdexCollectionIdentifier{ databaseName=default_edp_e6bfc4c3-24cc-4141-96fe-53cb808b788d, collectionName=default_edp_e6bfc4c3-24cc-4141-96fe-53cb808b788d}, jobId=b6a9fab0-7ca0-4d35-9950-a066520dd948, whereClause=claim_amount > 1000}
You can also check the Dgraph HDFS Agent log for the status of the Dgraph ingest operation.
Nothing to be done here since no records are returned for the filter predicate.
Note that future Incremental updates on this data set will continue to use the same Data Set Logical Name. You will also use this name if you set up a Incremental update cron job for this data set.