Schema for internal transactions #72
There are no files selected for viewing
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,85 @@ | ||
| [ | ||
| { | ||
| "name": "internal_tx_block_number", | ||
| "type": "INT64", | ||
| "mode": "REQUIRED", | ||
| "description": "Block number which included parent of this internal transaction", | ||
| "_comment" : "Can be made available via joins" | ||
| }, | ||
| { | ||
| "name": "internal_tx_block_timestamp", | ||
| "type": "INT64", | ||
| "mode": "REQUIRED", | ||
| "description": "The unix timestamp for when the block was collated" | ||
| }, | ||
| { | ||
| "name": "internal_tx_hash", | ||
| "type": "STRING", | ||
| "mode": "REQUIRED", | ||
| "description": "Hash of the transaction" | ||
| }, | ||
| { | ||
| "name": "internal_tx_from", | ||
| "type": "STRING", | ||
| "mode": "REQUIRED", | ||
| "description": "Address of the sender" | ||
| }, | ||
| { | ||
| "name": "internal_tx_to", | ||
| "type": "STRING", | ||
| "mode": "REQUIRED", | ||
| "description": "Address of the receiver" | ||
| }, | ||
| { | ||
| "name": "internal_tx_value", | ||
| "type": "STRING", | ||
| "mode": "REQUIRED", | ||
| "description": "Value transferred in Wei" | ||
| }, | ||
| { | ||
| "name": "internal_tx_contract_address", | ||
| "type": "STRING", | ||
| "mode": "REQUIRED", | ||
| "description": "Address of the contract which initiated the transaction" | ||
| }, | ||
| { | ||
| "name": "internal_tx_input", | ||
| "type": "STRING", | ||
| "mode": "REQUIRED", | ||
| "description": "The data send along with the transaction" | ||
| }, | ||
| { | ||
| "name": "internal_tx_type", | ||
| "type": "STRING", | ||
| "mode": "REQUIRED", | ||
| "description": "Type of internal transaction: CREATE, SELFDESTRUCT, CALL, CALLCODE, DELEGATECALL, STATICCALL" | ||
| }, | ||
| { | ||
| "name": "internal_tx_gas", | ||
| "type": "STRING", | ||
| "description": "Gas available for the internal transaction" | ||
| }, | ||
| { | ||
| "name": "internal_tx_gas_used", | ||
| "type": "STRING", | ||
| "description": "Gas used by the internal transaction" | ||
| }, | ||
| { | ||
| "name": "internal_tx_trace_id", | ||
|
Member
There was a problem hiding this comment. Should we call it internal_tx_trace_address for consistency with Parity https://wiki.parity.io/JSONRPC-trace-module#trace_block? |
||
| "type": "STRING", | ||
| "mode": "REQUIRED", | ||
| "description": "The level of nesting of an internal transaction" | ||
| }, | ||
| { | ||
| "name": "internal_tx_is_error", | ||
|
Member
There was a problem hiding this comment. Should this column have BOOLEAN type? |
||
| "type": "STRING", | ||
| "mode": "REQUIRED", | ||
| "description": "" | ||
| }, | ||
| { | ||
| "name": "internal_tx_err_code", | ||
| "type": "STRING", | ||
| "mode": "REQUIRED", | ||
| "description": "" | ||
| } | ||
| ] | ||
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The internal_tx_trace_id column can have MODE: REPEATED since it's an array. Then the export job will use json output format for which BigQuery supports REPEATED columns.