• 44
    • 21
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server including Data Center.
      This request to also covers ONLY Aurora deployments, for Aurora Serverless see JRASERVER-41985

      Amazon is using a MySQL and Postgres compatible database servers, called Aurora, for use in the AWS. It would be great if we can have support for this database, which according to Amazon, is designed to be compatible with MySQL 5.6 and postgres 9.6+

      For clarification, on Jira 8.4, support for Aurora PostgreSQL was added. There's an open feature request to add support for MySQL:

      (JRASERVER-72376) Support for Amazon Aurora Database for MySQL

            [JRASERVER-41985] Support for Amazon Aurora Database

            Logged https://jira.atlassian.com/browse/JRASERVER-71055 specifically on the AURORA_VERSION() issue. 

            Colin McDermott_GLiNTECH added a comment - Logged  https://jira.atlassian.com/browse/JRASERVER-71055  specifically on the AURORA_VERSION() issue. 

            Milen Kostadinov added a comment - - edited

            Just for info (accidentally found it), we use these:

            • Jira Server 8.4.1 (Win Server 2012)
            • PostgreSQL 9.6.12 on x86_64-pc-mingw64, compiled by gcc.exe (Rev5, Built by MSYS2 project) 4.9.2, 64-bit
              2019-11-07 14:08:43 GMT [1232]: [1-1] user=jira,db=jira,app=[unknown],client=127.0.0.1 ERROR:  function aurora_version() does not exist at character 8
              2019-11-07 14:08:43 GMT [1232]: [2-1] user=jira,db=jira,app=[unknown],client=127.0.0.1 HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
              2019-11-07 14:08:43 GMT [1232]: [3-1] user=jira,db=jira,app=[unknown],client=127.0.0.1 STATEMENT:  select AURORA_VERSION() as aurora_version
              

            Milen Kostadinov added a comment - - edited Just for info (accidentally found it), we use these: Jira Server 8.4.1 (Win Server 2012) PostgreSQL 9.6.12 on x86_64-pc-mingw64, compiled by gcc.exe (Rev5, Built by MSYS2 project) 4.9.2, 64-bit 2019-11-07 14:08:43 GMT [1232]: [1-1] user=jira,db=jira,app=[unknown],client=127.0.0.1 ERROR: function aurora_version() does not exist at character 8 2019-11-07 14:08:43 GMT [1232]: [2-1] user=jira,db=jira,app=[unknown],client=127.0.0.1 HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2019-11-07 14:08:43 GMT [1232]: [3-1] user=jira,db=jira,app=[unknown],client=127.0.0.1 STATEMENT: select AURORA_VERSION() as aurora_version

            Tadas added a comment - - edited

            Ping @sking@atlassian.com , our DBA tried to silence errors by creating aurora_version() that returns nothing, and now we have warning in Jira that the use Aurora and we need Datacenter license...

             

            Pelase consider checking SELECT version(), as it might have "Aurora" string in there, instead of creating errors in the logs.

            Tadas added a comment - - edited Ping @ sking@atlassian.com , our DBA tried to silence errors by creating aurora_version() that returns nothing, and now we have warning in Jira that the use Aurora and we need Datacenter license...   Pelase consider checking SELECT version() , as it might have "Aurora" string in there, instead of creating errors in the logs.

            Tadas added a comment -

            Looks like this introduces this error messag in PostgreSQL logs regurarly:

            2019-10-18 11:10:12 EEST PostgreSQL JDBC Driver jiradb jira_user 127.0.0.1 ERROR: function aurora_version() does not exist at character 8
            2019-10-18 11:10:12 EEST PostgreSQL JDBC Driver jiradb jira_user 127.0.0.1 HINT: No function matches the given name and argument types. You might need to add explicit type casts.
            2019-10-18 11:10:12 EEST PostgreSQL JDBC Driver jiradb jira_user 127.0.0.1 STATEMENT: select AURORA_VERSION() as aurora_version
            2019-10-18 11:12:13 EEST PostgreSQL JDBC Driver jiradb jira_user 127.0.0.1 ERROR: function aurora_version() does not exist at character 8
            2019-10-18 11:12:13 EEST PostgreSQL JDBC Driver jiradb jira_user 127.0.0.1 HINT: No function matches the given name and argument types. You might need to add explicit type casts.
            2019-10-18 11:12:13 EEST PostgreSQL JDBC Driver jiradb jira_user 127.0.0.1 STATEMENT: select AURORA_VERSION() as aurora_version
            

            There was no such issue on 8.3.x.

            I've wanted to create new issue, but Atlassian suggest to only ask community question...

            Tadas added a comment - Looks like this introduces this error messag in PostgreSQL logs regurarly: 2019-10-18 11:10:12 EEST PostgreSQL JDBC Driver jiradb jira_user 127.0.0.1 ERROR: function aurora_version() does not exist at character 8 2019-10-18 11:10:12 EEST PostgreSQL JDBC Driver jiradb jira_user 127.0.0.1 HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2019-10-18 11:10:12 EEST PostgreSQL JDBC Driver jiradb jira_user 127.0.0.1 STATEMENT: select AURORA_VERSION() as aurora_version 2019-10-18 11:12:13 EEST PostgreSQL JDBC Driver jiradb jira_user 127.0.0.1 ERROR: function aurora_version() does not exist at character 8 2019-10-18 11:12:13 EEST PostgreSQL JDBC Driver jiradb jira_user 127.0.0.1 HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2019-10-18 11:12:13 EEST PostgreSQL JDBC Driver jiradb jira_user 127.0.0.1 STATEMENT: select AURORA_VERSION() as aurora_version There was no such issue on 8.3.x. I've wanted to create new issue, but Atlassian suggest to only ask community question...

            Darryl H added a comment -

            As a company we are moving towards Amazon Aurora, It would be great to have this feature in both versions  Server and DataCenter.

            I read it like confluence will only be supported in DataCenter why not server?

            It is a database engine, is your codebase really that different between versions, 

             

            Darryl H added a comment - As a company we are moving towards Amazon Aurora, It would be great to have this feature in both versions  Server and DataCenter. I read it like confluence will only be supported in DataCenter why not server? It is a database engine, is your codebase really that different between versions,   

            At Summit in Las Vegas there was a slide during the keynote that support for Aurora was coming soon to data center. Can someone from Atlassian confirm the target version?

            Greg Warner (Amazon) added a comment - At Summit in Las Vegas there was a slide during the keynote that support for Aurora was coming soon to data center. Can someone from Atlassian confirm the target version?

            Make it so! +1 LGTM

            Michael Joy added a comment - Make it so! +1 LGTM

            Ray Choi added a comment -

            I need this!

            Ray Choi added a comment - I need this!

            Since there is no comment from anyone from Atlassian yet I opened a support issue. This is the core of their response:

            We cant assure that using Jira with an unofficial database as Amazon Aurora with will work fine since we didn't test the applications on it.

            Most of the time it'll work for some period of time and then broke after some add-on update or even a minor application update, we can't predict all the scenarios that might impact on it.

            The dilemma is not that JIRA will not work, is that if you encounter any issues that may be database related, we can't offer support on this since it's something that wasn't tested fully by our dev team.

            The suggestion is to test it using a staging environment and decides if it's a good option keep using it or chooses any other supported database outlined in the Supported Platforms page.

            This is not what I wanted but it is what I expected.

            For the time being I'll continue to use standard MySQL.

            Gustavo Chaves added a comment - Since there is no comment from anyone from Atlassian yet I opened a support issue. This is the core of their response: We cant assure that using Jira with an unofficial database as Amazon Aurora with will work fine since we didn't test the applications on it. Most of the time it'll work for some period of time and then broke after some add-on update or even a minor application update, we can't predict all the scenarios that might impact on it. The dilemma is not that JIRA will not work, is that if you encounter any issues that may be database related, we can't offer support on this since it's something that wasn't tested fully by our dev team. The suggestion is to test it using a staging environment and decides if it's a good option keep using it or chooses any other supported database outlined in the Supported Platforms page. This is not what I wanted but it is what I expected. For the time being I'll continue to use standard MySQL.

            Oops, my bad. I had that link in my docs and didn't check the version - still they are very picky in their supported versions, so if they don't write Aurora - they are not supporting it.

            Edward Dumser added a comment - Oops, my bad. I had that link in my docs and didn't check the version - still they are very picky in their supported versions, so if they don't write Aurora - they are not supporting it.

              sking@atlassian.com steve
              aquadrospetry Andre Quadros Petry (Inactive)
              Votes:
              125 Vote for this issue
              Watchers:
              114 Start watching this issue

                Created:
                Updated:
                Resolved: