apache / apache/hop

[Bug]: HOP_VERSION returns local version instead of remote execution version

Open
#8,263 1 comment 0 reactions 0 assignees View on GitHub
awaiting triage Hop Server P2
Dominant language
Java
Stars
1.5k
Forks
476
Avg merge
18h 32m
Merged PRs (30d)
216

Description

### Apache Hop version?

2.19.0

### Java version?

21

### Operating system

macOS

### What happened?

I have a local Apache Hop installation (on Mac) running version 2.19, while the actual pipeline execution takes place on a Linux VM running Apache Hop 2.18.1.

In my pipeline, I use a Get Variables action to retrieve the following variables:
- HOP_VERSION
- HOP_PLATFORM_OS

The results are inconsistent:
- HOP_VERSION = 2.19
- HOP_PLATFORM_OS = Linux

Image

I would expect both variables to reflect the environment in which the pipeline is actually being executed.
Since the pipeline is executed on the remote Linux VM running Apache Hop 2.18.1, I would expect:
- HOP_VERSION = 2.18.1
- HOP_PLATFORM_OS = Linux

Instead, HOP_VERSION appears to be taken from the local Apache Hop installation (2.19), while HOP_PLATFORM_OS correctly reflects the remote execution environment.

### Issue Priority

Priority: 2

### Issue Component

Component: Hop Server

Contributor guide

Open the contributing guide

Research direction

Start by tracing how the Get Variables action resolves HOP_VERSION and HOP_PLATFORM_OS when a pipeline runs through Hop Server, comparing local and remote execution contexts. Reproduce the reported setup with a 2.19 client and 2.18.1 remote server; done means HOP_VERSION reports the remote execution version while HOP_PLATFORM_OS remains correct.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, distributed-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.