Re: [I] [Feature Request]: Persistence and Display of Local Execution History in Hop GUI (hop)

2026-08-31 Thread via GitHub


nadment commented on issue #6904:
URL: https://github.com/apache/hop/issues/6904#issuecomment-5483137367

   For now, I'm trying to improve it—I use it almost every day at work—but the 
idea is really to integrate it into Hop.


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



Re: [I] [Feature Request]: Persistence and Display of Local Execution History in Hop GUI (hop)

2026-08-31 Thread via GitHub


CarlosJuncher03 commented on issue #6904:
URL: https://github.com/apache/hop/issues/6904#issuecomment-5482826107

   Is that right? Can you configure it so it can be installed via the 
marketplace? I believe that would add a lot of value. @nadment 


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



Re: [I] [Feature Request]: Persistence and Display of Local Execution History in Hop GUI (hop)

2026-08-31 Thread via GitHub


CarlosJuncher03 commented on issue #6904:
URL: https://github.com/apache/hop/issues/6904#issuecomment-5478423775

   I'll give it a try — that's exactly it. Thanks.


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



Re: [I] [Feature Request]: Persistence and Display of Local Execution History in Hop GUI (hop)

2026-08-29 Thread via GitHub


nadment commented on issue #6904:
URL: https://github.com/apache/hop/issues/6904#issuecomment-5464832661

   You can try my experimental plugin that displays execution history. It 
allows you to easily see execution time trends, regressions, and failures over 
time (for version >=2.19.0 only): 
https://github.com/nadment/hop-execution-history


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



Re: [I] [Feature Request]: Persistence and Display of Local Execution History in Hop GUI (hop)

2026-03-31 Thread via GitHub


CarlosJuncher03 commented on issue #6904:
URL: https://github.com/apache/hop/issues/6904#issuecomment-4163079219

   I improved the description of the activity idea. It was confusing before, 
sorry, sometimes I use AI to convey my idea and I didn't validate it correctly 
this time.


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



Re: [I] [Feature Request]: Persistence and Display of Local Execution History in Hop GUI (hop)

2026-03-30 Thread via GitHub


CarlosJuncher03 commented on issue #6904:
URL: https://github.com/apache/hop/issues/6904#issuecomment-4157814402

   I completely agree, and the fact that Hop already has the Execution 
Information Engine for persistence is a huge advantage. It’s a solid foundation.
   
   My suggestion is more about the Developer Experience (DX) during the tuning 
phase. While external persistence is perfect for auditing, having a quick way 
to 'read back' and compare the last few runs directly within the GUI would be a 
game-changer.
   
   When we are hunting for bottlenecks or testing small logic adjustments, 
switching to an external SQL editor or Grafana to check if we gained 5 or 10 
seconds breaks the development flow. If the GUI could leverage that existing 
persisted data to show a simple 'Current vs. Previous' delta, it would turn Hop 
into an even more powerful IDE for performance optimization.
   
   It’s less about storing the data and more about making it actionable for the 
developer in real-time.


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



Re: [I] [Feature Request]: Persistence and Display of Local Execution History in Hop GUI (hop)

2026-03-30 Thread via GitHub


CarlosJuncher03 commented on issue #6904:
URL: https://github.com/apache/hop/issues/6904#issuecomment-4157824251

   The idea I'm discussing here addresses problems I encounter daily in my 
development work, and I see this as a major step forward for Apache Hop. It's 
already a magnificent and complete tool. What I really see are these 
improvements that would make its daily use easier.


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



Re: [I] [Feature Request]: Persistence and Display of Local Execution History in Hop GUI (hop)

2026-03-30 Thread via GitHub


hansva commented on issue #6904:
URL: https://github.com/apache/hop/issues/6904#issuecomment-4157255474

   If you configure an execution information location, it is persisted


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