Update: just had a meeting with the Microsoft engineers.
Looks like the root cause is that Google storage that emulates Amazon S3 API returns file size = -1, which is interpreted as infinite by Copy activity.
In the regular mode, when Copy activity using multiple threads, it tries to split -1 and gets 0 for each thread.
However, if I use (as MS engineers suggested) undocumented sequential mode
"storeSettings": {
"type": "GoogleCloudStorageReadSettings",
"multipartSourceType": "Sequential",
"recursive": true,
"enablePartitionDiscovery": false
},
"formatSettings": {
"type": "DelimitedTextReadSettings"
}
It actually copies file, but infinitely and never finishes. I've stopped it when it inserted 510k rows from a tiny 17-rows file.