From issues-return-92125-archive-asf-public=cust-asf.ponee.io@nifi.apache.org Thu Feb 13 18:36:03 2020 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 [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 43C091802C7 for ; Thu, 13 Feb 2020 19:36:03 +0100 (CET) Received: (qmail 45946 invoked by uid 500); 13 Feb 2020 18:36:02 -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 45936 invoked by uid 99); 13 Feb 2020 18:36:02 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Feb 2020 18:36:02 +0000 Received: from jira-he-de.apache.org (static.172.67.40.188.clients.your-server.de [188.40.67.172]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id DCE0DE00A5 for ; Thu, 13 Feb 2020 18:36:01 +0000 (UTC) Received: from jira-he-de.apache.org (localhost.localdomain [127.0.0.1]) by jira-he-de.apache.org (ASF Mail Server at jira-he-de.apache.org) with ESMTP id 3A949780B62 for ; Thu, 13 Feb 2020 18:36:00 +0000 (UTC) Date: Thu, 13 Feb 2020 18:36:00 +0000 (UTC) From: "Chris Sampson (Jira)" To: issues@nifi.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (NIFI-7145) Chained SplitText processors unable to handle files in some circumstances MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Chris Sampson created NIFI-7145: ----------------------------------- Summary: Chained SplitText processors unable to handle files i= n some circumstances Key: NIFI-7145 URL: https://issues.apache.org/jira/browse/NIFI-7145 Project: Apache NiFi Issue Type: Bug Affects Versions: 1.11.1 Environment: Docker Image (apache/nifi) running in Kubernetes (1.1= 5) Reporter: Chris Sampson Attachments: Broken_SplitText.json, Broken_SplitText.xml, test.csv= .tgz With chained SplitText processors (NiFi 1.11.1 apache/nifi Docker image wit= h default nifi.properties, although configured to allow secure access in my= environment with encrypted flowfile/provenance/content repositories, don't= know whether that makes a difference): * ingest 40MB CSV file with 50k lin= es of data (plus 1 header) * SplitText - chunk the file into 10k segments (including header in each f= ile) * SplitText - break each row out into its own FlowFile =C2=A0 The 10k chunking works fine, but then the files sit in the queue between th= e processors forever with the second SplitText sat showing it=E2=80=99s wor= king but never actually produces anything (can=E2=80=99t see anything in th= e logs, although haven=E2=80=99t turned on debug logging to see whether tha= t would provide anything more). =C2=A0 If I reduce the chunk size to 1k then the per-row split works fine - maybe = some sort of issue with SplitText and/or swapping of FlowFiles/content to t= he repositories? =C2=A0 Example Flow/Template attached with file that breaks the flow (untar and co= py into /tmp). Second SplitText set to Concurrency=3D3 in the template, but= fails just the same when set to default Concurrency=3D1. =C2=A0 SplitRecord would be an alternative (which works fine when I try it), but I= can=E2=80=99t use that as we potentially lose data if the CSV is malformed= (there are more data fields in a row that defined headers - the extra fiel= ds are thrown away by the Record processors, which I understand to be norma= l and that=E2=80=99s fine, but unfortunately I later need to ValidateRecord= for each of these rows to check for this kind of invalidity). -- This message was sent by Atlassian Jira (v8.3.4#803005)