From dev-return-16523-archive-asf-public=cust-asf.ponee.io@nifi.apache.org Mon Feb 26 13:31:29 2018 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 [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id A79BB18064A for ; Mon, 26 Feb 2018 13:31:28 +0100 (CET) Received: (qmail 18151 invoked by uid 500); 26 Feb 2018 12:31:27 -0000 Mailing-List: contact dev-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 dev@nifi.apache.org Received: (qmail 18139 invoked by uid 99); 26 Feb 2018 12:31:26 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Feb 2018 12:31:26 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 4B38AC0040 for ; Mon, 26 Feb 2018 12:31:26 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.879 X-Spam-Level: * X-Spam-Status: No, score=1.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id zMC2jjwqsqq2 for ; Mon, 26 Feb 2018 12:31:25 +0000 (UTC) Received: from mail-oi0-f50.google.com (mail-oi0-f50.google.com [209.85.218.50]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id BE0155F20B for ; Mon, 26 Feb 2018 12:31:24 +0000 (UTC) Received: by mail-oi0-f50.google.com with SMTP id g5so4315843oiy.8 for ; Mon, 26 Feb 2018 04:31:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=NVrdEkd4I5PbgblTozZB/F0tcjKfEOGySMWo8FSinas=; b=W9gCxJitpTNakesztnCGPszkMVYrozyLu6chTXJcUeRyxrTrGFXsWoLTaIjdLBPDuX 01GJEu9yIDqApVxZlC8xxhsPGdhYgtfPlErjV+v/oxxFQ0aXz2Ibyal8xj3SX9HI0D7L CvseooYGfTGZ6VPGTtdRFo/jw0/5PTqzIdDjD0+A/Y7vfePIuuc7JUzvw2cYjudD1YIG NWhr/8Hkb6IXPLAvbkKWRddeoZOfQoKbp0y0K1HXUFsofhrZzWzaWojWWd9lxMLDiZg3 gOYDoEaWBOAis+Iv+fMp+RgpKlovxQO1qi1jbb7tMi/0vIH6jd2fGpr92fQ0uERH2mm1 Tv7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=NVrdEkd4I5PbgblTozZB/F0tcjKfEOGySMWo8FSinas=; b=KZdRnqfE0VK8YKjSrpQwRnc73JEzDV4uoQScM18YZdI/FubzHv5GxgIjqXjiruaF9r N0NhX45sra7dpY144F9PqII7NM+q0Mg3UwIhjfl9mcVCHux2gFVMEuo64eS4xQ6svMJ+ dNMyv3CSVHAcC+OcWau70kOBP4eGn2NtdT7FtOyKX5hUvg8PDTWQHJGMGFjdbF5XFnH7 idRDTWK0My9DXC1pCDE7tYFmSjtOzQGmDY8rTXmI14FtpgYz/RINfA+PbuLEmxYON4mu zoAVMb1UrURxMVWWByMlCIlC8uwVTYlceDFPOq5plm+ZwTLVazn6p6ZE0ob5A4jJ0ST2 dN0A== X-Gm-Message-State: APf1xPCc5aR13u0AO5FAn6Nqcp98auomcTHkhjEqe0rjtJ1b4VVKUeSx QTkVA0NO7ynCilaPZAiQOL3ybQrQAu/dBvwp6wk= X-Google-Smtp-Source: AG47ELvLGgzMscDmDKRPyuUbcPGUsgNt0pYGtOadlEfG9YmFIr+oQlgpJ8EJqrsx8mcmgvVmpASdIXFKaXawEy4h36g= X-Received: by 10.202.19.16 with SMTP id e16mr6795377oii.46.1519648283241; Mon, 26 Feb 2018 04:31:23 -0800 (PST) MIME-Version: 1.0 Received: by 10.74.128.140 with HTTP; Mon, 26 Feb 2018 04:31:22 -0800 (PST) From: Mike Thomsen Date: Mon, 26 Feb 2018 07:31:22 -0500 Message-ID: Subject: PutElasticsearchHttpRecord writing null values To: dev@nifi.apache.org Content-Type: multipart/alternative; boundary="f4f5e808c9541b424005661cb0f8" --f4f5e808c9541b424005661cb0f8 Content-Type: text/plain; charset="UTF-8" I have a client that uses that processor and doesn't like the fact that null record fields get sent to ElasticSearch instead of excluded from the payload. Does anyone know if there is a good reason to keep that behavior? It doesn't seem to add anything except line noise when looking at the results from ElasticSearch. Thanks, Mike --f4f5e808c9541b424005661cb0f8--