Cleanup

Author: smalyshev

x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/optimizer/PhysicalVerifier.java

@@ -36,16 +36,6 @@ public Failures verify(PhysicalPlan plan) {
         if (enriches.isEmpty() == false && ((EnrichExec) enriches.get(0)).mode() == Enrich.Mode.REMOTE) {
             return failures;
         }
-        // Do the same for remote lookup joins
-        // var fragment = plan.collectFirstChildren(FragmentExec.class::isInstance);
-        // if (fragment.isEmpty() == false) {
-        // // LookupJoin gets rewritten as Join by surrogate()
-        // FragmentExec f = (FragmentExec) fragment.get(0);
-        // var ljoins = f.fragment().collectFirstChildren(Join.class::isInstance);
-        // if (ljoins.isEmpty() == false) {
-        // return failures;
-        // }
-        // }
 
         plan.forEachDown(p -> {
             if (p instanceof FieldExtractExec fieldExtractExec) {

x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/plan/physical/LookupJoinExec.java

@@ -163,5 +163,4 @@ public boolean equals(Object o) {
     public int hashCode() {
         return Objects.hash(super.hashCode(), leftFields, rightFields, addedFields);
     }
-
 }

x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/planner/Layout.java

@@ -115,7 +115,7 @@ public Layout build() {
                 for (NameId id : set.nameIds) {
                     // Duplicate name ids would mean that have 2 channels that are declared under the same id. That makes no sense - which
                     // channel should subsequent operators use, then, when they want to refer to this id?
-                    assert (layout.containsKey(id) == false) : "Duplicate name ids are not allowed in layouts: " + id;
+                    assert (layout.containsKey(id) == false) : "Duplicate name ids are not allowed in layouts";
                     ChannelAndType next = new ChannelAndType(channel, set.type);
                     layout.put(id, next);
                 }