Some analytics tables have some duplicate rows

オープン
#40 コメント 6 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
25/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
停滞
技術スタック
sql

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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

主要言語
Java
スター
13
フォーク
33
PR マージ指標
30日以内にマージされた PR はありません

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

killbill/killbill-analytics-plugin のほかの issue

killbill/killbill-analytics-plugin の issue をすべて見る

似ている issue

Java の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。