On Wed, Nov 11, 2020 at 5:26 AM AntiCompositeNumber <anticompositenum...@gmail.com> wrote: > I understand the system engineering reasons for this change, but I > think it's worth underscoring exactly how disruptive it will be for > the queries that depended on this functionality.
The use cases seem to be relatively few and relatively limited. Could this perhap be a good case for a data mart (ETL) or meta index style approach? I'm thinking of things like CloverDX and Jaspersoft ETL, or even Apache Solr or another non-SQL solution. Moving JOINs up the stack from the SQL layer to the application layer does not sound like an architecturally sound approach. Cheers, Xover _______________________________________________ Wikimedia Cloud Services mailing list Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/cloud
