[
https://issues.apache.org/jira/browse/AIRFLOW-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16604445#comment-16604445
]
ASF GitHub Bot commented on AIRFLOW-3010:
-----------------------------------------
rlkelly opened a new pull request #3850: [AIRFLOW-3010] added support for date
format to postgres_to_gcs_operator
URL: https://github.com/apache/incubator-airflow/pull/3850
Make sure you have checked _all_ steps below.
### Jira
- [X ] My PR addresses the following [Airflow
Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues and references
them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
- https://issues.apache.org/jira/browse/AIRFLOW-XXX
- In case you are fixing a typo in the documentation you can prepend your
commit with \[AIRFLOW-XXX\], code changes always need a Jira issue.
### Description
- [ X ] Here are some details about my PR, including screenshots of any UI
changes:
I just changed it so the Date datatype would be acknowledged in write and
read.
### Tests
- [ X ] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
Currently the schema functionality is largely untested and this would be a
larger undertaking if we wanted to create better testing for serialization.
### Commits
- [ X ] My commits all reference Jira issues in their subject lines, and I
have squashed multiple commits if they address the same issue. In addition, my
commits follow the guidelines from "[How to write a good git commit
message](http://chris.beams.io/posts/git-commit/)":
1. Subject is separated from body by a blank line
1. Subject is limited to 50 characters (not including Jira issue reference)
1. Subject does not end with a period
1. Subject uses the imperative mood ("add", not "adding")
1. Body wraps at 72 characters
1. Body explains "what" and "why", not "how"
### Documentation
- [ X ] In case of new functionality, my PR adds documentation that
describes how to use it.
- When adding new operators/hooks/sensors, the autoclass documentation
generation needs to be added.
### Code Quality
- [ ] Passes `git diff upstream/master -u -- "*.py" | flake8 --diff`
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Postgres to BigQuery Operator does not handle the Date datatype
> ---------------------------------------------------------------
>
> Key: AIRFLOW-3010
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3010
> Project: Apache Airflow
> Issue Type: Bug
> Reporter: robert kelly
> Priority: Trivial
>
> Right now, all time based datatypes are treated as Datetime, but this isn't
> optimal if you're dumping your database to csv and uploading to bigquery,
> since the csv dump will be in the date format, but the database will expect
> the datetime format.
>
> By making a few small changes to the Operator, it will read this format
> properly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
