| Note |
|---|
Atlassian endshas ended support for the data source connections for external data sourcesin Confluence 8.0. It recommends switching to a direct JDBC connectionThe recommendation is to switch from the existing JNDI data source connections and move to a direct JDBC connection. For more information, refer to Configuring a data source connection. |
Considering the Confluence 8.x upliftment, the upcoming release of SQL for Confluence app will no longer support profiles based on the JNDI data source connections with Confluence 8.x. The already configured Application server defined data source based (global data source) profiles will have to be converted to connection string profiles. Our team is working on this and will soon release the SQL for Confluence app and update the documentation.
To know more about this change, read the FAQ below.
FAQ
| Expand | ||
|---|---|---|
| ||
No, this change does not impact the Confluence 7.x versions. |
| Expand | ||
|---|---|---|
| ||
The upcoming release version is SQL for Confluence 11.x, and |
...
it will work seamlessly with Confluence 7.x (Confluence 7.4 to Confluence 7.20) versions, including support for JNDI data source connections. |
| Expand | ||
|---|---|---|
| ||
The upcoming release version SQL for Confluence 11.x will be compatible with Confluence 8.x and will drop the support for profiles based on the JNDI data source connections. |
| Expand | ||
|---|---|---|
| ||
To resolve this, you need to manually convert the Application server defined data source (global data source) configurations to a connection string profile. Our team is working on these changes and will soon release the tutorial. |
| Expand | ||
|---|---|---|
| ||
SQL for Confluence 11.x version will be released on the Atlassian Marketplace in the week of Feb 20, 2023. |