Download the Java JDBC *.jar library
Download the driver below and install it on the Java tool of your choice:
| View file | ||
|---|---|---|
|
Download the driver above and install it in your favorited Java tool for reporting & analytics.
JDBC connect
...
Then configure a connection to the SQL Cloud database with the following configuration:
Driver class: expert.marketplace.sqlc.jira.cloud.Driver
URL: jdbc:jira-cloud:<port> (any available local port)
Username: Must match the name of the Jira instance (https:<instance>.atlassian.net)
Password: Must match the password on SQL Cloud - Query Server page (https://<instance>.atlassian.net/plugins/servlet/ac/expert.marketplace.jira.cloud.sql/sqlc-server)
Prerequisites
Minimum Java version 1.8
For Java +17 these JVM parameters must be added to the command line:
--add-opens java.base/java.lang=ALL-UNNAMED
--add-opens java.base/java.math=ALL-UNNAMED
--add-opens java.base/java.util=ALL-UNNAMED
--add-opens java.base/java.util.concurrent=ALL-UNNAMED
--add-opens java.base/java.net=ALL-UNNAMED
--add-opens java.base/java.text=ALL-UNNAMED
How it works
SQL Cloud is a 100% JavaScript database. Therefore a browser page is always required to run it.
As it is an app for Jira then the user must be logged in Jira to view the page and connect to.
This may look weird, but the JDBC Driver cares about this process automatically making all the actions on behalf the user.
The SQL Cloud - Query Server page is displayed below:
...
The page displays the database connection status:
...
The limit to connect is 10 seconds. If the threshold is reached then a timeout exception will be raised.
The database username is the Jira instance name (same as in the URL).
The database password can be read from that page (click on the Edit password link). Initially a random password is created, but the user can change it or create a new random one automatically whether it is blank saved.
The database port does not matter. You can use any one available in the local machine and the JDBC Driver will use it for all the local communication. This is also configured in the JDBC connection URL.
Limitations
At the moment. The schema name is not supported in the queries running via JDBC.
Ex:
SELECT * FROM PUBLIC.PROJECT
will fail. Please use this instead:
SELECT * FROM PROJECT
...