No Mean Feat: Upgrading a Customized Solr to Upstream Solr
Formal Metadata
| Title | No Mean Feat: Upgrading a Customized Solr to Upstream Solr |
|
| Title of Series | |
| Number of Parts | 60 |
| Author | |
| License | You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. |
| Identifiers | |
| Publisher | |
| Release Date | |
| Language | |
Content Metadata
| Subject Area | |
| Genre | |
| Abstract | Technology upgrades are a key pillar of software infrastructure. However, upgrading search and information retrieval systems is a complex task. At Bloomberg, we had extended the open source Apache Solr implementation with in-house patches to customize it for our use cases. This made upgrading to a newer version quite challenging. But, when you have close to a billion documents that are used by major financial institutions across the world, you cannot afford any mistakes.
Learn how the News Search Infrastructure Team at Bloomberg migrated from a highly customized implementation of Apache Solr to the upstream Apache Solr, while also making sure that the quality, correctness, and performance of the system was not affected. You will learn about the different strategies we used before, during, and after the migration to make the upgrade transparent to our internal users, all while serving millions of requests everyday. |
|