Return-Path: X-Original-To: apmail-accumulo-user-archive@www.apache.org Delivered-To: apmail-accumulo-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 0A23D18ED6 for ; Mon, 7 Dec 2015 03:49:18 +0000 (UTC) Received: (qmail 22540 invoked by uid 500); 7 Dec 2015 03:49:17 -0000 Delivered-To: apmail-accumulo-user-archive@accumulo.apache.org Received: (qmail 22494 invoked by uid 500); 7 Dec 2015 03:49:17 -0000 Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@accumulo.apache.org Delivered-To: mailing list user@accumulo.apache.org Received: (qmail 22484 invoked by uid 99); 7 Dec 2015 03:49:17 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Dec 2015 03:49:17 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 26985C0473 for ; Mon, 7 Dec 2015 03:49:17 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.899 X-Spam-Level: ** X-Spam-Status: No, score=2.899 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id i1A4s4dtmVh2 for ; Mon, 7 Dec 2015 03:49:11 +0000 (UTC) Received: from mail-qg0-f41.google.com (mail-qg0-f41.google.com [209.85.192.41]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id C1611441C2 for ; Mon, 7 Dec 2015 03:49:10 +0000 (UTC) Received: by qgec40 with SMTP id c40so134651472qge.2 for ; Sun, 06 Dec 2015 19:49:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=dvEIKFBBUwOE9w9CN9bjxE4D6Dt6P/c0WwzqONE5/SE=; b=WUejWULwXjoSdpS2cxEKMAg0Cr1pJMrNcpyg8ooOYu/cQ2hR0vf3+7BytC7UMKlGxu 1yuPYxQNRB4ner7yVa50aq83SZzLjHDVqAmV83RMGFOPQnGOMyDMg+ctcLC9JMEn41sy qkCpeZbH9SYz6tMPvGzuCKpGzLtwA07xx48q+gluCUTzlX9eBARam2CmD1FzXQLPDrKt p9JZ/Cd2FrTHM2JjvC/spKoV/FIfe11bYKV3hKn9NLcn6UmZF0LAL6PQDsHJBMUcPDX2 PiuDBxkKI4yL8MfC/nfPL9kkNZ99lOAuDAfVRjY01LUHDK7HKDptLmFOCuTbjPibvqvo S2VQ== X-Received: by 10.140.163.198 with SMTP id j189mr36547806qhj.36.1449460144309; Sun, 06 Dec 2015 19:49:04 -0800 (PST) MIME-Version: 1.0 Received: by 10.55.207.65 with HTTP; Sun, 6 Dec 2015 19:48:44 -0800 (PST) Reply-To: baothaingo@gmail.com In-Reply-To: References: <565FBC11.30802@gmail.com> <565FBCE0.8050904@gmail.com> From: Thai Ngo Date: Mon, 7 Dec 2015 10:48:44 +0700 Message-ID: Subject: Re: Trigger for Accumulo table To: Accumulo User List Content-Type: multipart/alternative; boundary=001a1139b8f2048aeb052646bd48 --001a1139b8f2048aeb052646bd48 Content-Type: text/plain; charset=UTF-8 Christopher, This is interesting! Could you please give me more details about this? Thanks, Thai On Thu, Dec 3, 2015 at 12:17 PM, Christopher wrote: > You could also implement a constraint to notify an external system when a > row is updated. > > On Wed, Dec 2, 2015, 22:54 Josh Elser wrote: > >> oops :) >> >> [1] http://fluo.io/ >> >> Josh Elser wrote: >> > Hi Thai, >> > >> > There is no out-of-the-box feature provided with Accumulo that does what >> > you're asking for. Accumulo doesn't provide any functionality to push >> > notifications to other systems. You could potentially maintain other >> > tables/columns in which you maintain the last time a row was updated, >> > but the onus is on your "other services" to read the table to find out >> > when a change occurred (which is probably not scalable at "real time"). >> > >> > There are other systems you could likely leverage to solve this, >> > depending on the durability and scalability that your application needs. >> > >> > For a system "close" to Accumulo, you could take a look at Fluo [1] >> > which is an implementation of Google's "Percolator" system. This is a >> > system based on throughput rather than low-latency, so it may not be a >> > good fit for your needs. There are probably other systems in the Apache >> > ecosystem (Kafka, Storm, Flink or Spark Streaming maybe?) that are be >> > helpful to your problem. I'm not an expert on these to recommend on (nor >> > do I think I understand your entire architecture well enough). >> > >> > Thai Ngo wrote: >> >> Hi list, >> >> >> >> I have a use-case when existing rows in a table will be updated by an >> >> internal service. Data in a row of this table is composed of 2 parts: >> >> 1st part - immutable and the 2nd one - will be updated (filled in) a >> >> little later. >> >> >> >> Currently, I have a need of knowing when and which rows will be updated >> >> in the table so that other services will be wisely start consuming the >> >> data. It will make more sense when I need to consume the data in near >> >> realtime. So developing a notification function or simpler - a trigger >> >> is what I really want to do now. >> >> >> >> I am curious to know if someone has done similar job or there are >> >> features or APIs or best practices available for Accumulo so far. I'm >> >> thinking of letting the internal service which updates the data notify >> >> us whenever it updates the data. >> >> >> >> What do you think? >> >> >> >> Thanks, >> >> Thai >> > --001a1139b8f2048aeb052646bd48 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Christopher,

This is interesting! Could= you please give me more details about this?

Thank= s,
Thai

On Thu, Dec 3, 2015 at 12:17 PM, Christopher <ctubbsii@apache.org<= /a>> wrote:

You = could also implement a constraint to notify an external system when a row i= s updated.


On Wed, Dec 2, 2015, 22:54= =C2=A0Josh Elser <josh.elser@gmail.com> wrote:
oops :)

[1] http:/= /fluo.io/

Josh Elser wrote:
> Hi Thai,
>
> There is no out-of-the-box feature provided with Accumulo that does wh= at
> you're asking for. Accumulo doesn't provide any functionality = to push
> notifications to other systems. You could potentially maintain other > tables/columns in which you maintain the last time a row was updated,<= br> > but the onus is on your "other services" to read the table t= o find out
> when a change occurred (which is probably not scalable at "real t= ime").
>
> There are other systems you could likely leverage to solve this,
> depending on the durability and scalability that your application need= s.
>
> For a system "close" to Accumulo, you could take a look at F= luo [1]
> which is an implementation of Google's "Percolator" syst= em. This is a
> system based on throughput rather than low-latency, so it may not be a=
> good fit for your needs. There are probably other systems in the Apach= e
> ecosystem (Kafka, Storm, Flink or Spark Streaming maybe?) that are be<= br> > helpful to your problem. I'm not an expert on these to recommend o= n (nor
> do I think I understand your entire architecture well enough).
>
> Thai Ngo wrote:
>> Hi list,
>>
>> I have a use-case when existing rows in a table will be updated by= an
>> internal service. Data in a row of this table is composed of 2 par= ts:
>> 1st part - immutable and the 2nd one - will be updated (filled in)= a
>> little later.
>>
>> Currently, I have a need of knowing when and which rows will be up= dated
>> in the table so that other services will be wisely start consuming= the
>> data. It will make more sense when I need to consume the data in n= ear
>> realtime. So developing a notification function or simpler - a tri= gger
>> is what I really want to do now.
>>
>> I am curious to know if someone has done similar job or there are<= br> >> features or APIs or best practices available for Accumulo so far. = I'm
>> thinking of letting the internal service which updates the data no= tify
>> us whenever it updates the data.
>>
>> What do you think?
>>
>> Thanks,
>> Thai

--001a1139b8f2048aeb052646bd48--