Abstract
While the vitrivr stack has seen many changes in components over the years, its feature extraction and query processing engine traces its history back almost a decade. Some aspects of its architecture and operation are no longer current, limiting the entire stack’s applicability in various use cases. In this paper, we present the first glimpse into vitrivr’s next-generation retrieval engine and our plan to overcome previously identified limitations.