You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to run the DAGs for the first time, we are unable to see where the "logs_by_topic" table is getting populated for our log event.
WITH parsed_logs AS
(SELECT
logs.block_timestamp AS block_timestamp
,logs.block_number AS block_number
,logs.transaction_hash AS transaction_hash
,logs.log_index AS log_index
,logs.address AS contract_address
,`<project-id>-internal.ethereum_<entity>_blockchain_etl.parse_<smart-contract>_event_<event-name>`(logs.data, logs.topics) AS parsed
FROM `<project-id>-internal.crypto_ethereum_partitioned.logs_by_topic_0x8c5` AS logs
WHERE
address in (lower('<address>'))
AND topics[SAFE_OFFSET(0)] = '<topic>'
-- live
)
SELECT
block_timestamp
,block_number
,transaction_hash
,log_index
,contract_address
,parsed.owner AS `owner`
,parsed.spender AS `spender`
,parsed.value AS `value`
FROM parsed_logs
WHERE parsed IS NOT NULL
The section in question is this guy:
...
FROM `<project-id>-internal.crypto_ethereum_partitioned.logs_by_topic_0x8c5` AS logs
...
We know that this is part of the "LIVE" realtime update section, but what is actually populating the table with the topics that we specify? Is this being done in a different repo?
The text was updated successfully, but these errors were encountered:
Are both of these repos setup enough where we can plug and play our own implementation? We plan on contributing to the dataset ecosystem, but need a custom implementation for some edge cases.
Hi all,
When attempting to run the DAGs for the first time, we are unable to see where the "logs_by_topic" table is getting populated for our log event.
The section in question is this guy:
We know that this is part of the "LIVE" realtime update section, but what is actually populating the table with the topics that we specify? Is this being done in a different repo?
The text was updated successfully, but these errors were encountered: