[
https://issues.apache.org/jira/browse/BEAM-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15962791#comment-15962791
]
ASF GitHub Bot commented on BEAM-1923:
--------------------------------------
GitHub user ubunatic opened a pull request:
https://github.com/apache/beam/pull/2480
[BEAM-1923] Improve python log messages for temporary BigQuery tables
- fixed a typo
- added project and dataset names to log message
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ubunatic/beam temp-table-log-message
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/2480.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2480
----
commit 79537846431fb679cde85755e4bbdd868cff3eee
Author: Uwe Jugel <[email protected]>
Date: 2017-04-10T12:24:44Z
better log message for bigquery temp tables
commit 652663887c3448046ede70d1f430940e1cfdd9ce
Author: Uwe Jugel <[email protected]>
Date: 2017-04-10T12:30:32Z
fixed spelling, improved wording
----
> Improve python log messages for temporary BigQuery tables
> ---------------------------------------------------------
>
> Key: BEAM-1923
> URL: https://issues.apache.org/jira/browse/BEAM-1923
> Project: Beam
> Issue Type: Improvement
> Components: sdk-py
> Reporter: Uwe Jugel
> Assignee: Ahmet Altay
> Priority: Trivial
>
> When reading from BigQuery using the Python SDK, the SDK prints a WARNING:
> "Dataset does not exist so we will create it."
> I like to improve that:
> - showing that it is a temporary data set
> - showing the dataset name
> This is useful if the pipeline fails, since the temporary dataset will then
> be left undeleted in your project.
> I created a branch for the fix here:
> https://github.com/apache/beam/compare/master...ubunatic:temp-table-log-message
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
