StringPartitionKeyComponent limits the key length to 100 chars

[chetanmeh]

StringPartitionKeyComponent truncates the key to 100 chars.

azure-cosmosdb-java/sdk/src/main/java/com/microsoft/azure/cosmosdb/internal/routing/StringPartitionKeyComponent.java

Line 34 in 17937b1

public static final int MaxStringComponentLength = 100;

Per docs the maximum length for id field is 255 chars. However I was not able to find any documented limit for partition key. Closest reference found here mentions

The length of RowKey is 255 bytes and the length of PartitionKey is 1 KB.

Can this limit in StringPartitionKeyComponent be set to 255 at least? Due to current truncation I get error PartitionKey extracted from document doesn't match the one specified in the header as the id field in document being added has length say 120 chars while one passed in header is truncated to 100.

[moderakh]

@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.

[chetanmeh]

@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

[moderakh]

@chetanmeh no. that won't work.

[chetanmeh]

Thanks for confirming. Would then look for next release

[moderakh]

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

[chetanmeh]

@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

[chetanmeh]

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 !!