[GraphQL/Events] Disable filtering on both event_type and emitting_module

[wlmyng]

Description

From GraphQL performance benchmarks, we observed that events queries filtered on both event_type and emitting_module frequently time out. Some approaches were explored to support this, but ultimately we will do away with this combination for the time being.

The new paginated events query consists of a few roundtrips, first to collect a list of tx_sequence_number and event_sequence_number, and then a subsequent query composed of a series of UNION ALLs to leverage the index on the events table.

If filters are not specified for event_type, emitting_module, or sender, then we can query the events table directly.

Test plan

1. event_connection/combo_filter_error.move - tests that combining event_type and emitting_module will error
2. event_connection/no_filter.move - tests cursor pagination on an events query without any filters works as expected
3. event_connection/tx_digest.move - tests that when cursors and a filter on digest are used in tandem, that results are empty if they do not point to the same tx_sequence_number, and default to the cursor's event_sequence_number exclusive as the starting or ending point
4. event_connection/type_filter.move - tests event_type filter works
5. event_connection/type_param_filter.move - tests event_type with type param instantiation works

---

Release notes

Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.

For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.

• Protocol:
• Nodes (Validators and Full nodes):
• Indexer:
• JSON-RPC:
• GraphQL: Events queries no longer support filtering on both eventType and emittingModule
• CLI:
• Rust SDK:
• REST API:

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sui-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 28, 2024 4:35pm

3 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
multisig-toolkit	⬜️ Ignored (Inspect)	Visit Preview		Aug 28, 2024 4:35pm
sui-kiosk	⬜️ Ignored (Inspect)	Visit Preview		Aug 28, 2024 4:35pm
sui-typescript-docs	⬜️ Ignored (Inspect)	Visit Preview		Aug 28, 2024 4:35pm

[emmazzz]

By the way we'll need to apply the schema changes (removal of some columns in event tables that won't be used anymore in graphql) in this commit as well before merging this PR into main, as the backfills are done with these event columns removed.

[amnn]

Heads up @wlmyng and @emmazzz -- I took the liberty of simplifying add_bounds. Seeing as we aren't supporting compound queries, we don't need to use CTEs, which significantly simplifies the query. This also means we can get rid of the support for RawQuery::with.

I also took the opportunity to clean up some other things that were maybe a bit problematic:

• tx_hi - 1 -- there's a small underflow risk which we can avoid there.
• Using u64::MAX as the default event sequence number upperbound also carries an overflow risk, as Postgres uses signed integers, so I've avoided that too.