Some analytics tables have some duplicate rows

Aperta
#40 6 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
sql

Direzione di ricerca

Start by running the supplied duplicate-count query against the analytics tables and compare the affected payment tables with the unaffected ones. Then investigate how refreshing an associated account changes those rows. Done means the reported duplicate rows no longer occur; the issue does not identify files or tests to guide that investigation.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Some analytics have multiple rows for the same source row when there should be only one row in the analytics table. Refreshing the associated account in analytics corrects this problem for the affected accounts.

Tablename Repeated row count
analytics_payment_auths 10
analytics_payment_captures 3
analytics_payment_refunds 3
analytics_accounts 0
analytics_bundles 0
analytics_invoice_adjustments 0
analytics_invoice_credits 0
analytics_invoice_item_adjustments 0
analytics_invoice_items 0
analytics_invoices 0
analytics_payment_credits 0
analytics_payment_chargebacks 0
analytics_payment_purchases 0
analytics_payment_voids 0

select 'analytics_accounts' as table_name, ifnull(count(1),0) from (
select account_record_id from analytics_accounts a group by 1 having count(1)>1 ) b
UNION
select 'analytics_bundles' as table_name, count(1) from (
select bundle_record_id from analytics_bundles a group by 1 having count(1)>1 ) b
UNION
select 'analytics_invoice_adjustments' as table_name, ifnull(count(1),0) from (
select invoice_item_record_id from analytics_invoice_adjustments a group by 1 having count(1)>1 ) b
UNION
select 'analytics_invoice_credits' as table_name, ifnull(count(1),0) from (
select invoice_item_record_id from analytics_invoice_credits a group by 1 having count(1)>1 ) b
UNION
select 'analytics_invoice_item_adjustments' as table_name, ifnull(count(1),0) from (
select invoice_item_record_id from analytics_invoice_item_adjustments a group by 1 having count(1)>1 ) b
UNION
select 'analytics_invoice_items' as table_name, ifnull(count(1),0) from (
select invoice_item_record_id from analytics_invoice_items a group by 1 having count(1)>1 ) b
UNION
select 'analytics_invoices' as table_name, ifnull(count(1),0) from (
select invoice_record_id from analytics_invoices a group by 1 having count(1)>1 ) b
UNION
select 'analytics_payment_auths' as table_name, ifnull(count(1),0) from (
select payment_transaction_id from analytics_payment_auths a group by 1 having count(1)>1 ) b
UNION
select 'analytics_payment_captures' as table_name, count(1) from (
select payment_transaction_id from analytics_payment_captures a group by 1 having count(1)>1 ) b
UNION
select 'analytics_payment_credits' as table_name, count(1) from (
select payment_transaction_id from analytics_payment_credits a group by 1 having count(1)>1 ) b
UNION
select 'analytics_payment_chargebacks' as table_name, count(1) from (
select payment_transaction_id from analytics_payment_chargebacks a group by 1 having count(1)>1 ) b
UNION
select 'analytics_payment_purchases' as table_name, count(1) from (
select payment_transaction_id from analytics_payment_purchases a group by 1 having count(1)>1 ) b
UNION
select 'analytics_payment_refunds' as table_name, count(1) from (
select payment_transaction_id from analytics_payment_refunds a group by 1 having count(1)>1 ) b
UNION
select 'analytics_payment_voids' as table_name, count(1) from (
select payment_transaction_id from analytics_payment_voids a group by 1 having count(1)>1 ) b

Lingua principale
Java
Stelle
13
Fork
33
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di killbill/killbill-analytics-plugin

Tutte le issue di killbill/killbill-analytics-plugin

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.