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 04C90D774 for ; Mon, 30 Jul 2012 17:51:16 +0000 (UTC) Received: (qmail 86512 invoked by uid 500); 30 Jul 2012 17:51:15 -0000 Delivered-To: apmail-flume-user-archive@flume.apache.org Received: (qmail 86456 invoked by uid 500); 30 Jul 2012 17:51:15 -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 86448 invoked by uid 99); 30 Jul 2012 17:51:15 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Jul 2012 17:51:15 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of Yongcheng.Li@sas.com designates 216.32.181.181 as permitted sender) Received: from [216.32.181.181] (HELO ch1outboundpool.messaging.microsoft.com) (216.32.181.181) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Jul 2012 17:51:07 +0000 Received: from mail105-ch1-R.bigfish.com (10.43.68.252) by CH1EHSOBE004.bigfish.com (10.43.70.54) with Microsoft SMTP Server id 14.1.225.23; Mon, 30 Jul 2012 17:50:47 +0000 Received: from mail105-ch1 (localhost [127.0.0.1]) by mail105-ch1-R.bigfish.com (Postfix) with ESMTP id 1EDFF4200EE for ; Mon, 30 Jul 2012 17:50:47 +0000 (UTC) X-Forefront-Antispam-Report: CIP:149.173.6.164;KIP:(null);UIP:(null);IPV:NLI;H:mercav08d.na.sas.com;RD:mercav08d.na.sas.com;EFVD:NLI X-SpamScore: -3 X-BigFish: S-3(zzc85fh103dKzz1202hzz8275bh8275dhz2fh2a8h668h839hcf6hd25hf0ah107ah) Received-SPF: pass (mail105-ch1: domain of sas.com designates 149.173.6.164 as permitted sender) client-ip=149.173.6.164; envelope-from=Yongcheng.Li@sas.com; helo=mercav08d.na.sas.com ;d.na.sas.com ; Received: from mail105-ch1 (localhost.localdomain [127.0.0.1]) by mail105-ch1 (MessageSwitch) id 1343670646474877_16384; Mon, 30 Jul 2012 17:50:46 +0000 (UTC) Received: from CH1EHSMHS037.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.254]) by mail105-ch1.bigfish.com (Postfix) with ESMTP id 68172340046 for ; Mon, 30 Jul 2012 17:50:46 +0000 (UTC) Received: from mercav08d.na.sas.com (149.173.6.164) by CH1EHSMHS037.bigfish.com (10.43.69.246) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 30 Jul 2012 17:50:25 +0000 X-TM-IMSS-Message-ID: <5531547a00027c0b@mercav08d.na.sas.com> Received: from MERCHUB01D.na.SAS.com ([10.36.10.59]) by mercav08d.na.sas.com ([10.36.10.12]) with ESMTP (TREND IMSS SMTP Service 7.1; TLSv1/SSLv3 AES128-SHA (128/128)) id 5531547a00027c0b ; Mon, 30 Jul 2012 13:50:17 -0400 Received: from MERCMBX13R.na.SAS.com ([fe80::3951:675c:13fb:edd]) by MERCHUB01D.na.SAS.com ([10.36.10.59]) with mapi id 14.02.0298.004; Mon, 30 Jul 2012 13:50:16 -0400 From: Yongcheng Li To: "user@flume.apache.org" Subject: Production-Level Recoverable Memory Channel Thread-Topic: Production-Level Recoverable Memory Channel Thread-Index: Ac1ue8bzxw9OfyrrQLaUYUsjp7+96g== Date: Mon, 30 Jul 2012 17:50:16 +0000 Message-ID: <5937F16717A11040B251525519446CBE0392186F@MERCMBX13R.na.SAS.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.26.11.41] Content-Type: multipart/alternative; boundary="_000_5937F16717A11040B251525519446CBE0392186FMERCMBX13RnaSAS_" MIME-Version: 1.0 X-OriginatorOrg: sas.com X-Virus-Checked: Checked by ClamAV on apache.org --_000_5937F16717A11040B251525519446CBE0392186FMERCMBX13RnaSAS_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, In "Flume 1.3.0-SNAPSHOT User Guide", it states that "The Recoverable Memor= y Channel is currently experimental and is not yet ready for production use= . This channel's properties are being documented here in advance of its com= pletion.". When (in which release) will Flume provide a production-level re= coverable memory channel? Thanks! Yongcheng --_000_5937F16717A11040B251525519446CBE0392186FMERCMBX13RnaSAS_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

In "Flume 1.3.0-SNAPSHOT User Guide", i= t states that "The Recoverable Memory Channel is currently experimenta= l and is not yet ready for production use. This channel's properties are be= ing documented here in advance of its completion.". When (in which release) will Flume provide a production-level recoverable = memory channel?

 

Thanks!

 

Yongcheng

 

--_000_5937F16717A11040B251525519446CBE0392186FMERCMBX13RnaSAS_--