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 B50D3200D0A for ; Wed, 20 Sep 2017 08:10:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B35F41609E0; Wed, 20 Sep 2017 06:10:08 +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 03DC91609DD for ; Wed, 20 Sep 2017 08:10:07 +0200 (CEST) Received: (qmail 62997 invoked by uid 500); 20 Sep 2017 06:10:07 -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 62988 invoked by uid 99); 20 Sep 2017 06:10:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Sep 2017 06:10:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 772681A1881 for ; Wed, 20 Sep 2017 06:10:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-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 (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id abQhp7Tgou8f for ; Wed, 20 Sep 2017 06:10:04 +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 0E93B61254 for ; Wed, 20 Sep 2017 06:10:04 +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 4C8ECE0EFB for ; Wed, 20 Sep 2017 06:10:03 +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 9A00924527 for ; Wed, 20 Sep 2017 06:10:00 +0000 (UTC) Date: Wed, 20 Sep 2017 06:10:00 +0000 (UTC) From: "Deon Huang (JIRA)" To: issues@nifi.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (NIFI-4395) GenerateTableFetch can't fetch column type by state after instance reboot MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 20 Sep 2017 06:10:08 -0000 [ https://issues.apache.org/jira/browse/NIFI-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16172784#comment-16172784 ] Deon Huang commented on NIFI-4395: ---------------------------------- Thanks for the confirmation. I'll self assign and start to work on this. > GenerateTableFetch can't fetch column type by state after instance reboot > ------------------------------------------------------------------------- > > Key: NIFI-4395 > URL: https://issues.apache.org/jira/browse/NIFI-4395 > Project: Apache NiFi > Issue Type: Bug > Affects Versions: 1.3.0 > Reporter: Deon Huang > Assignee: Deon Huang > Fix For: 1.4.0 > > Attachments: GenerateTableFetch_Exception.png > > > The problem can easily be reproduce. > Once GenerateTableFetch store state and encounter NiFi instance reboot. > (Dynamic naming table by expression language) > The exception will occur. > The error in source code is list below. > --- > if (type == null) { > // This shouldn't happen as we are populating columnTypeMap when the processor is scheduled or when the first maximum is observed > throw new IllegalArgumentException("No column type found for: " + colName); > } > --- > When this situation happened. The FlowFile will also be grab and can't release or observed. > Processor can't existing grab column type from columnTypeMap through instance reboot. > Hence will inevidible get this exception, rollback FlowFile and never success. > QueryDatabaseTable processor will not encounter this exception due to it setup(context) every time, > While GenerateTableFetch will not pass the condition and thus try to fetch column type from 0 length columnTypeMap. > --- > if (!isDynamicTableName && !isDynamicMaxValues) { > super.setup(context); > } > --- > I can take the issue if it is recognize as bug. -- This message was sent by Atlassian JIRA (v6.4.14#64029)