Since the current Tajo cannot process distinct aggregation functions for multiple columns, PreLogicalPlanVerifier prevents such a case. But, PreLogicalPlanVerifier checks it incorrectly. As a result, it causes a verification error even though a query can be actually executed in Tajo.
See the below example. This query can be actually executed in Tajo.
But, it causes the following verification error.