Return-Path: X-Original-To: apmail-incubator-kafka-users-archive@minotaur.apache.org Delivered-To: apmail-incubator-kafka-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 67A7A989F for ; Fri, 21 Oct 2011 16:47:32 +0000 (UTC) Received: (qmail 57508 invoked by uid 500); 21 Oct 2011 16:47:30 -0000 Delivered-To: apmail-incubator-kafka-users-archive@incubator.apache.org Received: (qmail 57487 invoked by uid 500); 21 Oct 2011 16:47:30 -0000 Mailing-List: contact kafka-users-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: kafka-users@incubator.apache.org Delivered-To: mailing list kafka-users@incubator.apache.org Received: (qmail 57453 invoked by uid 99); 21 Oct 2011 16:47:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Oct 2011 16:47:30 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sharad.apache@gmail.com designates 209.85.214.47 as permitted sender) Received: from [209.85.214.47] (HELO mail-bw0-f47.google.com) (209.85.214.47) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Oct 2011 16:47:25 +0000 Received: by bkat8 with SMTP id t8so5337912bka.6 for ; Fri, 21 Oct 2011 09:47:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=+p5vhMW+qUuW+QoKXr+xF2KvUDHNJJvsjNNsSr1oJOo=; b=L+D81mqcgYl+reufIUHniBgp+44zVMAdXA83/OyVmnp/zu5tybp8jgIeBN6mxxogKy 5aPZQ8nAkyWeyw6s2JpsophDQw83NjsjapmLn8TnLBjdyVHvOCsJqJ1fJdjRSlsWegr1 Bl9MwsEYc6Zv5UsxNegEpmLtNm7mSo1IodC6U= MIME-Version: 1.0 Received: by 10.204.7.90 with SMTP id c26mr4280108bkc.92.1319215623730; Fri, 21 Oct 2011 09:47:03 -0700 (PDT) Received: by 10.204.121.147 with HTTP; Fri, 21 Oct 2011 09:47:03 -0700 (PDT) In-Reply-To: <004801cc900a$e6ca6bc0$b45f4340$@modelcitizen.com> References: <004801cc900a$e6ca6bc0$b45f4340$@modelcitizen.com> Date: Fri, 21 Oct 2011 22:17:03 +0530 Message-ID: Subject: Re: random access performance of messages. From: Sharad Agarwal To: kafka-users@incubator.apache.org Content-Type: multipart/alternative; boundary=0015175885daa277f604afd1d204 --0015175885daa277f604afd1d204 Content-Type: text/plain; charset=ISO-8859-1 kafka is more suited for sequential message reads. Not really meant for random message lookups. Also using kafka as *long* term message store is not a good usecase. On Fri, Oct 21, 2011 at 9:32 PM, wrote: > I would like to use Kafka to process messages that need to be immutably > stored for a N-days, and during that period the msgs need to be indexed, > searched, as well as retrieval of msg data that is queried. > > > > One approach is to read messages from Kafka and store the messages in a > secondary db for query and data retrieval. Once the messages are read and > processed into the secondary db, then the messages can be discarded from > the > Kafka queue. > > > > Another approach is to read the messages, build an external index for > searching that directly references the message data by Kafka-key in the > Kafka queue itself. In this case the Kafka becomes the message store for > the life of the message/data. > > > > The latter would be ideal for me if the performance of query-by-key and > message data retrieval is very good. > > > > Is random query of message+data good for Kafka? Is this an appropriate > usecase for Kafka? > > > > Thank you. > > > > Marko. > > . > > > > -- Thanks Sharad Agarwal Hadoop and Avro Committer Technology Platforms, InMobi *Disclaimer: Opinions expressed here are my own and do not represent past or present employers.* --0015175885daa277f604afd1d204--