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 5D836200CFE for ; Fri, 8 Sep 2017 16:58:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5C5FB160D5D; Fri, 8 Sep 2017 14:58:10 +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 A26CD160CB2 for ; Fri, 8 Sep 2017 16:58:09 +0200 (CEST) Received: (qmail 79213 invoked by uid 500); 8 Sep 2017 14:58: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 79204 invoked by uid 99); 8 Sep 2017 14:58: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; Fri, 08 Sep 2017 14:58: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 32C80D2954 for ; Fri, 8 Sep 2017 14:58: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-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 c9oLmgZW650F for ; Fri, 8 Sep 2017 14:58:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 326475F3D1 for ; Fri, 8 Sep 2017 14:58: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 708DDE06BF for ; Fri, 8 Sep 2017 14:58: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 290192414B for ; Fri, 8 Sep 2017 14:58:00 +0000 (UTC) Date: Fri, 8 Sep 2017 14:58:00 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: issues@nifi.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (NIFI-4306) UpdateRecord does not allow user to set root path to some child record MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 08 Sep 2017 14:58:10 -0000 [ https://issues.apache.org/jira/browse/NIFI-4306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158748#comment-16158748 ] ASF GitHub Bot commented on NIFI-4306: -------------------------------------- Github user markap14 commented on the issue: https://github.com/apache/nifi/pull/2103 @pvillard31 yeah at this point, the properties are given to use in a Map and not in any guaranteed order. So the updates are applied in some arbitrary order. If you have conflicting "rules" then there's no real way to determine what order they will be evaluated in. So if the first rule ( / => /accounts[1]/* ) is evaluated first then /name will evaluate to `null`. Otherwise, the /name will be updated and then the other rule will overwrite it... > UpdateRecord does not allow user to set root path to some child record > ---------------------------------------------------------------------- > > Key: NIFI-4306 > URL: https://issues.apache.org/jira/browse/NIFI-4306 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions > Reporter: Mark Payne > Assignee: Mark Payne > Fix For: 1.4.0 > > > If i have the following record: > {code} > { > "queue": { > "count": 1, > "size": "1 MB" > } > } > {code} > And I want to get rid of the 'queue' element I should be able to do so by using UpdateRecord with a property name of "/" and a value of "/queue/*" > Currently, if I try this, though, I get an error indicating that more than 1 element has been selected. We should instead just create a 'record' object with both the 'count' and 'size' fields and set that as the root so that the result is: > {code} > { > "count": 1, > "size": "1 MB" > } > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029)