Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 19E25200B5C for ; Thu, 11 Aug 2016 13:06:18 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 187AC160A94; Thu, 11 Aug 2016 11:06:18 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 5F631160A85 for ; Thu, 11 Aug 2016 13:06:17 +0200 (CEST) Received: (qmail 77436 invoked by uid 500); 11 Aug 2016 11:06:16 -0000 Mailing-List: contact dev-help@apex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@apex.apache.org Delivered-To: mailing list dev@apex.apache.org Received: (qmail 77425 invoked by uid 99); 11 Aug 2016 11:06:16 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Aug 2016 11:06:16 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id EC8A9CA5B7 for ; Thu, 11 Aug 2016 11:06:15 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -4.539 X-Spam-Level: X-Spam-Status: No, score=-4.539 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.519] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id f2T5o2kwvUAM for ; Thu, 11 Aug 2016 11:06:13 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id 3923F5FE5A for ; Thu, 11 Aug 2016 11:06:13 +0000 (UTC) Received: (qmail 77210 invoked by uid 99); 11 Aug 2016 11:06:12 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Aug 2016 11:06:12 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 4F183E03C0; Thu, 11 Aug 2016 11:06:12 +0000 (UTC) From: DT-Priyanka To: dev@apex.incubator.apache.org Reply-To: dev@apex.incubator.apache.org References: In-Reply-To: Subject: [GitHub] apex-malhar pull request #358: APEXMALHAR-2172: Updates to JDBC Poll Input O... Content-Type: text/plain Message-Id: <20160811110612.4F183E03C0@git1-us-west.apache.org> Date: Thu, 11 Aug 2016 11:06:12 +0000 (UTC) archived-at: Thu, 11 Aug 2016 11:06:18 -0000 GitHub user DT-Priyanka reopened a pull request: https://github.com/apache/apex-malhar/pull/358 APEXMALHAR-2172: Updates to JDBC Poll Input Operator Changes include: 1. Using jooq query to construct sql queries 2. Update logic to query based on row numbers instead of primary key column values 3. Small fixes 4. Code refactoring to make it more readable 5. Update operator to emit pojo class constructed from table input fields 6. Update to test cases, to abstract out generic test code and add more tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/DT-Priyanka/incubator-apex-malhar APEXMALHAR-2172-jdbc-poller-input Alternatively you can review and apply these changes as the patch at: https://github.com/apache/apex-malhar/pull/358.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 #358 ---- commit 26fa9d781e032fd61fbb2972a99874e77e0c509c Author: Priyanka Gugale Date: 2016-07-19T06:40:08Z APEXMALHAR-2172: Updates to JDBC Poll Input Operator ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---