Sidecar documents not inheriting parent's permissions

[eaolson]

I'm using Flux to take a corpus of already-ingested documents and split them into sidecar documents. So I'm doing a copy operation where the input and output database is the same and I'm specifying --splitter options for the job. My source document has five permissions, but all the split chunks have four. I'm pretty sure the four are just the default permissions for the user.

The documentation says "Each sidecar document defaults to the same permissions as its source document and no collections assigned to it."

[rjrudin]

Thanks @eaolson for the report. This behavior looks specific to copy, where no permissions are specified by the user but rather the permissions for the written document are inherited from the source document.

The creation of chunks currently uses permissions specified via either --permissions (or in the case of a copy, --output-permissions) or --splitter-sidecar-permissions.

I am thinking that for now, the documentation needs a clarification to make it clear that the chunk documents don't really inherit from the source document; rather, they will receive the permissions specified by --permissions or --output-permissions and those can be overridden via --splitter-sidecar-permissions. Modifying the copy operation to add the source document as an additional source of permissions needs a bit more thinking.

[SoumenduGhosh10]

We will be fixing this as a part of Flux 2.2.0 release. And we have filed https://progresssoftware.atlassian.net/browse/MLE-30003 for the same