[
https://issues.apache.org/jira/browse/AIRFLOW-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Croteau updated AIRFLOW-5104:
----------------------------------
Description:
The docstring for
`airflow.contrib.operators.gcp_transfer_operator.S3ToGoogleCloudStorageTransferOperator`
says of the `schedule` parameter:
{noformat}
Optional transfer service schedule;
If not set, run transfer job once as soon as the operator runs{noformat}
This isn't the way the operator is actually implemented though. If `schedule`
is unset, the operator provides to `schedule` parameter in the REST API call,
which causes the API to return this error:
{noformat}
HttpError 400 when requesting
https://storagetransfer.googleapis.com/v1/transferJobs?alt=json returned
"Schedule was not specified."{noformat}
It's not well-described in [the official
documentation|https://cloud.google.com/storage-transfer/docs/reference/rest/v1/transferJobs],
but it seems the REST API actually does require a `schedule` parameter to be
provided, and fails if it isn't.
was:
The docstring for
`airflow.contrib.operators.gcp_transfer_operator.S3ToGoogleCloudStorageTransferOperator`
says of the `schedule` parameter:
{{Optional transfer service schedule;
If not set, run transfer job once as soon as the operator runs}}
This isn't the way the operator is actually implemented though. If `schedule`
is unset, the operator provides to `schedule` parameter in the REST API call,
which causes the API to return this error:
{{HttpError 400 when requesting
[https://storagetransfer.googleapis.com/v1/transferJobs?alt=json] returned
"Schedule was not specified."}}
It's not well-described in [the official
documentation|https://cloud.google.com/storage-transfer/docs/reference/rest/v1/transferJobs],
but it seems the REST API actually does require a `schedule` parameter to be
provided, and fails if it isn't.
> "Schedule was not specified." error from GCS API when using
> gcp_transfer_operator.S3ToGoogleCloudStorageTransferOperator without
> specifying a schedule
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AIRFLOW-5104
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5104
> Project: Apache Airflow
> Issue Type: Bug
> Components: contrib, gcp
> Affects Versions: 1.10.3
> Reporter: Joel Croteau
> Priority: Major
>
> The docstring for
> `airflow.contrib.operators.gcp_transfer_operator.S3ToGoogleCloudStorageTransferOperator`
> says of the `schedule` parameter:
> {noformat}
> Optional transfer service schedule;
> If not set, run transfer job once as soon as the operator runs{noformat}
> This isn't the way the operator is actually implemented though. If `schedule`
> is unset, the operator provides to `schedule` parameter in the REST API call,
> which causes the API to return this error:
> {noformat}
> HttpError 400 when requesting
> https://storagetransfer.googleapis.com/v1/transferJobs?alt=json returned
> "Schedule was not specified."{noformat}
> It's not well-described in [the official
> documentation|https://cloud.google.com/storage-transfer/docs/reference/rest/v1/transferJobs],
> but it seems the REST API actually does require a `schedule` parameter to be
> provided, and fails if it isn't.
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)