From commits-return-17449-archive-asf-public=cust-asf.ponee.io@airflow.incubator.apache.org Mon Aug 6 12:34:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id B8D60180627 for ; Mon, 6 Aug 2018 12:34:03 +0200 (CEST) Received: (qmail 68660 invoked by uid 500); 6 Aug 2018 10:34:02 -0000 Mailing-List: contact commits-help@airflow.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airflow.incubator.apache.org Delivered-To: mailing list commits@airflow.incubator.apache.org Received: (qmail 68651 invoked by uid 99); 6 Aug 2018 10:34:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Aug 2018 10:34:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 6FE9D1811B8 for ; Mon, 6 Aug 2018 10:34:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id TgbqbFzojEVA for ; Mon, 6 Aug 2018 10:34:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 2BEEF5F3D0 for ; Mon, 6 Aug 2018 10:34:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 997EAE00CB for ; Mon, 6 Aug 2018 10:34:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 319D423F9B for ; Mon, 6 Aug 2018 10:34:00 +0000 (UTC) Date: Mon, 6 Aug 2018 10:34:00 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: commits@airflow.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AIRFLOW-2860) DruidHook: time variable is not updated correctly when checking for timeout MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AIRFLOW-2860?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16= 570017#comment-16570017 ]=20 ASF GitHub Bot commented on AIRFLOW-2860: ----------------------------------------- awelsh93 opened a new pull request #3707: [AIRFLOW-2860] DruidHook: time va= riable is not updated correctly when=E2=80=A6 URL: https://github.com/apache/incubator-airflow/pull/3707 =20 =20 =E2=80=A6 checking for timeout =20 Make sure you have checked _all_ steps below. =20 ### Jira =20 - [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 y= our commit with \[AIRFLOW-XXX\], code changes always need a Jira issue. =20 ### Description =20 - [x] Here are some details about my PR, including screenshots of any UI= changes: =20 ### Tests =20 - [x] My PR adds the following unit tests __OR__ does not need testing f= or this extremely good reason: I ran `nosetests /tests/hooks/test_druid_hook.py` =20 ### Commits =20 - [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 me= ssage](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 refer= ence) 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" =20 ### Documentation =20 - [ ] In case of new functionality, my PR adds documentation that descri= bes how to use it. - When adding new operators/hooks/sensors, the autoclass documentation= generation needs to be added. =20 ### Code Quality =20 - [x] Passes `git diff upstream/master -u -- "*.py" | flake8 --diff` =20 ---------------------------------------------------------------- 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. =20 For queries about this service, please contact Infrastructure at: users@infra.apache.org > DruidHook: time variable is not updated correctly when checking for timeo= ut=20 > -------------------------------------------------------------------------= --- > > Key: AIRFLOW-2860 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2860 > Project: Apache Airflow > Issue Type: Bug > Components: hooks > Reporter: Adam Welsh > Priority: Trivial > > The variable that=C2=A0is used in the condition to check if the Druid ing= estion task has exceeded the max_ingestion_time is not updated correctly. I= t gets incremented by one (which is the default value for timeout) but shou= ld be incremented by timeout. -- This message was sent by Atlassian JIRA (v7.6.3#76005)