[Bug] When starting Trino with a pulsar plugin using docker, an error of incompatible JDK version appears.

[crossoverJie]

Search before asking

• I searched in the issues and found nothing similar.

Version

Pulsar: 3.0.0
Trino: 368

Minimal reproduce step

Download plugin:

wget https://archive.apache.org/dist/pulsar/pulsar-3.0.0/apache-pulsar-3.0.0-bin.tar.gz

Copy plugin into image:

FROM trinodb/trino:368
COPY pulsar-presto-connector /usr/lib/trino/plugin/pulsar-presto-connector

Start container:

docker build . -t trinodb/trino:368-pulsar-3.0.0
docker run --name trino -d -p 8080:8080 trinodb/trino:368-pulsar-3.0.0

What did you expect to see?

The container started successfully.

What did you see instead?

Anything else?

When I used Trino:latest and Pulsar:3.0.0, got an error of NoclassDefFoundError:

Are you willing to submit a PR?

• I'm willing to submit a PR!

[tisonkun]

Here you come into two issues:

1. Trino 368 is compiled with JDK 11 while our plugin is compiled with JDK 17. You can try to compile the plugin with JDK 11 but it's not promised to work.
2. Trino lastest makes a lot of breaking changes from the one (368) used in our plugin. You can take a look at [sql] Upgrade prestosql to trino #16494 (comment) and [feat][sql] Bump Trino version to 368 and fix Decimal breaking change #20016 for some background.

Basically, please run the Trino worker from the one bundled by Pulsar distro.

Both of them are backed in the root that Pulsar SQL is not under primary maintenance (as well as that Trino pays less attention of compatibility). I suppose anyone who can cover its maintenance a qualified committer.

[crossoverJie]

Thank you for your answer.

1. I previously tried to use the JDK11 compiler plugin, but it failed.
2. You are right, so what we are doing now is compiling the plugin source code and manually building a Trino image to solve it.

Adding a Dockerfile under the pulsar-sql module and building your own image from the source code, is that a better solution?