graphql-engine/teardown.yaml at fec3707e2ea26ab85ca49d66aa175d664ddf78f1 - graphql-engine - gitea: Gitea Service

hasura/graphql-engine

mirror of https://github.com/hasura/graphql-engine.git synced 2024-12-22 06:51:32 +03:00

Brandon Simmons 9c9bb43a53 server: restore proper batching behavior in event trigger processing (#1237 )

This essentially restores the original code from c425b554b8
(https://github.com/hasura/graphql-engine/pull/4013). Prior to this
commit we would slurp messages as fast as possible from the database
(one thing c425b55 fixed).

Another thing broken as a consequence of the same logic was the
removeEventFromLockedEvents logic which unlocks in-flight events
(breaking at-least-once delivery)

Some archeology, post-c425b55:

- cc8e2ccc erroneously attempted to refactor using `bracket`, resulting
  in the same slurp-all-events behavior (since we don't ever wait for
  processEvent to complete)
- at some point event processing within a batch is made serial, this
  reported as a bug. See: https://github.com/hasura/graphql-engine/issues/5189
- in 0ef52292b5 (which I approved...) an `async` is added, again
  causing the same issue...

GitOrigin-RevId: d8cbaab385267a4c3f1f173e268a385265980fb1

2021-04-29 04:02:05 +00:00

10 lines

148 B

YAML

Raw Blame History

 type: bulk
 args:
 - type: delete_event_trigger
   args:
     name: flood_all
 - type: run_sql
   args:
     sql: |
       drop table hge_tests.test_flood;