From user-return-22347-apmail-spark-user-archive=spark.apache.org@spark.apache.org Sat Dec 13 02:46:03 2014 Return-Path: X-Original-To: apmail-spark-user-archive@minotaur.apache.org Delivered-To: apmail-spark-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C50129572 for ; Sat, 13 Dec 2014 02:46:03 +0000 (UTC) Received: (qmail 67838 invoked by uid 500); 13 Dec 2014 02:46:01 -0000 Delivered-To: apmail-spark-user-archive@spark.apache.org Received: (qmail 67766 invoked by uid 500); 13 Dec 2014 02:46:01 -0000 Mailing-List: contact user-help@spark.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list user@spark.apache.org Received: (qmail 67755 invoked by uid 99); 13 Dec 2014 02:46:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Dec 2014 02:46:01 +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 (nike.apache.org: domain of yvsunil@gmail.com designates 209.85.218.43 as permitted sender) Received: from [209.85.218.43] (HELO mail-oi0-f43.google.com) (209.85.218.43) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Dec 2014 02:45:35 +0000 Received: by mail-oi0-f43.google.com with SMTP id a3so6083485oib.30 for ; Fri, 12 Dec 2014 18:44:04 -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=BYs+r9deftJ+DaSWkUV4uh31hQFTglLYH3kURN35fAg=; b=EwRNM9ifFAxufmBFmGAG05iOvnydl/0FL2VIQCd1Wu0XNmGZJHNMDFIcF5W+8tgi3r 2phc1Ub+Q7HD5cweY7TgYaIyMKRk/kCfcWsAFQLhoDSjYcq9bxHZXBb09UgkCGChERZz UqhDf9YMN4sBDbd1FpBCHa1xQBJpehqGJ/LC2UijhNeDHCNZJDQcBkOH+o6Z54an47GT L0cpzG1dCd82D8YvnIQ5F0C8mAE2/OUysdORT8sCYVzMGfbQznBujCDZqIZeog7MiFgl C0SV1Sd/v8w8npitbFnsnZWuMRPvOYlqcsjOtzuz73RuTxnT4iQd4I+lb95H3YeBfru3 MNBQ== MIME-Version: 1.0 X-Received: by 10.182.241.133 with SMTP id wi5mr12181716obc.10.1418438644018; Fri, 12 Dec 2014 18:44:04 -0800 (PST) Received: by 10.202.213.67 with HTTP; Fri, 12 Dec 2014 18:44:03 -0800 (PST) Date: Fri, 12 Dec 2014 18:44:03 -0800 Message-ID: Subject: clean up of state in State Dstream From: Sunil Yarram To: "user@spark.apache.org" Content-Type: multipart/alternative; boundary=089e01634be8833310050a0ffb5f X-Virus-Checked: Checked by ClamAV on apache.org --089e01634be8833310050a0ffb5f Content-Type: text/plain; charset=UTF-8 I am using *updateStateByKey *to maintain state in my streaming application, the state gets accumulated over time. Is there a way i can delete the old state data or put a limit on the amount of state the State Dstream can keep in the system. Thanks, Sunil. --089e01634be8833310050a0ffb5f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I am using=C2=A0updateStateByKey to maintain state in my streaming application, the state get= s accumulated over time.=C2=A0
Is there a way i can delete the old state data or p= ut a limit on the amount of state the State Dstream can keep in the system.=
=
Thanks,
Sunil.

--089e01634be8833310050a0ffb5f--