Determining the Installed Apache TinkerPop Version

Knowing the exact version of Apache TinkerPop and the Gremlin Console in use is a fundamental operational concern. Version differences can affect:

 

·      Available Gremlin steps and traversal semantics

·      Behavior of drivers, plugins, and serialization formats

·      Compatibility with graph providers and remote servers

·      Reproducibility of examples and troubleshooting outcomes

 

For these reasons, checking the running version should be one of the first diagnostic steps when working with Gremlin, especially in shared environments or across multiple machines.

 

Checking the Version from Inside the Gremlin Console

The most direct way to determine the version is from within an active Gremlin Console session. The console exposes version information through the Gremlin utility class:

Gremlin.version()

gremlin> Gremlin.version()
==>3.8.0

This value represents:

·      The version of the Apache TinkerPop distribution

·      The version of the Gremlin traversal engine

·      The version of the Gremlin Console runtime

 

This call returns the version of the Apache TinkerPop distribution that the console is currently using. It reflects the runtime environment, not merely the version of a script or configuration file. This distinction is important when diagnosing issues caused by mismatched installations or stale binaries.

 

Conceptually, this method answers the question “Which TinkerPop runtime is executing my traversals right now?”

 

Checking the Version from the Command Line

When the console is not yet running or when scripting and automation are involved the version can be retrieved directly from the command line using the Gremlin startup script.

 

Two equivalent options are available:

·      gremlin.sh -v

·      gremlin.sh --version

 

$gremlin.sh -v
gremlin 3.8.0
$
$gremlin.sh --version
gremlin 3.8.0

   

Both commands print the version and exit immediately without starting an interactive console session. This approach is particularly useful in:

 

·      Shell scripts and CI/CD pipelines

·      Server provisioning and validation steps

·      Environments with multiple Gremlin installations

 

In effect, this method answers a slightly different question: “Which Gremlin distribution will be launched if this script is executed?”

 

As a best practice:

·      Use Gremlin.version() when already inside the console and validating runtime behavior

·      Use gremlin.sh -v or --version when validating installations, scripts, or deployment environments

 

Maintaining clarity about the exact TinkerPop version in use ensures consistency, prevents subtle bugs, and makes collaboration and troubleshooting significantly more predictable.

 

References

https://tinkerpop.apache.org/javadocs/current/core/org/apache/tinkerpop/gremlin/util/Gremlin.html#version()

 

 

Previous                                                    Next                                                    Home