When running a window function query on large datasets, increasing planner.memory.max_query_memory_per_node can actually help the query not run out of memory. But in some cases this can cause some issues (see DRILL-3555 <https://issues.apache.org/jira/browse/DRILL-3555>)
This seems to be caused by a hardcoded limit in ExternalSort called MAX_SORT_BYTES. What is the purpose of this limit ? -- Abdelhakim Deneche Software Engineer <http://www.mapr.com/> Now Available - Free Hadoop On-Demand Training <http://www.mapr.com/training?utm_source=Email&utm_medium=Signature&utm_campaign=Free%20available>
