You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the migration of the JDBCMetaData step I came into an issue with ComboVar. Trying to dispose a ComboVar component it seems that something strange happens because the disposed component stays connected to the parent composite even if the disposal of the component didn't give any problem
Issue Priority
Priority: 3
Issue Component
Component: Hop Gui
The text was updated successfully, but these errors were encountered:
Apache Hop version?
2.4.0-SNAPSHOT
Java version?
openjdk 11
Operating system
Linux
What happened?
During the migration of the JDBCMetaData step I came into an issue with ComboVar. Trying to dispose a ComboVar component it seems that something strange happens because the disposed component stays connected to the parent composite even if the disposal of the component didn't give any problem
Issue Priority
Priority: 3
Issue Component
Component: Hop Gui
The text was updated successfully, but these errors were encountered: