Getting Started With Analytics 2.0

You must upgrade the existing Analytics Cloud Connector CLI to the latest version before your next scheduled run to process the expanded historical volume of user activity data.

Key Benefits & Features of the Upgrade

• Partitioned Loading: First-time loads now import one partition (one day) at a time instead of executing a single large scan, preventing Out-Of-Memory (OOM) errors and timeouts on tables with years of history.

• Destination-Aware Recovery: If the processing_log table is cleared, a partition is lost, or a run fails partway, the Analytics Cloud Connector checks your destination database first and only loads missing partitions, making the backfill procedure safe and idempotent.

• Safer Force-Overwrite: Forcing an overwrite on one table no longer clears the entire global processing_log; other tables maintain their incremental cadence.
  Note: Force-overwrite (force_overwrite) is bypassed for the user_activity table and other APPEND tables.

• Consistent UTC Handling: The mutating current UTC day is excluded from every append load to ensure re-runs within the same day do not load incomplete datasets.

• New Configuration Key: A new source_config.exclude_tables configuration key to standardize table exclusions across all incremental datasets. The legacy process_user_activity key is still supported for backward compatibility.

• Prerequisites:

  • Download the latest version of the Analytics Cloud Connector CLI. See Download the Analytics Cloud Connector CLI.

1. Stop all active scheduled tasks, cron jobs, or wrapper scripts invoking your legacy CLI version.

2. Create a backup copy of your existing installation directory. Safely store your config.yaml and .share profile files in a secure temporary folder.

3. Unzip the new CLI file over your existing installation directory, or place it into a new folder and update your scheduler paths.

4. Restore your backed-up config.yaml and .share profile files into the newly updated directory.

5. Verify the update by running the following command in your terminal:
   cat VERSION # should read 2.0.2.xxxx

   The output must display 2.0.2.xxxx.

6. (Optional, Recommended) Complete a dry run against a small table first to confirm the new CLI connects and writes as expected.