Return-Path: <dev-return-2317-archive-asf-public=cust-asf.ponee.io@arrow.apache.org>
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 B49B3200C0B
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Sun, 15 Jan 2017 01:42:30 +0100 (CET)
Received: by cust-asf.ponee.io (Postfix)
	id B33CF160B35; Sun, 15 Jan 2017 00:42:30 +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 06240160B51
	for <archive-asf-public@cust-asf.ponee.io>; Sun, 15 Jan 2017 01:42:29 +0100 (CET)
Received: (qmail 73774 invoked by uid 500); 15 Jan 2017 00:42:29 -0000
Mailing-List: contact dev-help@arrow.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@arrow.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@arrow.apache.org>
List-Post: <mailto:dev@arrow.apache.org>
List-Id: <dev.arrow.apache.org>
Reply-To: dev@arrow.apache.org
Delivered-To: mailing list dev@arrow.apache.org
Received: (qmail 73763 invoked by uid 99); 15 Jan 2017 00:42:28 -0000
Received: from Unknown (HELO jira-lw-us.apache.org) (207.244.88.139)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 15 Jan 2017 00:42:28 +0000
Received: from jira-lw-us.apache.org (localhost [127.0.0.1])
	by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 6B3A025286
	for <dev@arrow.apache.org>; Sun, 15 Jan 2017 00:42:26 +0000 (UTC)
Date: Sun, 15 Jan 2017 00:42:26 +0000 (UTC)
From: "Nong Li (JIRA)" <jira@apache.org>
To: dev@arrow.apache.org
Message-ID: <JIRA.13033563.1484096525000.9776.1484440946437@Atlassian.JIRA>
In-Reply-To: <JIRA.13033563.1484096525000@Atlassian.JIRA>
References: <JIRA.13033563.1484096525000@Atlassian.JIRA> <JIRA.13033563.1484096525992@jira-lw-us.apache.org>
Subject: [jira] [Commented] (ARROW-474) Create an Arrow streaming file fomat
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Sun, 15 Jan 2017 00:42:30 -0000


    [ https://issues.apache.org/jira/browse/ARROW-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823001#comment-15823001 ] 

Nong Li commented on ARROW-474:
-------------------------------

https://github.com/apache/arrow/pull/288

> Create an Arrow streaming file fomat
> ------------------------------------
>
>                 Key: ARROW-474
>                 URL: https://issues.apache.org/jira/browse/ARROW-474
>             Project: Apache Arrow
>          Issue Type: Improvement
>            Reporter: Nong Li
>            Assignee: Nong Li
>
> It would be helpful to have a file/container layout that allows for streaming consumer and producers of arrow data.
> As a motivating example, a reader could have this API:
> Iterator<Record> read(java.io.InputStream source). 
> Similar a writer can have:
> void write(RecordBatch, java.io.OutputStream dest)
> The streams can be from a variety of sources: it be files, over the network, shared memory, pipe, etc. The layout would make it possible to implement
> both APIs without requiring intermediate buffering. 
> Speaking with Julien, this involves creating a simple container format similar to ARROW-264 but suitable for streaming consumer and producers. The layout in ARROW-264 has the schema at the end so can't be used in a streaming way. This format would likely be a rearranging of the current File layout pieces, something similar to:
> MAGIC, schema, totalBatches, (RecordBatchHeader, RecordBatchBody)*, MAGIC (or some end marker)
> totalBatches is optional for streaming producers that don't know.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)