Getting started with Raphtory only takes a few steps. We will first go through the different ways to install the packages required to run Raphtory. We will then download the Raphtory library and attach this to an example project to check that everything is working correctly. This quick start tutorial is based around a Lord of the Rings example, but there are several other examples available that it will work for, all of which are explored in the Examples Projects section of this tutorial.

Installing Java, Scala and SBT (Scala Build Tool)

Raphtory is a framework written in the Scala programming language, which runs on the JVM (Java virtual machine). As such both Java and Scala are required to run Raphtory. We additionally require SBT, the scala build tool, to compile and run your first Raphtory project.

Using SDK Man

Java, Scala and SBT are all very easy to install, but we must make sure that the correct versions are installed. To manage this we recommend the Software Development Kit Manager SDK Man. This allows you to install and switch between versions of all these libraries. SDK Man is available for Mac, Linux and Windows and can be installed by following their simple tutorial here.

Once you have this installed we will need to install a distribution of Java 11, Scala 13 and the latest version of SBT. Starting with java we can list the versions available via:

sdk list java

This will look something like the following:

Sdk Man java lists

The Vendor here (i.e. Corretto, GrallVM) doesn’t matter really, we just need to make sure that the major version (the first number) is 11. You can then copy the Identifier into the following command.

sdk install java IDENTIFIER

For instance: sdk install java 11.0.11.hs-adpt is the version I use

Once this is installed it should set this version as your default. You can then do the same for Scala and SBT - which only have one distributor and hence only version numbers. I have picked the latest version of Scala 13 and SBT below at the time of writing.

sdk install scala 2.13.7
sdk install sbt 1.6.2

To test that these are installed and working correctly you can run them with the --version argument to see if they are available on your class path and the correct version prints out.

java --version
scala -version

If the correct version hasn’t been set as default you can do this explicitly via sdkman. This is also how you can change back to another version of these libraries for other projects.

sdk use java 11.0.11.hs-adpt
sdk use scala 2.13.7
sdk use sbt 1.6.2

Everything should now be installed and ready for us to get your first Raphtory Job underway!

Running the latest Raphtory example projects via SBT

All example projects can be found in the Raphtory repo.

git clone

For this tutorial we are using the Lord of the Rings example, so we should now move into this directory - this is a totally independent sbt project.

cd examples/raphtory-example-lotr


You can now use the command sbt to start the Scala Build Tool. Once you see either the > or sbt:example-lotr> prompt, it means that you are in the SBT interactive shell. You can now run compile to build the project. This should produce output similar to below if working correctly:

sbt:example-lotr> compile
[info] compiling 3 Scala sources to /Users/YOUR_USERNAME/github/Examples/raphtory-example-lotr/target/scala-2.13/classes ...
[success] Total time: 3 s, completed 2 Feb 2022, 13:30:49


If there are a million errors saying that classes are not part of the package com.raphtory this is probably because your raphtory.jar did not publish correctly or your refresh of the sbt project did not occur. Alternatively if you have errors saying that something cannot be referenced as a URI, this is a Java version issue (the version you are using is higher than 11) and you should set the correct version as above.


To test that you have Raphtory working properly on your machine, use the command run when prompted again with >. From this you should get a request to select a main class (as can be seen below). Ignore the PulsarRunner, LOTRClient and LOTRService for now, these are used in the distributed deployment. We want to select number 4, the TutorialRunner.

Main Classes within the LOTR example

And you’re done! This will run the Lord of the Rings example that we will come back to in the next few tutorials.

Understanding the execution logs

First of all as Raphtory begins executing we should see some messages showing that the ingestion components of Raphtory are online and as such the system is ready for analysis to be performed. Don’t worry about what these are for the second, we will go through this in the next section.

Enter number: 4
[info] running com.raphtory.examples.lotrTopic.TutorialRunner
23:11:33.381 [run-main-0] INFO  com.raphtory.spouts.FileSpout - Spout: Processing file 'lotr.csv' ...
23:11:33.884 [] INFO  akka.event.slf4j.Slf4jLogger - Slf4jLogger started
23:11:34.808 [run-main-0] INFO - Creating '1' Partition Managers for raphtory_181811870.
23:11:34.856 [run-main-0] INFO - Creating new Query Manager.
23:11:34.862 [run-main-0] INFO - Created Graph object with deployment ID 'raphtory_181811870'.
23:11:34.862 [run-main-0] INFO - Created Graph Spout topic with name 'raphtory_data_raw_181811870'.

Next, we should see that our query has been submitted:

23:11:35.043 [run-main-0] INFO - Creating new Query Progress Tracker for 'DegreesSeparation_8822143620455242909'.
23:11:35.080 [] INFO  com.raphtory.internals.components.querymanager.QueryManager - Query 'DegreesSeparation_8822143620455242909' received, your job ID is 'DegreesSeparation_8822143620455242909'.
23:11:35.157 [monix-computation-138] INFO  com.raphtory.api.querytracker.QueryProgressTracker - Job DegreesSeparation_8822143620455242909: Starting query progress tracker.

Finally, once the data has completed ingesting, the query can run. The logs for this contain information about the Job ID, topics, perspectives, windows and the time it has taken to run.

23:11:37.247 [] INFO  com.raphtory.api.querytracker.QueryProgressTracker - Job 'DegreesSeparation_8822143620455242909': Perspective '32674' finished in 2202 ms.
23:11:37.247 [] INFO  com.raphtory.api.querytracker.QueryProgressTracker - Job DegreesSeparation_8822143620455242909: Running query, processed 1 perspectives.
23:11:37.255 [] INFO  com.raphtory.api.querytracker.QueryProgressTracker - Job DegreesSeparation_8822143620455242909: Query completed with 1 perspectives and finished in 2210 ms.

Checking your output

Once the query has finished executing Raphtory will not stop running. This is because we may submit more queries to the running instance, now that it has ingested the graph. However, you may now kill the Raphtory job and check out the output. For the example, results will be saved to /tmp/raphtory or the directory specified in the TutorialRunner class if you have changed it. Below is an example of the CSV file that has been output. This means that Raphtory is working as it should and you can move onto creating your first graph for analysis. The meaning of this output is only a couple pages away, so don’t threat if it looks a little odd right now!


Editing Raphtory core


If you are just building applications on top of Raphtory this section can be skipped as it discusses how to publish a new local version of Raphtory-core which can be used by your apps.

Once you have cloned the raphtory repo and made your changes you may build the new Raphtory jar and publish into the Maven folder on your local computer by running this command in your root Raphtory directory:

sbt "core/publishLocal"

If you are working on your application via Intellij you should give your sbt a refresh to reload the project locally and make sure it is using the new Raphtory jar. The button for this is the two rotating arrows located on the right hand side window within the sbt tab.

If you make any more changes to the core Raphtory code, you can go into your local ivy repo to delete the old jar and then re-publish using sbt "core/publishLocal". Alternatively, if you are making several iterative changes, you can add a dependency version := "0.1-SNAPSHOT" in the core build.sbt file and subsequent calls to sbt publishLocal will not require you to manually delete jars from your local repo. The Raphtory dependency in your project will need to be updated accordingly however.

cd ~/.ivy2/local/com.raphtory
rm (whichever jar you want to delete)