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

Move DirectTrinoClient to a non-testing package #24193

Merged

Conversation

ksobolew
Copy link
Contributor

Description

This originted in testing code, but it is being repurposed as a general-purpose utility, so it should not be in a testing package.

The tests for this class are in the testing/trino-tests module in class io.trino.tests.TestLocalQueries, so they are not moved along with it.

Additional context and related issues

Release notes

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

  • It's technically user-visible, but I don't think we're advertising this feature

( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:

## Section
* Fix some things. ({issue}`issuenumber`)

This originted in testing code, but it is being repurposed as a
general-purpose utility, so it should not be in a `testing` package.

The tests for this class are in the `testing/trino-tests` module in
class `io.trino.tests.TestLocalQueries`, so they are not moved along
with it.
@wendigo wendigo merged commit 1364863 into trinodb:master Nov 21, 2024
90 of 92 checks passed
@github-actions github-actions bot added this to the 466 milestone Nov 21, 2024
@ksobolew ksobolew deleted the kudi/direct-trino-client-non-testing branch November 21, 2024 11:38
@martint
Copy link
Member

martint commented Nov 21, 2024

This doesn’t seem to have any uses other than in tests, so it should remain where it was. We don’t do “general purpose utilities” for out-of-tree projects to use.

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