Return-Path: X-Original-To: apmail-flume-user-archive@www.apache.org Delivered-To: apmail-flume-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C758110809 for ; Wed, 5 Mar 2014 18:47:52 +0000 (UTC) Received: (qmail 15941 invoked by uid 500); 5 Mar 2014 18:47:51 -0000 Delivered-To: apmail-flume-user-archive@flume.apache.org Received: (qmail 15905 invoked by uid 500); 5 Mar 2014 18:47:50 -0000 Mailing-List: contact user-help@flume.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@flume.apache.org Delivered-To: mailing list user@flume.apache.org Received: (qmail 15897 invoked by uid 99); 5 Mar 2014 18:47:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Mar 2014 18:47:49 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jimmyjack@gmail.com designates 209.85.220.174 as permitted sender) Received: from [209.85.220.174] (HELO mail-vc0-f174.google.com) (209.85.220.174) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Mar 2014 18:47:44 +0000 Received: by mail-vc0-f174.google.com with SMTP id im17so1440728vcb.19 for ; Wed, 05 Mar 2014 10:47:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=+fQXOzZ+vM58fmuYBpDwysjBWMVkj0oHH6xuVfQmGzA=; b=kJGWWS9RgMhFE0h/6Y9Woqq7NXGjmgBTTKI69VBBlSIdP7oubeIUHp/ZSmZG5hdP+j iZHKSyjM6v/vZhnURTOe2IJZKza4LAEXajVbCJq0J+5KQYuLDMX1JqN6dZdzmV7mrfSN hiPap4Y3L9Z6LRJs6+wcG/zNVLMXeoh6S65R1O1h6PMpQOigucy+YDThLH34mGQBrI+h z8dEsz5w8JGwyWXSarj3UxZgaZft275GmAtqxW0lkUAuXvUQN9WHsJz09FkFsBVvS4mo qAAeifEeIDP8ULw1NrTUE/3gyNwILF9Qhd/VVfM2qnEeqHdgOZBKuxyrib/PB7BFBZw8 iD/A== MIME-Version: 1.0 X-Received: by 10.220.88.204 with SMTP id b12mr1150770vcm.3.1394045243470; Wed, 05 Mar 2014 10:47:23 -0800 (PST) Received: by 10.220.155.139 with HTTP; Wed, 5 Mar 2014 10:47:23 -0800 (PST) Date: Wed, 5 Mar 2014 10:47:23 -0800 Message-ID: Subject: File Channel Capacity vs transactionCapacity From: Jimmy To: user@flume.apache.org Content-Type: multipart/alternative; boundary=047d7b3a92ee89b93c04f3e073ef X-Virus-Checked: Checked by ClamAV on apache.org --047d7b3a92ee89b93c04f3e073ef Content-Type: text/plain; charset=ISO-8859-1 perhaps strange question, but looking at the documentation for flume 1.4 under FILE CHANNEL transactionCapacity1000The maximum size of transaction supported by the channel capacity1000000Maximum capacity of the channel is transactionCapacity truly a size of transaction? Isn't it number of transactions per event consumed? thank you --047d7b3a92ee89b93c04f3e073ef Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
perhaps strange question, but looking at the documentation= for flume 1.4 under FILE CHANNEL

transactionCapacity 1000The max= imum size of transaction supported by the channel

=



is transactio= nCapacity truly a size of transaction? Isn't it number of transactions = per event consumed?



thank you

--047d7b3a92ee89b93c04f3e073ef--
capacity100= 0000 Maximum capacity of the channel