Weird Issue with DB Table Selector Node in 5.5.3 ( Node Missing.. But, Available in Node Repository )

KNIME Analytics Platform
1

My workflows is showing as “DB Table Selector” is missing… But, I can see in node repository.. Check following extension..

It is asking me to install “Knime Database”.. when I try to install. It is throwing error as “Extension already available”…. Bit confused.. Circular dependency issue..

Screenshot2026_02_04_190317
Screenshot2026_02_04_190317915×416 49.6 KB

2

Hello @exploredata547,

and what happens when you drag a DB Table Repository node from Node Repository? Do you see it normally or as shown in picture?

Br,
Ivan

3

Yes, it is normally shown…

This workflow is shared by one of my colleagues. After importing this workflow… It is asking me to install extension.. when I try to install “extension”… it is saying.. extension already exists..

4

Hello @exploredata547,

is it every DB node or only DB Table Selector? What comes to my mind is different KNIME version between you and your colleague.

Br,
Ivan

5

It’s only for this node.. Yes.. I am using 5.5.3 and my colleague is using 5.9.0

If version is the problem… Then do we have to update our workflows everytime there is a new release ? It’s difficult we have 1000’s of workflows..

6

No, you don’t have to update workflows to newer versions (because we offer backwards-compatibility). In fact, we have thousands of old test workflows that we do specifically not update.

But what does not work is “forwards-compatibility” (this does not exist):

  • Creating a workflow in 5.5.3 and opening and executing it in 5.9.0 works (otherwise we broke backwards-compatibility).
  • Creating a workflow in 5.9.0 and opening it in 5.5.3 does not work in general. This is why there is a “future version” warning (I think you can check a box to disable this warning). It can work, if you happen to use only features that were available in 5.5.3, but it is not guaranteed.
7

That means… developers always has to maintain multiple knime versions in their system and also need to track which workflow they built, which version…

I agree.. you are adding that prompt as a warning..

maintaining multiple knime versions will be a problem right ? both from infosec perspective when there is critical security issue and also maintenance purpose….

In my opinion, this will be problem, when we want to upgrade !!

Not sure, how other teams are handling.. is there any best practices while distributing knime internally.

8

Have a central way of distributing and keep your own sample workflows at the version number you have rolled out internally. Try to follow closely the KNIME release cycle so you get the latest updates and bug fixes. I think this is basically the case with every software.

1 Like