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 D4801200C7F for ; Wed, 24 May 2017 15:25:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D2FC2160BB4; Wed, 24 May 2017 13:25:07 +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 26C96160B9C for ; Wed, 24 May 2017 15:25:07 +0200 (CEST) Received: (qmail 31207 invoked by uid 500); 24 May 2017 13:25:06 -0000 Mailing-List: contact commits-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 commits@nifi.apache.org Received: (qmail 31197 invoked by uid 99); 24 May 2017 13:25:06 -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, 24 May 2017 13:25:06 +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 EBD621AA974 for ; Wed, 24 May 2017 13:25:05 +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 a4lkPjOZk7ud for ; Wed, 24 May 2017 13:25:05 +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 0B4925F23E for ; Wed, 24 May 2017 13:25:05 +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 988AEE0D2B for ; Wed, 24 May 2017 13:25:04 +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 4D82221B58 for ; Wed, 24 May 2017 13:25:04 +0000 (UTC) Date: Wed, 24 May 2017 13:25:04 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: commits@nifi.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (MINIFI-37) Native Volatile Content Repository implementation MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 24 May 2017 13:25:08 -0000 [ https://issues.apache.org/jira/browse/MINIFI-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022884#comment-16022884 ] ASF subversion and git services commented on MINIFI-37: ------------------------------------------------------- Commit d26d65af4448ddb054975601a9bf59f8660e6a8d in nifi-minifi-cpp's branch refs/heads/master from Marc Parisi [ https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;h=d26d65a ] MINIFI-37: Create a volatile repository and config items for NoOp and Volatile repository configuration Allow the max count of the volatile repository size to be configurable This closes #98. Signed-off-by: Aldrin Piri > Native Volatile Content Repository implementation > ------------------------------------------------- > > Key: MINIFI-37 > URL: https://issues.apache.org/jira/browse/MINIFI-37 > Project: Apache NiFi MiNiFi > Issue Type: Task > Components: C++, Core Framework > Reporter: Aldrin Piri > Assignee: marco polo > Priority: Minor > Labels: native > > Given the constrained environments in which MiNiFi could operate, it would be beneficial to provide a content repository that is strictly in memory for those environments where disk storage may be limited or non-existent. > This implementation should consider configuration options around its footprint such as number of entries held and/or sheer capacity. -- This message was sent by Atlassian JIRA (v6.3.15#6346)