I think I might have misunderstood your original post. Just to clarify, the error you see is just in the Eclipse UI log only - it’s not preventing you from executing the node and getting results at the output port. Is that correct?
If so, you can safely ignore the error (and for peace of mind, close the error log view )
Here’s a thread with a similar discussion. Long story short - the “error” sounds much worse than it actually is.
)