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
In the course of investigating #3038, it became clear that one cause of missing transaction IDs in fct_payments_rides is that there are micropayments with no associated device transactions. As an analytics engineer, I want to ask Littlepay (the data vendor) how these rows should be interpreted so that I can correctly handle them in downstream models.
AC:
Reach out to Littlepay about these rows and ask whether they should be dropped or whether they can send us new data with the missing transactions
Query to identify affected rows:
WITH mapping AS (
SELECTmp.participant_id,
littlepay_transaction_id,
micropayment_id
FROM`cal-itp-data-infra.staging.stg_littlepay__micropayment_device_transactions`LEFT JOIN`cal-itp-data-infra-staging.charlie_staging.stg_littlepay__micropayments` mp USING (micropayment_id)
),
device_transactions AS (
SELECT
littlepay_transaction_id,
FROM`cal-itp-data-infra.staging.stg_littlepay__device_transactions`
),
compare AS (
SELECTdevice_transactions.littlepay_transaction_idIS NOT NULLAS has_device_transaction,
mapping.littlepay_transaction_id,
mapping.micropayment_id,
mapping.participant_idFROM mapping
LEFT JOIN device_transactions USING(littlepay_transaction_id)
)
SELECT*FROM compare
WHERE NOT has_device_transaction
The text was updated successfully, but these errors were encountered:
In the course of investigating #3038, it became clear that one cause of missing transaction IDs in
fct_payments_rides
is that there are micropayments with no associated device transactions. As an analytics engineer, I want to ask Littlepay (the data vendor) how these rows should be interpreted so that I can correctly handle them in downstream models.AC:
Query to identify affected rows:
The text was updated successfully, but these errors were encountered: