April2016 - LiquidAnalytics/ld-api-examples GitHub Wiki

#Major Changes and New Features Summary

##Cloud: Schema Inheritance (experimental feature) Added initial support for Schema Inheritance. Allows you to create a schema with a parentType specified. Internally the schema inherits all the fields specified on all of it's parent schemas. Makes use of [PostgreSql table inheritance] (http://www.postgresql.org/docs/9.3/static/ddl-inherit.html) for ease of use in querying inherited types

##Cloud: Expanded Task API Added processType, description and itemId to the Task class, allowing callers of the Task API (/ls/api/tasks/updateTaskProgress) to more accurately update a Task with values that the server does not need to know about before hand.

##Cloud: SQL Rejects

Items that could not be written into SQL are recorded into S3 for analysis by Liquid. This data is retained for 40 days.

##Improved Threading Model for Optimized Concurrency

This release improves performance of background processes such as permissions, interfaces, and mobile sync. Performance of some internal system process are improved by as much as 30%.

#Change Log

  1. (On-premise only) Improved expiration process by slicing date queries into smaller time ranges, avoiding cassandra timeout issues in the case of wide rows for a large item type.
  2. Fixed issue where devices on a tagged package version would incorrectly receive deletes of configuration items done on the "tip" version of the items.
  3. Improved performance issues on Mission Control startup when entering a community with a large number of User items.
  4. Fixed issue where if a userId in a community has a different case than the systemUser userId in the root community, and the user has loginAs access, would cause an incorrect item manifest to be generated for the user.
  5. Fixed an issue with batch API to accommodate for S3 eventual consistency.
  6. More informative messages in Mission Control during startup.
  7. Mission Control Community User Management tab will no longer allow customers to setup permission for all users. The only options are Active or Selected.
  8. The platform now collects detailed HTTP requests to assist with debugging.

#Risks and Known Issues

There are no known issues or risks.

#Maintenance Window

This server deployment does not require a maintenance window.

#Special Deployment Notes

There are no special notes for this release.

#Release Schedule

Date Environment
4/6/2016 ProdB
4/7/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** ⚠️