janusgraph-dev@lists.lfaidata.foundation

Home Messages Hashtags Subgroups Calendar

Messages

Between

and

Re: [PROPOSAL] Replace FulgoraGraphComputer by IgniteGraphActors/IgniteGraphComputer

Hi, I have never heard of Apache Ignite and Kuppitz just introduced me to Apache Geode too. Crazy cool technologies. Personally, I think it would be great to try and build

By okram...@... · #24 ·

[DISCUSS] Moving toward an initial release

I’d like to start a discussion to flesh out a list of tasks necessary to make an initial release. Having a downloadable binary release and associated maven artifacts, IMO would help in terms of

By "P. Taylor Goetz" <ptg...@...> · #28 ·

Re: [PROPOSAL] Replace FulgoraGraphComputer by IgniteGraphActors/IgniteGraphComputer

David Robinson presented The Many Faces of Apache Ignite (PDF) at Apache: Big Data NA 2016. He has since moved on from IBM, so his work on Genesis Graph was unfinished and unreleased. It predated the

By Jason Plurad <plu...@...> · #26 ·

Re: [DISCUSS] Moving toward an initial release

Hi Taylor, Definitely agree on this! And we've had a number of users ask for this explicitly as well. No strong feelings on this matter, the Apache release process sounds good to me. We can start

By Misha Brukman <mbru...@...> · #29 ·

Re: [PROPOSAL] Replace FulgoraGraphComputer by IgniteGraphActors/IgniteGraphComputer

I will be testing JanusGraph on ScyllaDB.

By mathias...@... · #27 ·

Re: [DISCUSS] Moving toward an initial release

Apache release process sounds good to me. Perhaps we can discuss what to include on this list and then mark the relevant issues in github with the 0.1 milestone. As far as what to include, I think it

By Ted Wilmes <twi...@...> · #30 ·

Re: [DISCUSS] Moving toward an initial release

+1 We are on the same page. The first release will be an introduction release. New face, updated dependencies as appropriate, on par with Titan 1.0/1.1 in term of testing and quality, with

By Jerry He <jerr...@...> · #31 ·

Re: [DISCUSS] Moving toward an initial release

FYI, I created a milestone for the 0.1.0 release (since we're on 0.1.0-SNAPSHOT now): https://github.com/JanusGraph/janusgraph/milestone/1 Let's start adding all blockers to that milestone so that

By Misha Brukman <mbru...@...> · #32 ·

Re: [PROPOSAL] Replace FulgoraGraphComputer by IgniteGraphActors/IgniteGraphComputer

Hi, I'd be happy to help where I can. I'll read up a bit on Apache Ignite. Cheers Pieter

By Pieter Martin <pieter...@...> · #33 ·

Re: [PROPOSAL] Replace FulgoraGraphComputer by IgniteGraphActors/IgniteGraphComputer

I just want to clarify the proposal, so we will just need the IGFS portion of Apache Ignite to add in-memory cache on top of HDFS ?

By Henry Saputra <henry....@...> · #34 ·

Development process - testing

Hello JanusGraph developers, I'd like to request that the PR evaluation/approval process be updated to require successful local testing (mvn clean install) of all relevant test suites before merging

By sjudeng <sju...@...> · #35 ·

Re: Development process - testing

+1, given the current limitation with Travis CI. Thanks, Jerry

By Jerry He <jerr...@...> · #36 ·

Re: [DISCUSS] Moving toward an initial release

I created the following issue to get Sonatype Nexus setup so we can publish artifacts to maven central. https://github.com/JanusGraph/janusgraph/issues/97 Any committers interested in having the

By "P. Taylor Goetz" <ptg...@...> · #37 ·

HBase table definition and how flexible to change it?

hi, Guys new to this form and looking for a few pointers. I am fairly familiar with HBase, hence plan to use it as the backend. I went through the 'getting-started' tutorial, and have the example up

By Demai <nid...@...> · #38 ·

Re: HBase table definition and how flexible to change it?

This is a good video that I would recommend -> https://youtu.be/tLR-I53Gl9g I would keep your vertex, edges, and properties together. Thank You, Irving Duran

By Irving Duran <irvin...@...> · #39 ·

Re: HBase table definition and how flexible to change it?

Irving, thanks for the pointers. Neo4j is still running on single server, though there are efforts with data distribution/partition to support true cluster. maybe Neo4j doesn't worry about

By Demai Ni <nid...@...> · #40 ·

Re: HBase table definition and how flexible to change it?

The edges, vertices, properties and indexes are stored in a fixed table and a fixed set of column families within the table in HBase. i.e. edges are in one CF, properties are in another CF. They are

By Jerry He <jerr...@...> · #41 ·

Re: HBase table definition and how flexible to change it?

Jerry, thanks for the pointer. Since they are stored in different CFs, it is a bit similar as Neo4j. I have the janusGraph up and running on my mac on top of HBase 1.2, thanks for the effort to make

By Demai <nid...@...> · #42 ·

Re: HBase table definition and how flexible to change it?

interesting. I followed the example from the 'getting start' section. The HBase table contains quick a few (9 to be exact) column families, and the columnfamily name is from 'e' to 't', which I guess

By Demai <nid...@...> · #43 ·

Re: [DISCUSS] Development Process

A pull request has been submitted for this work: https://github.com/JanusGraph/janusgraph/pull/106. --Ted

By Ted Wilmes <twi...@...> · #44 ·

21 - 40 of 1612

Home Hashtags Subgroups Calendar Terms