Script logs lose information (casing and new lines)

[kentcb]

Script logs lose information (casing and new lines)

[kirankumarkolli]

EnableScriptLogging gets logs in a header named 'x-ms-documentdb-script-log-results', which can be access through CosmosItemResponse.Headers.

@kentcb are you not seeing 'x-ms-documentdb-script-log-results' header in the response?

[kentcb]

Ah, yes I do. Sorry, I missed that somehow. That said, it comes through as encoded (e.g. a space comes through as %20) which is probably fine and expected given that it's a header. However, being in a header also means that it comes through as lower case, which means that important information may be lost (e.g. generated IDs will lose casing).

[kentcb]

It also loses line breaks between distinct console.log calls, which is a bit annoying.

[kirankumarkolli]

@kentcb thanks for the feedback.

Some parts of the feedback (encoding etc..) can be handled by client abstraction but it doesn't cover the lower-casing part, this needs to be addressed by service.

@kentcb can you please share this feedback over askcosmosdb[AtT]microsoft.com?

[kirankumarkolli]

@mkolt thoughts on lower case issues in script logs?

[mkolt]

+@balaperu

[christopheranderson]

@mkolt - we need to triage this still. Since this is a backend limitation, my thought is that we should move this off the SDK repo. Did you make any progress on this?

[mkolt]

The line breaks etc should be fixed a while ago. We URL-encode the value.