From dev-return-11047-archive-asf-public=cust-asf.ponee.io@arrow.apache.org Fri Mar 15 12:01:11 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 945D3180627 for ; Fri, 15 Mar 2019 13:01:10 +0100 (CET) Received: (qmail 66013 invoked by uid 500); 15 Mar 2019 12:01:09 -0000 Mailing-List: contact dev-help@arrow.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@arrow.apache.org Delivered-To: mailing list dev@arrow.apache.org Received: (qmail 65995 invoked by uid 99); 15 Mar 2019 12:01:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Mar 2019 12:01:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 2D21AC054A for ; Fri, 15 Mar 2019 12:01:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.798 X-Spam-Level: * X-Spam-Status: No, score=1.798 tagged_above=-999 required=6.31 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id tpZXtsqLO9uy for ; Fri, 15 Mar 2019 12:01:06 +0000 (UTC) Received: from mail-io1-f47.google.com (mail-io1-f47.google.com [209.85.166.47]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id F357260CFE for ; Fri, 15 Mar 2019 12:01:05 +0000 (UTC) Received: by mail-io1-f47.google.com with SMTP id u12so7956564iop.11 for ; Fri, 15 Mar 2019 05:01:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=pp1zhe2QQJKU4dBShHJ6DOyU5v5r54DBcILGfb8ol+0=; b=g4tAD082WHNEEgLtxexTa4ZDqFxvBTBJW5JXqwzg2bKTsj3jRsFr3ftPaZIoKM2x12 vwf6CDpqd0jGxGHzAZFBlckzt1juvrSImLxULBgj4DeMSf1x+NKMBoV6sZ/uYEOJ6Svz SmyUhb1GYw3z1eKReGw+7ELQ32ACgXtEv8Gt2P1B1EUvXgk2qVV/2poGIXJWDhN0idfV NYDfiLcs0JziHbje8dYya0otfaeg2Tcs6pKJMlbmVqSGgeCbRuY0tGhp0n0PNOr0N6Xh FiKmwwXCDuCbK0Y+6AsV0VHmDpyCUaK9iKJ0lYWEplBhvSQlK86/xxZiKAM/jq8MyFMQ dgTg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=pp1zhe2QQJKU4dBShHJ6DOyU5v5r54DBcILGfb8ol+0=; b=YS3CcTOdNRVYUg2ZUtyoI4XvSguKjz0Rcm2dY3RbMy9nABwn0djfBcILX/ULmY2uuD 5fEZjk8eAf6K1+e5zo1DhMPNq94JgvUkgjpfIamqTYYavyr6e29QBH4IDISl14LG8Yb/ UcoGNM16dlwMzzUernTa6hIXS4WW7ZHD7cWpTW3EKiSMLty9B0rtvwXJU0XEMOlXiWq0 YQSZwIJ51wuEGhza48T7aQOrweW7gfwJ1Xp+h18EI/11mJvXLHAaZihKm7r1/KUozHPi IQ3ByyVzai9VsoC/BltT9T0Zxcz4hfbjrHB/SW/+Z/tkT5tVIzQtZlFPXt2MkbnUmFna BaWA== X-Gm-Message-State: APjAAAVVJI7hS0x9JpMb455sJyE2Y8/E8THyzLCD1Y2JAg6QsdyikPXV YeuiC4ad04vjI2DT1xfevBZGU4Qs0rVrYk5nMwbMUw== X-Google-Smtp-Source: APXvYqy50ZX9Xh25qWO2TvnhZS7sTSsyqpH1PdL0JOTaTTZCPH/3KR/eGwlHT5aTXg+1Hxbr222wPxWQrtq4BjSL0IM= X-Received: by 2002:a6b:db19:: with SMTP id t25mr1954989ioc.140.1552651258762; Fri, 15 Mar 2019 05:00:58 -0700 (PDT) MIME-Version: 1.0 From: Maxim Novikov Date: Fri, 15 Mar 2019 13:00:48 +0100 Message-ID: Subject: Arrow Flight RPC usage To: dev@arrow.apache.org Content-Type: multipart/alternative; boundary="000000000000bd1a17058420ca9f" --000000000000bd1a17058420ca9f Content-Type: text/plain; charset="UTF-8" Hello, I am evaluating Arrow RPC for usage with multidimensional Tensors. In my case, mostly 2D/3D images with multiple channels. Let's say I want to develop a service that applies a gaussian blur on a 2D image. From my understanding expected workflow is the following: 1. DoPut $key, image data 2. DoAction (blur $key) 2.1. Get image data from $key 2.2. Apply blur 2.3. Encode Tensor to result 3. Recv result on the client 4. Decode result Is it correct approach or am I misinterpreting the purpose of this API/endpoints? I didn't find any documentation except for a couple of slides and Flight.proto definition. I understand that docs are planned in the future, but maybe there is an issue/pull-request from which I can get more information about design decisions and expected use cases? -- Maksim Novikov, *Developer* *EMBL* --000000000000bd1a17058420ca9f--