airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-3881) Correct hive_hook to_csv row number
Date Wed, 13 Feb 2019 03:06:00 GMT

    [ https://issues.apache.org/jira/browse/AIRFLOW-3881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16766719#comment-16766719
] 

ASF GitHub Bot commented on AIRFLOW-3881:
-----------------------------------------

zhongjiajie commented on pull request #4699: [AIRFLOW-3881] Correct to_csv row number
URL: https://github.com/apache/airflow/pull/4699
 
 
   Correct row number each patch write log
   
   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-3881
   
   ### Description
   
   - [x] Here are some details about my PR, including screenshots of any UI changes:
   
   Correct hive_hooks to_csv function row number while logging.
   
   ### Tests
   
   - [x] My PR adds the following unit tests __OR__ does not need testing for this extremely
good reason:
   
   minor change, existing test could test it.
   
   ### 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.
     - All the public functions and the classes in the PR contain docstrings that explain
what it does
   
   ### Code Quality
   
   - [x] Passes `flake8`
   
 
----------------------------------------------------------------
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:
users@infra.apache.org


> Correct hive_hook to_csv row number
> -----------------------------------
>
>                 Key: AIRFLOW-3881
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3881
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: hive_hooks
>    Affects Versions: 1.10.2
>            Reporter: zhongjiajie
>            Assignee: zhongjiajie
>            Priority: Minor
>              Labels: easyfix
>             Fix For: 1.10.3
>
>
> hive_hooks to_csv function had wrong row number each path so far, this Jira ticket is correct
row number



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message