Re: Proposed Arrow Graph representations

hi folks, I have glanced at the Flatbuffers file with the proposed graph schemas. IP / licensing problems aside, I don't know enough about graph representations to have the context to judge whether this is the correct approach. My initial reaction is that the file is very long and without a

Re: Proposed Arrow Graph representations

hi Josh, Yes, the standard process for importing externally-developed code is the Incubator IP clearance: http://incubator.apache.org/ip-clearance/. As an example, we recently received a Go codebase donation from InfluxData where there was a combination of ICLAs from the contributors and a

Re: Proposed Arrow Graph representations

Hi Wes, I'm sure we're going to run into this with libgdf/pygdf as well. Is there a systematic way we could do a transfer of IP? On 5/20/18, 7:05 PM, "Wes McKinney" wrote: hi Paul, This is a great discussion to get started. I will review the patch in

Re: Proposed Arrow Graph representations

hi Paul, This is a great discussion to get started. I will review the patch in some more detail and send feedback > I've pushed Joe's initial GraphSchema.fbs to this branch on my Arrow fork I'm concerned the way this patch is set up right now is a little bit problematic from an IP lineage

Proposed Arrow Graph representations

At GTC San Jose last month, NVidia's Joe Eaton (cc'd) presented on the nvGraph team's goals for accelerating in-memory graph processing and analytics. A major component of that is advancing and standardizing a common, efficient representation for graphs that