-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Make Flow topology safe on duplicate for JDBC #4825
Labels
area/backend
Needs backend code changes
bug
Something isn't working
kind/customer-request
Requested by one or more customers
kind/quick-win
Seems to be quick to do
Comments
tchiotludo
added
bug
Something isn't working
area/backend
Needs backend code changes
kind/quick-win
Seems to be quick to do
kind/customer-request
Requested by one or more customers
labels
Sep 4, 2024
loicmathieu
added a commit
that referenced
this issue
Sep 11, 2024
We usually always include `onDuplicateKeyUpdate()` when we save an object in the database, it was missing for batch insert of flow topologies. Fixes #4825
loicmathieu
added a commit
that referenced
this issue
Sep 11, 2024
We usually always include `onDuplicateKeyUpdate()` when we save an object in the database, it was missing for batch insert of flow topologies. Fixes #4825
loicmathieu
added a commit
that referenced
this issue
Sep 11, 2024
We usually always include `onDuplicateKeyUpdate()` when we save an object in the database, it was missing for batch insert of flow topologies. Fixes #4825
fhussonnois
pushed a commit
that referenced
this issue
Sep 12, 2024
We usually always include `onDuplicateKeyUpdate()` when we save an object in the database, it was missing for batch insert of flow topologies. Fixes #4825
Not working on PG14 |
Skraye
added a commit
that referenced
this issue
Sep 23, 2024
Skraye
added a commit
that referenced
this issue
Sep 23, 2024
Skraye
added a commit
that referenced
this issue
Sep 23, 2024
The fix will not prevent the executor to crash if we have another error, please capture the error and make the executor only log it as |
loicmathieu
added a commit
that referenced
this issue
Sep 24, 2024
loicmathieu
added a commit
that referenced
this issue
Sep 24, 2024
loicmathieu
added a commit
that referenced
this issue
Sep 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/backend
Needs backend code changes
bug
Something isn't working
kind/customer-request
Requested by one or more customers
kind/quick-win
Seems to be quick to do
some flow topology insert can crash the application :
that lead to
We should:
REPLACE INTO
insteadINSERT INTO
if we are not sure at 100%, it will don't change the data behindThe text was updated successfully, but these errors were encountered: