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-21.2: New SQL Activity page #72052

Conversation

maryliag
Copy link
Contributor

@maryliag maryliag commented Oct 27, 2021

Backport:

Please see individual PRs for details.

/cc @cockroachdb/release

Release justification: Category 4

xinhaoz and others added 6 commits October 27, 2021 11:23
Fixes: cockroachdb#70790

Previously, the selected app was derived from a route param on the
statements page. All other filters are derived from query search
parameters on the page. This commit makes the app name a query search
parameter, as is the case in the transactions page.

Release note: None
New SQL Activity page that includes Sessions, Statement
and Transaction pages.

Partially addresses cockroachdb#66052

Release note (ui change): Session, Statement and Transaction pages
are now grouped inside the new SQL Activity page.
Update ui-components version to include a fix
on scrolling on pages with tooltip

Release note: None
When the user clicks on a tab on the new SQL Activity page
now the search params on the url is updated with the tab
selection.
This commit also create a common function to sync history
so all the pages can use it and remove duplicate code.

Release note: None
When a statement was not found, the return to statements
link was returning to the SQL Activity page without the
Statement tab selected.
This commit adds the right tab to the return option.

Release note: None
Previously, when changing tabs on SQL Activity page the history
would be replaced, this commits change to push to history, meaning
when the user clicks Back on the browser it will return for the
previous tab.

Release note: None
@maryliag maryliag added the do-not-merge bors won't merge a PR with this label. label Oct 27, 2021
@maryliag maryliag requested a review from a team October 27, 2021 19:23
@blathers-crl
Copy link

blathers-crl bot commented Oct 27, 2021

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?

@cockroach-teamcity
Copy link
Member

This change is Reviewable

Release note (<category, see below>): <what> <show> <why>
Copy link
Contributor

@matthewtodd matthewtodd left a comment

Choose a reason for hiding this comment

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

Checked out the branch to run locally, :lgtm:

Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained

A recent commit changed the default value of filter
to be an empty string, but we do have transactions that have
no associated app names to it, so All and empty string
should be treated as different cases. This commit reverse
that changes and use All

Release note (bug fix): Show All statements when filter All is
selected and not only the ones with empty string
@maryliag maryliag removed the do-not-merge bors won't merge a PR with this label. label Nov 15, 2021
@maryliag maryliag merged commit aac9181 into cockroachdb:release-21.2 Nov 15, 2021
@maryliag maryliag deleted the backport21.2-71175-71325-71522-71762-71845-71938 branch November 15, 2021 20:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants