HistoricalClient.BatchSubmitJobAsync(...) accepts a splitDuration argument, but the value never reaches the API. The submitted job is always created with the server-side default ("split_duration": "year"), regardless of what's passed.
There's no exception and no warning, the job submits and completes successfully. The only way to notice is to read the finished job's metadata.json or count the delivered files.
Tested in 5.3.4 and 5.3.5
HistoricalClient.BatchSubmitJobAsync(...) accepts a splitDuration argument, but the value never reaches the API. The submitted job is always created with the server-side default ("split_duration": "year"), regardless of what's passed.
There's no exception and no warning, the job submits and completes successfully. The only way to notice is to read the finished job's metadata.json or count the delivered files.
Tested in 5.3.4 and 5.3.5