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

Remove non-null restriction for QueryHistory #381

Merged
merged 1 commit into from
Jun 6, 2024

Conversation

oneonestar
Copy link
Member

Description

Both userName and source in QueryHistory are nullable.

userName (ie. X-Trino-User) is optional in request. If not supplied, the session user is automatically determined via user mapping by coordinator. Trino-gateway won't be able to know the user determined by user mapping.

source is optional in Trino:
https://github.com/trinodb/trino/blob/edd5d5bec766e90053e7c28ff9c9dc254790fdb0/core/trino-spi/src/main/java/io/trino/spi/eventlistener/QueryContext.java#L45

Release notes

(x) This is not user-visible or is docs only, and no release notes are required.

@cla-bot cla-bot bot added the cla-signed label Jun 6, 2024
@ebyhr ebyhr merged commit d45c64f into trinodb:main Jun 6, 2024
2 checks passed
@github-actions github-actions bot added this to the 10 milestone Jun 6, 2024
@oneonestar oneonestar deleted the star/fix_history_record branch June 6, 2024 11:43
@mosabua
Copy link
Member

mosabua commented Jul 16, 2024

I added a release notes entry for this since I think it is kinda user facing..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants