On Tue, 2018-11-20 at 21:17 -0700, Shawn Heisey wrote: > Maybe the error condition should be related to a new schema > property, something like allowQueryOnDocValues. This would default > to true with current schema versions and false in the next schema > version, which I think is 1.7. Then a user could choose to allow > them on a field-by-field basis, by reading documentation that > outlines the severe performance disadvantages.
I support the idea of making such choices explicit and your suggestion sounds like a sensible way to do it. I have toyed with a related idea: Issue a query with debug=sanity and get a report from checks on both the underlying index and the issued query for indicators of problems: https://github.com/tokee/lucene-solr/issues/54 - Toke Eskildsen, Royal Danish Library
