name of WITH query needs to be normalized to be case-insensitive
Add array concat operator

Added array-to-array, element-to-array, and array-to-element concat (||) support
Fix intellij warnings
Add support for non-equi inner joins
Add ntile window function
Only merge ORC reads that are close together
Implement json equality operators
Improved string representation of array values in jmx connector

Arrays were being rendered using the default toString representation.
So, an Array would be rendered as something like [Ljava.lang.String;@4da91ced.
Arrays are now rendered as a string representation of the contents of the array.
The string representation consists of a list of the array's elements,
enclosed in square brackets ("[]").  Adjacent elements are separated by ", ".

Fixes #1632
Improve error message when using DISTINCT with non-comparable types
Validate types for IN subquery expression
Throw proper exception when memory size exceeded in TopN
Verify that types of ORDER BY expressions are orderable
Fix handling of SampleNode in SymbolExtractor
Add array constructor syntax to migration guide
Add developer guide to documentation

Currently, this includes documentation for types, scalar functions, and
aggregation functions
Added support for map construction from key/value arrays
Implement min_by aggregation function
Add JMX counters for query bytes rate distribution
Expire queries only after maxQueryAge

This fixes a regression introduced in c918b549cf0cca6c3329b8f8ea5c9d23beadb128, where
the expiration queue would get trimmed to maxQueryHistory regardless of how long ago
the queries had finished. This can result in clients getting "not found" errors
in highly loaded clusters that retire queries quickly.

This implementation now keeps queries around until for at least maxQueryAge after
they are finished, but it can keep them longer if the history is less than maxQueryHistory
 long.
Run information_schema queries only in coordinator

This fixes an issue where queries over information_schema could run in
any of the workers, resulting in inconsistent metadata due to caching
(e.g., "describe <table>" might show 0 columns for a table that had
recently been deleted)

As part of this change, the split scheduler has been updated to pick
the coordinator for processing coordinator-only splits regardless
of the value of the includeCoordinator flag