DanielCarter-stack commented on issue #10636:
URL: https://github.com/apache/seatunnel/issues/10636#issuecomment-4110553757

   <!-- code-pr-reviewer -->
   Thank you for reporting this issue. The analysis confirms a contract 
mismatch between the frontend and backend in SeaTunnel 2.3.13.
   
   The backend (`BaseService.java:463,500,534`) constructs metric keys with 
vertex prefixes like `Sink[0].fake.user_table`, and the test 
(`BaseServiceTableMetricsTest.java:236`) explicitly verifies that original 
table path keys are not included. However, the frontend (`detail.tsx:103,116`) 
still looks up metrics using `row.tablePaths` (e.g., `fake.user_table`), 
causing `Number(undefined)` to render as `NaN`.
   
   The fix requires adding compatibility logic in the frontend to handle 
vertex-prefixed keys or generating both key formats in the backend. Sources: 
`seatunnel-engine/seatunnel-engine-ui/src/views/jobs/detail.tsx:103,116`, 
`seatunnel-engine/seatunnel-engine-server/src/main/java/org/apache/seatunnel/engine/server/rest/service/BaseService.java:463,500,534`


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