Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.2.0
-
None
Description
In hop 2.2.0-SNAPSHOT, storing execution information in neo4j enables "Execution lineage" tab in the "execution information" perspective.
When a root workflow is opened, clicking in the "Execution lineage" tab displays nothing and a exception is raised, visible in the console.
In Hop Web it also kills the application causing restart.
No error is raised in case of child wf/pl.
Error in Hop GUI console:
Error in the Hop GUI : Cannot coerce NODE to Path org.neo4j.driver.exceptions.value.Uncoercible: Cannot coerce NODE to Path at org.neo4j.driver.internal.value.ValueAdapter.asPath(ValueAdapter.java:305) at org.apache.hop.neo4j.execution.path.base.NeoExecutionViewerLineageTab.lambda$getLineageToRoot$3(NeoExecutionViewerLineageTab.java:221) at org.neo4j.driver.internal.InternalSession.lambda$transaction$4(InternalSession.java:150) at org.neo4j.driver.internal.retry.ExponentialBackoffRetryLogic.retry(ExponentialBackoffRetryLogic.java:103) at org.neo4j.driver.internal.InternalSession.transaction(InternalSession.java:146) at org.neo4j.driver.internal.InternalSession.readTransaction(InternalSession.java:112) at org.neo4j.driver.internal.InternalSession.readTransaction(InternalSession.java:106) at org.apache.hop.neo4j.execution.path.base.NeoExecutionViewerLineageTab.getLineageToRoot(NeoExecutionViewerLineageTab.java:214) at org.apache.hop.neo4j.execution.path.base.NeoExecutionViewerLineageTab.refresh(NeoExecutionViewerLineageTab.java:141) at org.apache.hop.neo4j.execution.path.base.NeoExecutionViewerLineageTab.lambda$addNeoExecutionPathTab$2(NeoExecutionViewerLineageTab.java:134) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5796) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1529) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1555) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1538) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1316) at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3248) at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:1882) at org.eclipse.swt.custom.CTabFolder.lambda$0(CTabFolder.java:332) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5796) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1529) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:5025) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4477) at org.apache.hop.ui.hopgui.HopGui.open(HopGui.java:464) at org.apache.hop.ui.hopgui.HopGui.main(HopGui.java:351)
Error in Hop Web:
HTTP Status 500 – Internal Server Error Type Exception Report Message Cannot coerce NODE to Path Description The server encountered an unexpected condition that prevented it from fulfilling the request. Exception org.neo4j.driver.exceptions.value.Uncoercible: Cannot coerce NODE to Path org.neo4j.driver.internal.value.ValueAdapter.asPath(ValueAdapter.java:305) org.apache.hop.neo4j.execution.path.base.NeoExecutionViewerLineageTab.lambda$getLineageToRoot$3(NeoExecutionViewerLineageTab.java:221) org.neo4j.driver.internal.InternalSession.lambda$transaction$4(InternalSession.java:150) org.neo4j.driver.internal.retry.ExponentialBackoffRetryLogic.retry(ExponentialBackoffRetryLogic.java:103) org.neo4j.driver.internal.InternalSession.transaction(InternalSession.java:146) org.neo4j.driver.internal.InternalSession.readTransaction(InternalSession.java:112) org.neo4j.driver.internal.InternalSession.readTransaction(InternalSession.java:106) org.apache.hop.neo4j.execution.path.base.NeoExecutionViewerLineageTab.getLineageToRoot(NeoExecutionViewerLineageTab.java:214) org.apache.hop.neo4j.execution.path.base.NeoExecutionViewerLineageTab.refresh(NeoExecutionViewerLineageTab.java:141) org.apache.hop.neo4j.execution.path.base.NeoExecutionViewerLineageTab.lambda$addNeoExecutionPathTab$2(NeoExecutionViewerLineageTab.java:134) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:109) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:687) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:594) org.eclipse.swt.widgets.Display.executeNextEvent(Display.java:1216) org.eclipse.swt.widgets.Display.runPendingMessages(Display.java:1197) org.eclipse.swt.widgets.Display.safeReadAndDispatch(Display.java:1180) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1172) org.eclipse.rap.rwt.application.AbstractEntryPoint.createUI(AbstractEntryPoint.java:69) org.eclipse.rap.rwt.internal.lifecycle.RWTLifeCycle.createUI(RWTLifeCycle.java:177) org.eclipse.rap.rwt.internal.lifecycle.RWTLifeCycle$UIThreadController.run(RWTLifeCycle.java:290) java.base/java.lang.Thread.run(Thread.java:829) org.eclipse.rap.rwt.internal.lifecycle.UIThread.run(UIThread.java:107) Note The full stack trace of the root cause is available in the server logs.