mattcasters opened a new pull request, #8282:
URL: https://github.com/apache/hop/pull/8282

   Fixes the Neo4j execution-information path that produced the generic warning 
in discussion #8204 (Hop 2.19 + Neo4j v5): history/logs/metrics worked, but 
data, lineage, and nested error highlighting did not.
   
   ## What changed
   
   - **Surface the real error.** The local pipeline timer no longer swallows 
the exception behind `unable to register execution info (data and state)`. 
Sample-row registration and state updates run independently so a bad data type 
cannot skip metrics.
   - **Make `registerData` Neo4j-safe.** Unsupported property types (mixed 
lists, maps, `Integer`, blobs, …) are coerced to values the driver accepts, so 
one sampled field no longer rolls back the whole data write.
   - **Neo4j 5 lineage/error Cypher.** Directed `[:EXECUTES*]` from a bound 
start node, `child.failed = true`, and a leaf predicate (`NOT 
(child)-[:EXECUTES]->()`). Path-tab failures show an error dialog instead of an 
empty tree.
   - **Execution viewer.** Pipeline drill-down loads the child execution state. 
Failed transforms get a red border from stored error metrics.
   - **Hardening.** MERGE metrics instead of CREATE duplicates; cache eviction 
and `unBuffer()`; null-safe close; index drop requires a name; constraint/index 
actions fail on Cypher errors; importer accepts 2025.x/2026.x CLI; `Number` CSV 
type is `double`.
   
   ## Tests
   
   - Unit tests for property coercion, cache eviction, path Cypher shape, and 
index DDL
   - `ErrorPathCypherIT` against Neo4j 5.26, including the execution-info schema
   
   Fixes #8280


-- 
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]

Reply via email to