Skip to content

v0.16.4

Choose a tag to compare

@github-actions github-actions released this 12 Dec 14:16
· 37 commits to master since this release
7e5a1e6

Release v0.16.4

Highlights

  • Raphtory is now be available for Python 3.14.
  • We have dropped support for 3.10 to allow Raphtory to be brought up to date with the latest version of PyO3. The minimum Python version is now 3.11.

UI

  • Filtered out all non-valid edges in direct connections.
  • Added a node type loading indicator to search page to let you know when the graph has finished loading into the cache.
  • Added a new layout customiser panel which allows you to change the parameters of the layout algorithm and run multiple layouts as part of a pipeline.
image
  • Added node and edge styling which can be set in metadata for node types, layers or individual nodes and edges. Styles can be manually written into the graph or added from the UI. Currently, you can adjust the node colour or size and the edge colour in the timeline.

    • In the future, style options will expand to everything that our underlying graph visualisation library (g6) offers.
    image

image

Bug fixes


  • Fixed the DataFrame and Arrow loaders now correctly handle different datetime formats (including Date32).
  • Dataframe and Arrow loaders now correctly convert strings into timestamps (if possible) when provided as the time column. This brings them in line with the functionality of add_node and add_edge .
  • The GraphQL health check now goes through the read and write rayon pools before returning, so deadlocks don't go undetected when using it.
  • Added a check on otlp_agent_host to confirm the host accepts OpenTelemetry data (otherwise logs the failure to let the user know).
  • Enabled logs from OTLP libraries so any connection errors are properly logged when debug level is enabled.
  • Fixed an issue where the python server would only fail, given wrong arguments, after the timeout completes.

Known issues


What's Changed

This version also adds a docker compose setup under examples/grafana with:

  • Raphtory set up to send traces to Tempo.
  • Tempo set up to compute TraceQL metrics.
  • Grafana set up with tempo as a datasource and a basic dashboard template.
image

Full tracing for complex queries generates quite large spans so we have added some different tracing levels. Available options are:

  • COMPLETE: Provides full traces for each query.
  • ESSENTIAL: Tracks key functions — addEdge, addEdges, deleteEdge, graph, updateGraph, addNode, node, nodes, edge, edges.
  • MINIMAL: Provides only summary execution times.