Merge pull request #79510 from kanshiG/patch-54

2019-June updates

Author: PRMerger13

articles/cosmos-db/cassandra-support.md

@@ -69,6 +69,8 @@ Azure Cosmos DB Cassandra API supports the following CQL data types:
 Azure Cosmos DB Cassandra API supports the following CQL functions:
 
 * Token  
+* Aggregate functions
+  * min, max, avg, count
 * Blob conversion functions 
   * typeAsBlob(value)  
   * blobAsType(value)
@@ -83,7 +85,8 @@ Azure Cosmos DB Cassandra API supports the following CQL functions:
   * toDate(timestamp)  
   * toUnixTimestamp(timestamp)  
   * toTimestamp(date)  
-  * toUnixTimestamp(date)  
+  * toUnixTimestamp(date) 
+  
 
 
 ## Cassandra Query Language limits
@@ -149,11 +152,11 @@ foreach (string key in insertResult.Info.IncomingPayload)
 
 ## Consistency mapping 
 
-Azure Cosmos DB Cassandra API provides choice of consistency for read operations. All write operations, irrespective of the account consistency are always written with write performance SLAs.
+Azure Cosmos DB Cassandra API provides choice of consistency for read operations.  The consistency mapping is detailed [here[(https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels-across-apis#cassandra-mapping).
 
 ## Permission and role management
 
-Azure Cosmos DB supports role-based access control (RBAC) and read-write and read-only passwords/keys that can be obtained through the [Azure portal](https://portal.azure.com). Azure Cosmos DB does not yet support users and roles for data plane activities. 
+Azure Cosmos DB supports role-based access control (RBAC) for provisioning, rotating keys, viewing metrics and read-write and read-only passwords/keys that can be obtained through the [Azure portal](https://portal.azure.com). Azure Cosmos DB does not yet support users and roles for CRUD activities. 
 
 ## Planned support 
 * Region name in create keyspace command is ignored at present- Distribution of data is implemented in underlying Cosmos DB platform and exposed via portal or powershell for the account.