From issues-return-34089-apmail-nifi-issues-archive=nifi.apache.org@nifi.apache.org Wed Aug 9 14:47:03 2017 Return-Path: X-Original-To: apmail-nifi-issues-archive@minotaur.apache.org Delivered-To: apmail-nifi-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BB0B71AD77 for ; Wed, 9 Aug 2017 14:47:03 +0000 (UTC) Received: (qmail 40736 invoked by uid 500); 9 Aug 2017 14:47:03 -0000 Delivered-To: apmail-nifi-issues-archive@nifi.apache.org Received: (qmail 40702 invoked by uid 500); 9 Aug 2017 14:47:03 -0000 Mailing-List: contact issues-help@nifi.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@nifi.apache.org Delivered-To: mailing list issues@nifi.apache.org Received: (qmail 40674 invoked by uid 99); 9 Aug 2017 14:47:02 -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; Wed, 09 Aug 2017 14:47:02 +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 43726C001A for ; Wed, 9 Aug 2017 14:47:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id kmQD1c6FRyVd for ; Wed, 9 Aug 2017 14:47: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 5D11E5FB57 for ; Wed, 9 Aug 2017 14:47: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 E5BBFE0E26 for ; Wed, 9 Aug 2017 14:47: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 92F6024161 for ; Wed, 9 Aug 2017 14:47:00 +0000 (UTC) Date: Wed, 9 Aug 2017 14:47:00 +0000 (UTC) From: "Matt Burgess (JIRA)" To: issues@nifi.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (NIFI-3335) GenerateTableFetch should allow you to specify an initial Max Value MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/NIFI-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated NIFI-3335: ------------------------------- Issue Type: Improvement (was: New Feature) > GenerateTableFetch should allow you to specify an initial Max Value > ------------------------------------------------------------------- > > Key: NIFI-3335 > URL: https://issues.apache.org/jira/browse/NIFI-3335 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions > Reporter: Matt Burgess > Assignee: Matt Burgess > Fix For: 1.4.0 > > > NIFI-2583 added the ability (via dynamic properties) to specify initial Max Values for columns, to enable the user to "pick up where they left off" if something happened with a flow, a NiFi instance, etc. where the state was stored but the processing did not complete successfully. > This feature would also be helpful in GenerateTableFetch, which also supports max-value columns. > Since NIFI-2881 adds incoming flow file support, it's more useful if Initial max values can be specified via flow file attributes. Because if a table name is dynamically passed via flow file attribute and Expression Language, user won't be able to configure dynamic processor attribute in advance for each possible table. > Add dynamic properties ('initial.maxvalue.' same as QueryDatabaseTable) to specify initial max values statically, and also use incoming flow file attributes named 'initial.maxvalue.' if any. -- This message was sent by Atlassian JIRA (v6.4.14#64029)