Not sure if this is a bug or my not knowing what I'm doing, but I can't seem to get any database drivers to show up/work.
I installed Hop in microk8s using helm:
helm repo add apache-hop https://hop.apache.org
helm repo update
helm show values apache-hop/hop > values.yaml
k namespace create hop
# created PVC via rook-ceph
nano values.yml #set persistence.enabled=true and set existingClaim to a PVC
k create secret generic -n hop hop-deployment-server --from-literal=pass=XYZ123
helm install hop-deployment apache-hop/hop -f values.yaml -n hop
After adding an ingressroute via Traefik I got to Hop just fine. However, when adding a relational database connection, every "Connection Type" says "no driver installed". For example I tried MSSQL both normal and native and got these errors:
MS SQL Server (Native): driver class 'net.sourceforge.jtds.jdbc.driver' could not be found
MS SQL Server: driver class 'net.sourceforge.jtds.jdbc.driver' could not be found
But there seemed to be MSSQL drivers for jdbc installed:
Edit: I believe I should have looked at the 'web' pod in which case the issue is that the docker image is missing the jdbc directory per existing issue https://github.com/apache/hop/issues/4013
I was guessing there should be an ENV variable by default in the values.yaml file, I tried defining server.image.env with HOP_SHARED_JDBC_FOLDERS set to either "/opt/hop/lib/jdbc" or "/opt/hop/lib/jdbc,/opt/hop/plugins/databases" and then running helm upgrade but that didn't seem to help despite it showing up on the running process:
hop-deployment-server-56984bcd8d-t6c26:~$ ps aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
hop 1 0.0 0.0 2356 1780 ? Ss 21:37 0:00 /bin/bash /opt/hop/run.sh
hop 7 0.0 0.0 2448 1876 ? S 21:37 0:00 /bin/bash /opt/hop/load-and-execute.sh
hop 12 0.0 0.0 2348 1748 ? S 21:37 0:00 bash /opt/hop/hop-server.sh --level=Basic /tmp/hop-server.xml
hop 13 0.0 0.0 1616 4 ? S 21:37 0:00 tee /opt/hop/hop.err.log
hop 37 8.4 5.9 10141556 977372 ? Sl 21:37 0:12 java -XX:+AggressiveHeap -DHOP_AUDIT_FOLDER=./audit **-DHOP_SHARED_JDBC_FOLDERS=/opt/hop/lib/jdbc** -DHOP_PLATFORM_RUNTIME=Server -DHOP_AUTO_CREATE_CONFIG=Y -DHOP_PLATFORM_OS=Linux -Djava.library.path= -classpath lib/core/*:lib/beam/*:lib/swt/linux/x86_64/* org.apache.hop.www.HopServer --level=Basic /tmp/hop-server.xml
hop 70 0.0 0.0 2640 2308 pts/0 Ss 21:40 0:00 /bin/bash
hop 77 0.0 0.0 2524 1736 pts/0 R+ 21:40 0:00 ps aux
Issue Priority
Priority: 2
Issue Component
Component: Containers, Component: Database, Component: Documentation, Component: Hop Config, Component: Hop Server
Apache Hop version?
2.9.0 (helm list shows 2.5.0 but I see hop-core-2.9.0.jar in /opt/hop/lib/core)
Java version?
11.0.23
Operating system
Linux
What happened?
Edit: I believe this is a duplicate of https://github.com/apache/hop/issues/4013
Not sure if this is a bug or my not knowing what I'm doing, but I can't seem to get any database drivers to show up/work.
I installed Hop in microk8s using helm:
After adding an ingressroute via Traefik I got to Hop just fine. However, when adding a relational database connection, every "Connection Type" says "no driver installed". For example I tried MSSQL both normal and native and got these errors:
MS SQL Server (Native): driver class 'net.sourceforge.jtds.jdbc.driver' could not be found MS SQL Server: driver class 'net.sourceforge.jtds.jdbc.driver' could not be found
But there seemed to be MSSQL drivers for jdbc installed: Edit: I believe I should have looked at the 'web' pod in which case the issue is that the docker image is missing the jdbc directory per existing issue https://github.com/apache/hop/issues/4013
hop-deployment-server-6cc467cb58-tnhzc:/opt/hop$ find . -name "mssql"
hop-deployment-server-56984bcd8d-t6c26:~$ ls /opt/hop/lib/jdbc
hop-deployment-server-56984bcd8d-t6c26:~$ ls /opt/hop/plugins/databases/
I was guessing there should be an ENV variable by default in the values.yaml file, I tried defining server.image.env with HOP_SHARED_JDBC_FOLDERS set to either "/opt/hop/lib/jdbc" or "/opt/hop/lib/jdbc,/opt/hop/plugins/databases" and then running helm upgrade but that didn't seem to help despite it showing up on the running process:
hop-deployment-server-56984bcd8d-t6c26:~$ ps aux
Issue Priority
Priority: 2
Issue Component
Component: Containers, Component: Database, Component: Documentation, Component: Hop Config, Component: Hop Server