We're winding down on JanusGraph 0.2.1. Ted's fixes have been merged, and there are only a few remaining PRs left to be merged. They are approved, so we're mostly waiting on doc updates/rebase. One

Hello, I was excited to hear last week that Apple had open sourced FoundationDB [1], a distributed ACID k/v store. I'm hopeful that it may fill a hole that Janus has in the distributed & ACID

Dear JG dev, I have a native/simple question but couldn't 'google' out its answer. I have JG+HBase setup. And once load the 'hbase,properties', I can see a HBase table called 'janusgraph' created

Hi, This thread should be in janusgraph-users. You problem is that your analyzer is not register. You can use custom_analyzer without register your analyzer if you use basic but known custom ES

I have this spring cloud POM file: <?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

Hello, JanusGraph enables users to utilize ElasticSearch as an additional indexing backend. Instructions on how to accomplish this is available here

Hi Jason, Thanks for kicking this off. I'm going to try to finish this one up this week: https://github.com/JanusGraph/janusgraph/pull/1000 If time allows, I think

JanusGraph uses some types and predicates that are not part of TinkerPop and therefore don't have serializers and deserializers in the different TinkerPop GLVs and language drivers. This means that

We were looking at a use case of using remote server mode of JanusGraph with Cassandra. While exploring various pros and cons we cam across this

I'm contributing to different rust project and they are using https://bors.tech/ which allows to merge PRs with more consistent. If you bors to merge a PR, it will merge the commits into a staging

Let's start a discussion on releases. This thread is for the master branch (0.3.0 release). The master branch has fixes and new features. The master branch is currently based on Apache TinkerPop 3.3.1

Let's start a discussion on releases. This thread is for the 0.2 branch (0.2.1 release), and I'll start a separate thread for the master branch (0.3.0 release). The 0.2 branch is for fixes only and no

This sounds like an interesting approach. I'd be in favor of anything that makes testing easier for contributors. What else specifically do you need to start working on your approach?

Hi It would be cool to reduce the number test retries. Currently, basically each test needed to fail three times to be called broken. I would like to see removing these technique. I have some idea to

I'm happy to take this one on. For a sanity check when I just ran docs/build-and-copy-docs.sh I got 308 separate javadoc errors, does this sound about right? If so I plan to go through and do a large

That issue is open and has not been resolved. Chris, if you want to run with it, I think the main thing to figure out is what kinds of permissions/authorizations the job would need. Along the same

When a committer merges a fix that needs to go into 0.2 and master, they need to follow up and make sure that the fix goes into master. Ideally this happens at about the same time. It looks like one

Hi all, None of the documentation fixes are getting pushed to the website. So from an end user perspective, they didn't happen. I know because I just ran into a documentation issue that was fixed back

Hello, I just threw a doc fix to 0.2.0 and went to do a merge commit when I ran into conflicts, see below: Chriss-MacBook-Pro-2:janusgraph chupman$ git status On branch merge-monitoring-doc-fix You

the ingestion is based on Vertices with 3-4 properties and edges connect them In case of event i need to : upsert vertices and create edges so i traverse on composite index twice to get vertices ( in