October2016 - LiquidAnalytics/ld-api-examples GitHub Wiki

#Major Changes and New Features Summary

Cross-region replication

This release focuses on the ability to replicate data between Liquid Platform multicommunity environments. This is an experimental feature only offered to selected communities.

#Change Log

  1. More flexible configuration object replication config; finer control over what gets replicated between on-premise and cloud environments.
  2. Upgraded liquid-commons to resolve some of the SQS processing issues.
  3. Added API to facilitate recon between replication regions.
  4. Old query API respects userId passed into it.
  5. Entitlement queries can have a path override to explicitly specify which path they are overriding.
  6. Authorization info rest API must pass client_id along.
  7. Using MC to replicate items to cloud now reflects the actual progress.
  8. Setting max results on search requires for replication from main UI.
  9. Mission Control startup speed improvements.
  10. Publishing replication lag to CloudWatch.
  11. Added a convenient dialog to replicate all items.
  12. Use upsert API for merge instead of calling merge directly.
  13. Can now specify custom create index statements on the schema.
  14. Utility column should be created before others.
  15. Replicating package deployment data.
  16. Replicating package version data now.
  17. Temporary log message to see where the batch job is being repeated.
  18. Added a log message to see what it is trying to do .
  19. Support for replication of transactions.
  20. Support for replication of schemas, relationships and other configuration.

#Risks and Known Issues

No known risks or issues.

#Maintenance Window

This server deployment does not require a maintenance window.

#Special Deployment Notes

This release requires that the WebSocket relay is updated as well.

#Release Schedule

Date Environment
10/5/2016 ProdB
10/6/2016 Prod

#ProdB Validation

Testers assigned to each customer use the current production client app to verify there are no new issues introduced in ProdB:

  1. In settings change the server URL to https://ldcloud-b.liquidanalytics.com
  2. Perform exploratory testing
  3. Report only new issues found, distinguishing between what may be caused by the server from what is a client-side issue
    • Sync
    • Transactions
    • Registrations
    • Authentication
    • On-demand functions
    • Queries

#Prod Validation

Testers assigned to each customer use the current production client app to verify there are no new issues introduced in Prod:

  1. In settings make sure the server URL is https://ldcloud.liquidanalytics.com
  2. Perform exploratory testing
  3. Report only new issues found, distinguishing between what may be caused by the server from what is a client-side issue
    • Sync
    • Transactions
    • Registrations
    • Authentication
    • On-demand functions
    • Queries
⚠️ **GitHub.com Fallback** ⚠️