Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[connector-builder] add support for specifying timezone for Start Datetime and End Datetime in Incremental Sync #38081

Open
swrookie opened this issue May 9, 2024 · 1 comment

Comments

@swrookie
Copy link

swrookie commented May 9, 2024

Topic

connector-builder, timezone

Relevant information

Tell us about the problem you're trying to solve

Currently, Start Datetime and End Datetime for Incremental Sync in connector builder only supports UTC Timezone.

When trying to input datetime with timezone of specific country, the value being sent to api request automatically converts to current datetime in UTC due to MinMaxDatetime validation.

Describe the solution you’d like

In connector builder incremental sync configuration, users should be able to select timezone in the dropdown for each Start and End datetime, just like timezone dropdown when choosing cron as the schedule type in configuring connection.

Datetime inputs then would be converted to UTC timezone for MinMaxDatetime validation internally and after validation is successful, datetime would be used as it was entered for api request.

Are you willing to submit a PR?

Yes.

@octavia-squidington-iii
Copy link
Collaborator

At Airbyte, we seek to be clear about the project priorities and roadmap. This issue has not had any activity for 180 days, suggesting that it's not as critical as others. It's possible it has already been fixed. It is being marked as stale and will be closed in 20 days if there is no activity. To keep it open, please comment to let us know why it is important to you and if it is still reproducible on recent versions of Airbyte.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants