This isn’t even the example that’s really bad. Use compound or computed fields and watch per go through the floor because you defeated the index. This is why @RavenDB doesn’t even let you do it at all. If you need to do it, you use an index that’s the shape you need ahead of time instead of doing dumb stuff.

Excellent product that once you understand how it does indexes, is the best of both worlds. To get the most out of it you need to understand databases but it has full vector and Lucene search built in, sharding, load balancing the whole deal that gets hard fast with others.