vbhanuchander-lang commented on issue #4750:
URL: https://github.com/apache/hop/issues/4750#issuecomment-5446511306
This looks fixed already — it can be closed.
The stack trace in the screenshot is:
```
Unable to open pipeline: Cannot invoke
"org.apache.hop.pipeline.transform.TransformMeta.getName()"
because "nextTransform" is null
at
org.apache.hop.pipeline.transforms.kafka.consumer.KafkaConsumerInputMeta.getFields(KafkaConsumerInputMeta.java:444)
at
org.apache.hop.pipeline.transform.BaseTransformMeta.getFields(BaseTransformMeta.java:328)
at
org.apache.hop.pipeline.PipelineMeta.getThisTransformFields(PipelineMeta.java:1413)
```
`KafkaConsumerInputMeta.getFields()` checks whether it is being called down
the error path by comparing the error target's name against `nextTransform`:
```java
if (transformErrorMeta != null
&& transformErrorMeta.getTargetTransform() != null
&&
transformErrorMeta.getTargetTransform().getName().equals(nextTransform.getName()))
{
```
`PipelineMeta.getThisTransformFields()` legitimately passes `nextTransform
== null`, so with error handling configured (making `transformErrorMeta`
non-null) the third condition dereferenced null and the pipeline could not be
opened at all — which matches the report exactly.
A `nextTransform != null` guard was added to that condition in 52efe7a40b
("issue #7519 : Kafka Consumer stop when idle", #7524, 2026-07-15), where it
came along incidentally rather than as the point of the change — which is
presumably why this issue was never linked to it.
Checked the file at each release tag to confirm where the fix lands:
| tag | guarded |
|---|---|
| 2.11.0-rc1 (the reported version) | no |
| 2.13.0-rc1 | no |
| 2.15.0-rc1 | no |
| 2.17.0-rc1 | no |
| 2.18.0-rc1 | no |
| 2.19.0-rc1 | **yes** |
So the NPE is reproducible on everything up to and including 2.18.0 and is
gone from 2.19.0 onwards. @petertsneg, upgrading to 2.19.0 or later should
resolve it.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
