"hello world" makes sense as a good place to start for general IPC integration.
I thought there was still some disconnect on how strings were going to
be represented. That was the basis for my suggestion above. But the
integer use-case bypasses these concerns for now.
On Wed, May 25, 2016 at 2:
By usecase, I really meant "hello world"
On Wed, May 25, 2016 at 2:09 PM, Jacques Nadeau wrote:
> Let's start by creating a simple usecase. For example, I would start with
> nullable 4 byte integer, maybe and use the example of java > (col1) >
> python (or c++) > (newcol) > java that is one what
Let's start by creating a simple usecase. For example, I would start with
nullable 4 byte integer, maybe and use the example of java > (col1) >
python (or c++) > (newcol) > java that is one what I'd call a single batch
algorithm (e.g. one batch of values in, one out).
A simple way to sidestep the
Laurent Goujon created ARROW-208:
Summary: Add checkstyle policy to java project
Key: ARROW-208
URL: https://issues.apache.org/jira/browse/ARROW-208
Project: Apache Arrow
Issue Type: Bug
Just to follow-up on this. I got distracted on a few other items on
the C++ implementation side, but my next task is to get a String types
working for the C++ IPC unit test. Once I send a PR for that, it
might help clarify the concerns on both sides and we can hammer out
the details from there.
