This evening we will switch Codeberg.org's issue search backend from Bleve to our new OpenSearch cluster.
-
This evening we will switch Codeberg.org's issue search backend from Bleve to our new OpenSearch cluster. During this transition, search results might be unavailable or inaccurate as every issue is getting re-indexed. We've done a test on a snapshot of the data and then it took roughly 1 hour for re-indexing.
-
This evening we will switch Codeberg.org's issue search backend from Bleve to our new OpenSearch cluster. During this transition, search results might be unavailable or inaccurate as every issue is getting re-indexed. We've done a test on a snapshot of the data and then it took roughly 1 hour for re-indexing.
-
This evening we will switch Codeberg.org's issue search backend from Bleve to our new OpenSearch cluster. During this transition, search results might be unavailable or inaccurate as every issue is getting re-indexed. We've done a test on a snapshot of the data and then it took roughly 1 hour for re-indexing.
@codebergstatus have a good migration. Thanks for your hard work
-
This evening we will switch Codeberg.org's issue search backend from Bleve to our new OpenSearch cluster. During this transition, search results might be unavailable or inaccurate as every issue is getting re-indexed. We've done a test on a snapshot of the data and then it took roughly 1 hour for re-indexing.
Re-indexing just started.
-
This evening we will switch Codeberg.org's issue search backend from Bleve to our new OpenSearch cluster. During this transition, search results might be unavailable or inaccurate as every issue is getting re-indexed. We've done a test on a snapshot of the data and then it took roughly 1 hour for re-indexing.
@codebergstatus Thank you for your work!
-
R relay@relay.infosec.exchange shared this topic
