Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id EDC4A200AE2 for ; Fri, 27 May 2016 17:34:29 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id ECA3F160A12; Fri, 27 May 2016 15:34:29 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 1A5DE160A10 for ; Fri, 27 May 2016 17:34:28 +0200 (CEST) Received: (qmail 88427 invoked by uid 500); 27 May 2016 15:34:28 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 88417 invoked by uid 99); 27 May 2016 15:34:28 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 May 2016 15:34:28 +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 CB5EAC0EDE for ; Fri, 27 May 2016 15:34:27 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.198 X-Spam-Level: * X-Spam-Status: No, score=1.198 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-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-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id Ennshu3YbR5n for ; Fri, 27 May 2016 15:34:25 +0000 (UTC) Received: from mail-qk0-f172.google.com (mail-qk0-f172.google.com [209.85.220.172]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id C19FA5F2EF for ; Fri, 27 May 2016 15:34:24 +0000 (UTC) Received: by mail-qk0-f172.google.com with SMTP id h185so48612574qke.2 for ; Fri, 27 May 2016 08:34:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=y9BTKPrHDcntGsA5vowczDmHUzSC56j5yvTSRq5TV2c=; b=AUep4XyD/EUTaCKKmj/JPOT8vq/tYxa57EUNtk/B9MCJzpzBQMIxaGuRhol1wPyF75 0g2vMI89y4AEWlkknPJiylGnYjh/vXLCExjCwCVtRM+cAnBFvA7kqnB3+lr138IYoJKG z1YAN5fnBKarJGj46vO9R5g3roHsJ1dFWmIcEaKIcrD1D2fi06kp/U/QegdQEYBiwM2Z rcqcWeTwTewN1UvvFVMaqKMsimfkceOB+GZ8QzBO+j9lXXHKaAcx0r00tMsLIBPd98g3 cyGmY2Fp5FWso/V3/uSzdF+yeJrOq8Hg45HxSeWyPXBtc8ms1guQ/ZN4AWAUUV1F7eJX WMlw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=y9BTKPrHDcntGsA5vowczDmHUzSC56j5yvTSRq5TV2c=; b=Qv/YjL/sgB4W0plm+3ISIRF45vVnAZteYA/909T0MBD3Zvkk6l2WhbP5eaVyF/4s3N pYQA2R7efuF5EsswMOj2xrrdngKjJD5Bd9QIbA4wKyIx13vDJFFN5VMuY+5DZ5ywXJ4O ae+5wWRcbu3ReXJmMt4vTWGhjNrq1gMjwrDd7hsYkvO5vtjAk2R1ixvGOM3ly4gosIym /i1dTTwqOEntusbElmFAUoufOc9Tur800Ch7MIgzdHnEjZiaN58Q1oT06go0Olr5ojy0 z9LizI5zjSR1d4mt4Y51PxDh/V2uQV7bIj+V0pBqaggKhx6dAMlpFA+GgGY8pNOxZI2g tH6Q== X-Gm-Message-State: ALyK8tKmfOCKN+TTid+QF8QLkyTk+X8P3ySiOHEuTMk094x/OBg0aS2thsGvuvt/wxxafvItB+NyVsjIApVEKQ== MIME-Version: 1.0 X-Received: by 10.55.78.9 with SMTP id c9mr14853761qkb.0.1464363258104; Fri, 27 May 2016 08:34:18 -0700 (PDT) Received: by 10.140.41.75 with HTTP; Fri, 27 May 2016 08:34:17 -0700 (PDT) In-Reply-To: <1464356982655-5282.post@n6.nabble.com> References: <1464356982655-5282.post@n6.nabble.com> Date: Fri, 27 May 2016 18:34:17 +0300 Message-ID: Subject: Re: Simulating Graph Dependencies With Ignite From: Alexei Scherbakov To: user@ignite.apache.org Content-Type: multipart/alternative; boundary=001a114a8a52d254180533d4a332 archived-at: Fri, 27 May 2016 15:34:30 -0000 --001a114a8a52d254180533d4a332 Content-Type: text/plain; charset=UTF-8 Hi, You can store cell dependencies as Ignite's data grid of IgniteCache cells = ... where relation between key and value is interpreted like: value depends on key. When the cell is updated you do the following: Cell cell = updated; do { recalculate(cell); } while( (cell = cells.get(cell)) != null); Did it help ? 2016-05-27 16:49 GMT+03:00 pragmaticbigdata : > Hello, > > I have started exploring apache ignite by following the introductory > videos. > It looks quite promising and I wanted to understand if it will be well > suited for the use case I brief out below. If so, I would be glad to hear > out on how could I approach it > > The use case is > > We are trying to implement cell level dependencies within multiple tables. > It's similar to the functionality excel offers just that in our case it > could span across multiple tables. Imagine multiple cells in an excel > worksheet having interdependent formula's where updating a value in one > cell > causes another cell value to change and that cell update causes another > cell > value to update and so on and so forth. It is kind of graph of dependencies > that determines what is the next row cell that needs to be updated. > > With apache ignite, what api's and data structures could I use to maintain > a > graph of inter-dependencies between multiple tables? Note that these would > be metadata dependencies and not data. > > I would appreciate to get inputs on this. > > Thanks, > Amit > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Simulating-Graph-Dependencies-With-Ignite-tp5282.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Best regards, Alexei Scherbakov --001a114a8a52d254180533d4a332 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

You can store cell dependencies as = Ignite's data grid of

IgniteCache<Cell, Cel= l> cells =3D ...

where relation between key and= value is interpreted like: value depends on key.

= When the cell is updated you do the following:

Cel= l cell =3D updated;
do {
=C2=A0 =C2=A0 =C2=A0recalculat= e(cell);
} while( (cell =3D cells.get(cell)) !=3D null);

Did it help ?



=


2016-05-27 16:49 GMT+03:00 pragmaticbigdata <= ;amits.84@gmail.com= >:
Hello,

I have started exploring apache ignite by following the introductory videos= .
It looks quite promising and I wanted to understand if it will be well
suited for the use case I brief out below. If so, I would be glad to hear out on how could I approach it

The use case is

We are trying to implement cell level dependencies within multiple tables.<= br> It's similar to the functionality excel offers just that in our case it=
could span across multiple tables. Imagine multiple cells in an excel
worksheet having interdependent formula's where updating a value in one= cell
causes another cell value to change and that cell update causes another cel= l
value to update and so on and so forth. It is kind of graph of dependencies=
that determines what is the next row cell that needs to be updated.

With apache ignite, what api's and data structures could I use to maint= ain a
graph of inter-dependencies between multiple tables? Note that these would<= br> be metadata dependencies and not data.

I would appreciate to get inputs on this.

Thanks,
Amit



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.co= m/Simulating-Graph-Dependencies-With-Ignite-tp5282.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.



--

Best r= egards,
Alexei Scherbakov
--001a114a8a52d254180533d4a332--