|
Re: New committer: David Pitera
Awesome! Welcome David!
--Ted
Awesome! Welcome David!
--Ted
|
By
Ted Wilmes <twi...@...>
·
#516
·
|
|
Re: New TSC member: Robert Dale
Great news, congrats Robert!
--Ted
Great news, congrats Robert!
--Ted
|
By
Ted Wilmes <twi...@...>
·
#515
·
|
|
Re: New TSC member: Robert Dale
Congratulations Robert! JanusGraph is lucky to have you on board.
Congratulations Robert! JanusGraph is lucky to have you on board.
|
By
sjudeng <sju...@...>
·
#514
·
|
|
Re: New committer: David Pitera
Thanks for all your contributions to the project and congratulations!
Thanks for all your contributions to the project and congratulations!
|
By
sjudeng <sju...@...>
·
#513
·
|
|
Re: New committer: David Pitera
Congrats, David!
By
Henry Saputra <henry....@...>
·
#511
·
|
|
Re: New TSC member: Robert Dale
Congrats, Robert!
By
Henry Saputra <henry....@...>
·
#510
·
|
|
Re: [PROPOSAL] Strict Schema
In our use of Titan and JanusGraph for several years now we have had a need for this. In fact, over two years ago we built our own ORM-like, schema-enforcement layer and have been using it ever since.
In our use of Titan and JanusGraph for several years now we have had a need for this. In fact, over two years ago we built our own ORM-like, schema-enforcement layer and have been using it ever since.
|
By
Austin Sharp <austins...@...>
·
#509
·
|
|
Re: [PROPOSAL] Strict Schema
I haven't fully thought about this yet, but my initial reaction is that (1) the schema enforcement should be opt-in and (2) we want to avoid performance degradation in the case that schema enforcement
I haven't fully thought about this yet, but my initial reaction is that (1) the schema enforcement should be opt-in and (2) we want to avoid performance degradation in the case that schema enforcement
|
By
David Pitera <piter...@...>
·
#512
·
|
|
Re: [PROPOSAL] Strict Schema
Hi Florian,
I think this would be a very worthwhile addition. Provided folks are in agreement, I think a good next step would be to spec out the additions to JanusGraphManagement, a format for the
Hi Florian,
I think this would be a very worthwhile addition. Provided folks are in agreement, I think a good next step would be to spec out the additions to JanusGraphManagement, a format for the
|
By
Ted Wilmes <twi...@...>
·
#508
·
|
|
New TSC member: Robert Dale
On behalf of the JanusGraph Technical Steering Committee (TSC), I'd like to welcome Robert Dale as a TSC member on the project. The TSC members ultimately guide the future direction of the
On behalf of the JanusGraph Technical Steering Committee (TSC), I'd like to welcome Robert Dale as a TSC member on the project. The TSC members ultimately guide the future direction of the
|
By
Jason Plurad <plu...@...>
·
#507
·
|
|
[PROPOSAL] Strict Schema
Currently, the schema for JanusGraph is basically only a list of allowedlabels (for vertices and edges) and available properties. What's missing in myopinion is the option to specify which vertex and
Currently, the schema for JanusGraph is basically only a list of allowedlabels (for vertices and edges) and available properties. What's missing in myopinion is the option to specify which vertex and
|
By
Florian Hockmann <f...@...>
·
#506
·
|
|
Re: Insertion of vertex with composite-indexed property fails due to type check assertion
Sounds fair enough to me. Feel free to open up an issue and pull request. Contributions are welcome.
Sounds fair enough to me. Feel free to open up an issue and pull request. Contributions are welcome.
|
By
Jason Plurad <plu...@...>
·
#505
·
|
|
Insertion of vertex with composite-indexed property fails due to type check assertion
Hello,
I stumbled into an issue with composite indices and data types: It happens when inserting a vertex with an indexed property that has the schema-defined type of "Object". With Java assertions
Hello,
I stumbled into an issue with composite indices and data types: It happens when inserting a vertex with an indexed property that has the schema-defined type of "Object". With Java assertions
|
By
rain...@...
·
#504
·
|
|
Re: New committer: David Pitera
Congrats, David. Look forward to more of your involvement here!
Congrats, David. Look forward to more of your involvement here!
|
By
Jerry He <jerr...@...>
·
#503
·
|
|
Re: New committer: David Pitera
Thanks guys-- am happy to help and looking forward to creating some great software together :)
Thanks guys-- am happy to help and looking forward to creating some great software together :)
|
By
David Pitera <piter...@...>
·
#502
·
|
|
Re: New committer: David Pitera
Thanks for all your work to help improve both Janus and the graph community at large David
Kelvin
Thanks for all your work to help improve both Janus and the graph community at large David
Kelvin
|
By
kelvin....@...
·
#501
·
|
|
Re: New committer: David Pitera
Great job, David, and thank you for your contributions! Great to have you as a committer on the project.
Great job, David, and thank you for your contributions! Great to have you as a committer on the project.
|
By
Misha Brukman <mbru...@...>
·
#499
·
|
|
New committer: David Pitera
On behalf of the JanusGraph Technical Steering Committee (TSC), I'm pleased to welcome a new committer on the project!
David Pitera has been a solid contributor. In the JanusGraph 0.2.0 release, he
On behalf of the JanusGraph Technical Steering Committee (TSC), I'm pleased to welcome a new committer on the project!
David Pitera has been a solid contributor. In the JanusGraph 0.2.0 release, he
|
By
Jason Plurad <plu...@...>
·
#500
·
|
|
Re: [DISCUSS] merge/commit flow for committers
A belated +1 from me on point #1 and I think the milestone hygiene makes sense.
Makes me wonder if we should also require folks to add an entry to the CHANGELOG for every contribution so it gets
A belated +1 from me on point #1 and I think the milestone hygiene makes sense.
Makes me wonder if we should also require folks to add an entry to the CHANGELOG for every contribution so it gets
|
By
Ted Wilmes <twi...@...>
·
#498
·
|
|
Re: DynamoDB storage backend
Cassandra and DynamDB have similar eventually consistent, scale-out, cluster types of architectures.
They are "essentially" unlimited in the amount of data, or cluster size.
Neptune - as of today - is
Cassandra and DynamDB have similar eventually consistent, scale-out, cluster types of architectures.
They are "essentially" unlimited in the amount of data, or cluster size.
Neptune - as of today - is
|
By
mcha...@...
·
#496
·
|