graphql: Remove TransactionBlockFilter.recvAddress and AddressTransactionBlockRelation.RECV #19805
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
amnn
requested review from
wlmyng,
stefan-mysten,
emmazzz and
suiwombat
as code owners
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
8 tasks
wlmyng
approved these changes
Oct 10, 2024
crates/sui-graphql-e2e-tests/tests/stable/transactions/filters/transaction_ids.move
Show resolved
Hide resolved
amnn
force-pushed
the
amnn/gql-rm-sign-addr
branch
from
6c6d653 to
4fb458d
Compare
amnn
force-pushed
the
amnn/gql-rm-rev-addr
branch
from
089096f to
060fec4
Compare
8 tasks
amnn
force-pushed
the
amnn/gql-rm-rev-addr
branch
from
060fec4 to
1c29221
Compare
bmwill
approved these changes
Oct 11, 2024
…tionBlockRelation.RECV ## Description These fields were flagged for deprecation in 1.34 and have been replaced in 1.35 by - `TransactionBlockFilter.affectedAddress` and - `AddressTransactionBlockRelation.AFFECTED` Which offer a similar (but not exactly the same) semantics, but without confusion around the sender address which was often also an implicit recipient of a transaction. ## Test plan ``` sui$ cargo nextest run -p sui-graphql-rpc sui$ cargo nextest run -p sui-graphql-rpc --features staging sui$ cargo nextest run -p sui-graphql-e2e-tests ```
amnn
force-pushed
the
amnn/gql-rm-rev-addr
branch
from
ad8a1cb to
abed6e8
Compare
amnn
added a commit
that referenced
this pull request
Oct 14, 2024
## Description All references to these fields have been removed from readers, so we can stop keeping it up-to-date. Once this change lands, we can also clean these tables from the schema. ## Test plan ``` sui$ cargo nextest run -p sui-indexer ``` ## Stack - #19708 - #19802 - #19803 - #19804 - #19805 --- ## 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): - [x] Indexer: Indexer no longer fills the `tx_sender` and `tx_recipient` tables. - [ ] JSON-RPC: - [ ] GraphQL: - [ ] CLI: - [ ] Rust SDK: - [ ] REST API:
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
These fields were flagged for deprecation in 1.34 and have been replaced in 1.35 by
TransactionBlockFilter.affectedAddressandAddressTransactionBlockRelation.AFFECTEDWhich offer a similar (but not exactly the same) semantics, but without confusion around the sender address which was often also an implicit recipient of a transaction.
Test plan
Stack
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.
TransactionBlockFilter.recvAddressandAddressTransactionBlockRelation.RECVhave been replace byTransactionBlockFilter.affectedAddressandAddressTransactionBlockRelation.AFFECTEDwhich offer similar semantics, but without confusion around the sender address which was also often (but not always) an implicit recipient. Now we don't distinguish between senders and recipients -- we only have senders and "affected" addresses which were touched by the transaction in some way.