Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Table output - bad performance in transaction-based pipelines #4680

Open
dave-csc opened this issue Dec 9, 2024 · 0 comments
Open

Comments

@dave-csc
Copy link
Contributor

dave-csc commented Dec 9, 2024

Apache Hop version?

2.10.0

Java version?

17.0.2

Operating system

Linux

What happened?

Following discussion #4678, here's a use case:

  1. Set a transform that loads some thousands of rows (i.e. with a Table input from a database, or with a Text file input from a text file)
  2. Link this transform to a Table output, and set it to truncate the table (in any case, not just if a row comes in)

Start the pipeline in the default local run configuration, without transactions enabled: the execution time is somehow reasonable.

Start the pipeline in a run configuration that includes transactions: the pipeline works as expected, and it's correctly rollbacked in case of errors, but the execution times worsen a lot (even 60 times compared to the previous case).

For a data sample, you can try to download the GeoLite2 City CSV Database from Maxmind (you need to signup to Maxmind, the GeoLite2 database is free of charge).

Issue Priority

Priority: 2

Issue Component

Component: Transforms

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant