You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit eb095f3
Browse filesBrowse the repository at this point in the historyBrowse files
chore: Add Trino Offline Store in the contrib folder (#2517)
* Add Trino Offline Store in the contrib folder
Signed-off-by: Matt Delacour <[email protected]>
* Assess comments
Signed-off-by: Matt Delacour <[email protected]>
* Assess comments of Tomas
Signed-off-by: Matt Delacour <[email protected]>
Co-authored-by: Matt Delacour <[email protected]>
This is a walkthrough to talk about how we can test the trino plugin locally
3
+
4
+
## Start Trino in a docker container
5
+
```sh
6
+
make start-trino-locally
7
+
```
8
+
9
+
Normally this should start a docker container named `trino` listening on the port 8080.
10
+
You can see the docker command executed by looking at the `Makefile` at the root.
11
+
12
+
You can look at the queries being executed during the tests with the [local cluster UI](http://0.0.0.0:8080/ui/#) running.
13
+
This can be helpful to debug the Trino plugin while executing tests.
14
+
15
+
## Run the universal suites locally
16
+
```sh
17
+
make test-trino-plugin-locally
18
+
```
19
+
20
+
## Kill the local Trino container
21
+
```sh
22
+
make kill-trino-locally
23
+
```
24
+
25
+
You can always look at the running containers and kill the ones you don't need anymore
0 commit comments