Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-13247

Add support for Elasticsearch 8

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Search
    • None
    • 133
    • We collect Bitbucket 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.

      Important: Elasticsearch license change

      Note that Elasticsearch versions from 7.11 onwards are no longer available licensed under the Apache 2.0 open source license. See here and here for details of the new licensing.

      Support for using Elasticsearch 8 with Bitbucket Server & Data Center should be added.

      Note: The scope of this issue does not include bundling Elasticsearch 8.0 with Bitbucket, rather just used as an external/self-managed service, as is required when running Bitbucket in a cluster. Due to the licensing change, Atlassian is not able to bundle Elasticsearch 8.0

            [BSERV-13247] Add support for Elasticsearch 8

            Anurag Jalan added a comment -

            It would be good to have elastic 8 as well as 9 support. Elastic is used widely by organizations across world for various purposes. Some of us have invested in setting up elastic infra over last few years. In terms of performance, it is superior to opensearch as well.

            Customers should get an option on which one to go for instead of withdrawing the complete support.

            Anurag Jalan added a comment - It would be good to have elastic 8 as well as 9 support. Elastic is used widely by organizations across world for various purposes. Some of us have invested in setting up elastic infra over last few years. In terms of performance, it is superior to opensearch as well. Customers should get an option on which one to go for instead of withdrawing the complete support.

            Stefan added a comment -

            There is a lot of enterprises that have invested in elasticsearch infrastructure that would have seen great benefit with elasticsearch support.

            Maybe you should ask your customers?

            Stefan added a comment - There is a lot of enterprises that have invested in elasticsearch infrastructure that would have seen great benefit with elasticsearch support. Maybe you should ask your customers?

            Sake added a comment -

            Probably will be completly ignored becaues of the statement made in https://jira.atlassian.com/browse/CONFSERVER-96112

            Sake added a comment - Probably will be completly ignored becaues of the statement made in https://jira.atlassian.com/browse/CONFSERVER-96112

            Sake added a comment -

            Please also vote on https://jira.atlassian.com/browse/CONFSERVER-96112 for Elasticsearch support for Confluence.

            Sake added a comment - Please also vote on https://jira.atlassian.com/browse/CONFSERVER-96112 for Elasticsearch support for Confluence.

            Sake added a comment -

            We're paying premium price for the Atlassian stack and it's a shame version 8 isn't supported and version 9 is probably around the corner. Just like  833ca81f20cc is saying; we don't need to vote for this, support for Elasticsearch should be the norm.

            A good guess why the switch to Opensearch is made, is because of AWS and Atlassian using it's services.

            Somethin else, hearing about Confluence en moving it's search index to Opensearch is also a blow to paying customers. Why not use Elasticsearch and make it possible to use the same cluster for both applications. Looking at a blogpost from Elasticsearch about performance (https://www.elastic.co/blog/elasticsearch-opensearch-performance-gap), Opensearch isn't quite up to the task.

            Sake added a comment - We're paying premium price for the Atlassian stack and it's a shame version 8 isn't supported and version 9 is probably around the corner. Just like   833ca81f20cc is saying; we don't need to vote for this, support for Elasticsearch should be the norm. A good guess why the switch to Opensearch is made, is because of AWS and Atlassian using it's services. Somethin else, hearing about Confluence en moving it's search index to Opensearch is also a blow to paying customers. Why not use Elasticsearch and make it possible to use the same cluster for both applications. Looking at a blogpost from Elasticsearch about performance ( https://www.elastic.co/blog/elasticsearch-opensearch-performance-gap ), Opensearch isn't quite up to the task.

            Kevin Lange added a comment -

            We should not be required to "vote" for this issue.  This is what we pay Atlassian premium price for their products.  This is basic sustaining engineering and dependency lifecycle management that we already pay for; ElasticSearch (not bundled) is required for Bitbucket search, then Atlassian should be on-track with testing and providing support for ElasticSearch 8.x, especially since ES 8.0.0 has been available since February 2022.  Upstream support for ElasticSearch through elastic.co development provides patches for security and functionality defects for ElasticSearch 7.x until August 1 2023 or 6 months after ElasticSearch 9.0.0 is released (I swear they just recently added the "6 months after", but I don't have confirmation of that).  This is still pretty 11th hour to be considering support for ElasticSearch 8.x; Atlassian should have been considering support for 8.x when it was in alpha/beta.

            Support for OpenSearch looks to be in a similar state (https://opensearch.org/releases.html#maintenance-policy) with Atlassian supporting 1.x only, and 2.x has been available since May 2022.

            Kevin Lange added a comment - We should not be required to "vote" for this issue.  This is what we pay Atlassian premium price for their products.  This is basic sustaining engineering and dependency lifecycle management that we already pay for; ElasticSearch (not bundled) is required for Bitbucket search, then Atlassian should be on-track with testing and providing support for ElasticSearch 8.x, especially since ES 8.0.0 has been available since February 2022.  Upstream support for ElasticSearch through elastic.co development provides patches for security and functionality defects for ElasticSearch 7.x until August 1 2023 or 6 months after ElasticSearch 9.0.0 is released (I swear they just recently added the "6 months after", but I don't have confirmation of that).  This is still pretty 11th hour to be considering support for ElasticSearch 8.x; Atlassian should have been considering support for 8.x when it was in alpha/beta. Support for OpenSearch looks to be in a similar state ( https://opensearch.org/releases.html#maintenance-policy ) with Atlassian supporting 1.x only, and 2.x has been available since May 2022.

            Allan0_06 added a comment -

            We are using at the moment an AWS Opensearch Service for enabling the search capability in bitbucket. We are moving away from AWS and towards Azure. on Azure we have to use a Elastic Search service for Bitbucket and the new service only supports Elastic search version 8.x according to the companies policies. The policy is enforced because ES 7.x will be EOL end of the year. 

            Allan0_06 added a comment - We are using at the moment an AWS Opensearch Service for enabling the search capability in bitbucket. We are moving away from AWS and towards Azure. on Azure we have to use a Elastic Search service for Bitbucket and the new service only supports Elastic search version 8.x according to the companies policies. The policy is enforced because ES 7.x will be EOL end of the year. 

            IT Infrastructure added a comment - - edited

            This is important as Bitbucket is the last application we run which does not support Elasticsearch 8, requiring us to maintain legacy systems specifically for it.

             

            This might involve updating Buckler, so mentioning it as a keyword here.

            IT Infrastructure added a comment - - edited This is important as Bitbucket is the last application we run which does not support Elasticsearch 8, requiring us to maintain legacy systems specifically for it.   This might involve updating Buckler, so mentioning it as a keyword here.

              Unassigned Unassigned
              ce3030380072 Amit Singh
              Votes:
              30 Vote for this issue
              Watchers:
              29 Start watching this issue

                Created:
                Updated: