Skip to content

Commit

Permalink
Fix typos
Browse files Browse the repository at this point in the history
  • Loading branch information
Mario Galic committed Sep 2, 2019
1 parent 82ade92 commit 6fa40ce
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions handlers/zuora-datalake-export/README.md
Expand Up @@ -47,7 +47,7 @@ object AccountQuery extends Query(
## How does it get triggered?

AWS Cloudwatch Event Rule triggers the export lambda once per day. Each execution exports changes
since last time export run. Rule passes `{"exportFromDate": "afterLastIncrement"}` to lambda.
since last time export ran. Rule passes `{"exportFromDate": "afterLastIncrement"}` to lambda.

## How do we know when it fails?

Expand All @@ -58,8 +58,8 @@ since last time export run. Rule passes `{"exportFromDate": "afterLastIncrement"

Export is **NOT** idempotent. Do not blindly re-run the export. Lake must ingest the latest increment before
lambda can be executed again with `{"exportFromDate": "afterLastIncrement"}`. If the lambda is executed before
lake ingest the latest increment, then the increment is lost. (If this happens use `incrementalTime` method \
described bellow to retrieve the lost increment.)
lake ingests the latest increment, then the increment is lost. (If this happens use `incrementalTime` method \
described below to retrieve the lost increment.)

However it seems to be safe to re-run the export with `incrementalTime` provided. This will get the changes since
`incrementalTime` but it will not modify the session so when lambda runs again with `{"exportFromDate": "afterLastIncrement"}`
Expand Down

0 comments on commit 6fa40ce

Please sign in to comment.