From issues-return-81538-archive-asf-public=cust-asf.ponee.io@nifi.apache.org Sun Jul 21 09:47:05 2019 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 AF828180676 for ; Sun, 21 Jul 2019 11:47:04 +0200 (CEST) Received: (qmail 38255 invoked by uid 500); 21 Jul 2019 09:47:01 -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 38171 invoked by uid 99); 21 Jul 2019 09:47:01 -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; Sun, 21 Jul 2019 09:47:01 +0000 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 9AD81E2EDF for ; Sun, 21 Jul 2019 09: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 180B6265AA for ; Sun, 21 Jul 2019 09:47:00 +0000 (UTC) Date: Sun, 21 Jul 2019 09:47:00 +0000 (UTC) From: "Alessandro D'Armiento (JIRA)" To: issues@nifi.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (NIFI-6461) FileTransfer remote path should accept FlowFile attributes as expression variable scope 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/NIFI-6461?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro D'Armiento updated NIFI-6461: ---------------------------------------- Description:=20 h2. Current Situation FileTransfer based processors (ex: PutSFTP) only accept remote path variabl= es from the variable registry. Each flowfile sent through those processors = will be sent in the same directory. =C2=A0 h2. Improvement Proposal=C2=A0 It would be nice to be able to send flowfile to=C2=A0different locations ba= sed on their attributes, for example partitioning those files.=C2=A0 was: h2. Current Situation FileTransfer based processors (ex: PutSFTP) only accept remote path variabl= e from the variable registry. Each flowfile sent through those processors w= ill be sent in the same directory. =C2=A0 h2. Improvement Proposal=C2=A0 It would be nice to be able to send flowfile to=C2=A0different locations ba= sed on their attributes, for example partitioning those files.=C2=A0 > FileTransfer remote path should accept FlowFile attributes as expression = variable scope > -------------------------------------------------------------------------= -------------- > > Key: NIFI-6461 > URL: https://issues.apache.org/jira/browse/NIFI-6461 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework > Affects Versions: 1.9.2 > Reporter: Alessandro D'Armiento > Priority: Minor > > h2. Current Situation > FileTransfer based processors (ex: PutSFTP) only accept remote path varia= bles from the variable registry. Each flowfile sent through those processor= s will be sent in the same directory. > =C2=A0 > h2. Improvement Proposal=C2=A0 > It would be nice to be able to send flowfile to=C2=A0different locations = based on their attributes, for example partitioning those files.=C2=A0 -- This message was sent by Atlassian JIRA (v7.6.14#76016)