Skip to content

Conversation

@tirumaraiselvan
Copy link
Contributor

@tirumaraiselvan tirumaraiselvan commented May 25, 2020

Description

Check if there are any event triggers configured before fetching batch of events. This reduces DB load in case event triggers are not used.

Changelog

  • CHANGELOG.md is updated with user-facing content relevant to this PR.

Affected components

  • Server

@netlify
Copy link

netlify bot commented May 25, 2020

Deploy preview for hasura-docs ready!

Built with commit d256b14

https://deploy-preview-4873--hasura-docs.netlify.app

@tirumaraiselvan tirumaraiselvan force-pushed the event-trigger-reduce-fetches branch from 586bc21 to 13fda3d Compare May 25, 2020 09:02
@tirumaraiselvan tirumaraiselvan requested a review from jberryman May 25, 2020 13:36
@tirumaraiselvan tirumaraiselvan force-pushed the event-trigger-reduce-fetches branch from 13fda3d to d256b14 Compare May 25, 2020 13:46
Copy link
Collaborator

@jberryman jberryman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What happens when a trigger is removed but there is a big backlog of events which haven't been processed yet? I guess they will persist in the DB until a new hook is added and then old events will be consumed and discarded?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants