Relaxed the previous transport version check, which was in fact always false - replace it with something that can work for now.

Author: shmuelhanoch

x-pack/plugin/esql-core/src/main/java/org/elasticsearch/xpack/esql/core/type/DataType.java

@@ -271,6 +271,9 @@ public enum DataType implements Writeable {
      * Nanosecond precision date, stored as a 64-bit signed number.
      */
     DATE_NANOS(builder().esType("date_nanos").estimatedSize(Long.BYTES).docValues().supportedOnAllNodes()),
+    /**
+     * Represents a half-inclusive range between two dates.
+     */
     DATE_RANGE(builder().esType("date_range").estimatedSize(2 * Long.BYTES).docValues().supportedOn(ESQL_DATE_RANGE_CREATED_VERSION)),
     /**
      * IP addresses. IPv4 address are always

x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/analysis/PreAnalyzer.java

@@ -88,7 +88,12 @@ protected PreAnalysis doPreAnalyze(LogicalPlan plan) {
                 supportsAggregateMetricDouble.set(true);
             }
         }));
-
+        // This is a temporary solution for the first phase of date_range: ATM we don't support any functions
+        // on date_range, but we do want to allow the simplest possible cases of loading and rendering those fields.
+        // Not the most useful idea but it is a (relatively) safe way to add it without breaking tests.
+        if (plan.expressions().isEmpty()) {
+            supportsDateRange.set(true);
+        }
         // mark plan as preAnalyzed (if it were marked, there would be no analysis)
         plan.forEachUp(LogicalPlan::setPreAnalyzed);