Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release-23.1: sql: fix activity update job missing stmts #109479

Merged
merged 1 commit into from Aug 25, 2023

Conversation

blathers-crl[bot]
Copy link

@blathers-crl blathers-crl bot commented Aug 24, 2023

Backport 1/1 commits from #109424 on behalf of @j82w.

/cc @cockroachdb/release


Problem:
The UI was missing query text and details when looking at SQL activity transaction page when there was more than 500 statments or transactions. This is because the activity update job only included the top N statements for each table. It is possible that a transaction is in the top list but none of it's individual statements are.

Solution:
The activity update job now includes all statements for a transaction that is in the transaction_acitivity table. This was done by adding another query after the initial update to add any missing statements.

Fixes: #109200

Release note (sql change): Fixes issue where the UI was missing query text and details when looking at SQL activity transaction page if there was more than 500 transaction or statements. The statement_activity table now includes all statements for a transaction that are in the transaction_activity table.


Release justification: bug fix

Problem:
The UI was missing query text and details when looking at SQL activity
transaction page when there was more than 500 statments or transactions.
This is because the activity update job only included the top N
statements for each table. It is possible that a transaction is in the
top list but none of it's individual statements are.

Solution:
The activity update job now includes all statements for a transaction
that is in the transaction_acitivity table. This was done by adding
another query after the initial update to add any missing statements.

Fixes: #109200

Release note (sql change): Fixes issue where the UI was missing query
text and details when looking at SQL activity transaction page if there
was more than 500 transaction or statements. The statement_activity
table now includes all statements for a transaction that are in the
transaction_activity table.
@blathers-crl blathers-crl bot requested a review from a team as a code owner August 24, 2023 23:24
@blathers-crl blathers-crl bot requested review from mgartner and removed request for a team August 24, 2023 23:24
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-23.1-109424 branch from d850c07 to 4b14133 Compare August 24, 2023 23:24
@blathers-crl blathers-crl bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels Aug 24, 2023
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-23.1-109424 branch from abf305f to bbcf4f4 Compare August 24, 2023 23:24
@blathers-crl
Copy link
Author

blathers-crl bot commented Aug 24, 2023

Thanks for opening a backport.

Please check the backport criteria before merging:

  • Patches should only be created for serious issues or test-only changes.
  • Patches should not break backwards-compatibility.
  • Patches should change as little code as possible.
  • Patches should not change on-disk formats or node communication protocols.
  • Patches should not add new functionality.
  • Patches must not add, edit, or otherwise modify cluster versions; or add version gates.
If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.
  • There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
  • The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
  • New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters.
  • The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

  • What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
  • Will this work in a cluster of mixed patch versions? Did we test that?
  • If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

@blathers-crl blathers-crl bot added the backport Label PR's that are backports to older release branches label Aug 24, 2023
@cockroach-teamcity
Copy link
Member

This change is Reviewable

Copy link
Contributor

@maryliag maryliag left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:lgtm:

Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained (waiting on @cucaroach, @gtr, and @mgartner)

@j82w j82w merged commit 0338cd2 into release-23.1 Aug 25, 2023
6 checks passed
@j82w j82w deleted the blathers/backport-release-23.1-109424 branch August 25, 2023 17:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport Label PR's that are backports to older release branches blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants