StringPartitionKeyComponent limits the key length to 100 chars about azure-cosmosdb-java HOT 7 CLOSED

@chetanmeh thanks for reporting this. We have a fix for this, which should get released along some other improvements in a week or so. We are code complete, just final review, testing.

from azure-cosmosdb-java.

@moderakh Good to know that its under fix. Just to unblock myself for now would it be fine to just bump the limit locally assuming the limit for PartitionKey is >= 255 or there is more to this issue

from azure-cosmosdb-java.

@chetanmeh no. that won't work.

from azure-cosmosdb-java.

Thanks for confirming. Would then look for next release

from azure-cosmosdb-java.

addressed in 2.1.0.

added unit test:
https://github.com/Azure/azure-cosmosdb-java/blob/master/sdk/src/test/java/com/microsoft/azure/cosmosdb/rx/DocumentCrudTest.java#L99-L115

from azure-cosmosdb-java.

@moderakh Should the test create key with length 255 as thats the max limit. So far keys upto 100 work as expected as that was the earlier limit in StringPartitionKeyComponent

from azure-cosmosdb-java.

Ignore the previous comment. Now see that test case was building with 2-3 chars per iteration. Also looks like 255 limit is only for id. For partition key the limit looks much higher (probably 1 KB).

So it works fine now !!

from azure-cosmosdb-java.