ESQL: Extend RENAME syntax to allow a new = old syntax

docs/reference/query-languages/esql/_snippets/commands/layout/rename.md

@@ -8,6 +8,18 @@ The `RENAME` processing command renames one or more columns.
 RENAME old_name1 AS new_name1[, ..., old_nameN AS new_nameN]
 ```
 
+::::{note}
+
+Starting with the versions 8.19.0 and 9.1.0, the following syntax is also supported:
+
+```esql
+RENAME new_name1 = old_name1[, ..., new_nameN = old_nameN]
+```
+
+The two syntax flavours can be used interchangeably.
+
+::::
+
 **Parameters**
 
 `old_nameX`

x-pack/plugin/esql/qa/testFixtures/src/main/resources/rename.csv-spec

@@ -296,3 +296,50 @@ ROW a="keyword", b=5, c=null
 a:integer
 5
 ;
+
+useAssignmentOnly
+required_capability: rename_allow_assignment
+
+ROW a = 1, b = "two"
+| RENAME aa = a, bb = b
+;
+
+aa:integer | bb:keyword
+1          | two
+;
+
+useAssignmentAndASKeyword
+required_capability: rename_allow_assignment
+
+ROW a = 1, b = "two", c = null
+| RENAME aa = a, b AS bb, cc = c
+;
+
+aa:integer | bb:keyword | cc:null
+1          | two        | null
+;
+
+shadowWithAssignment
+required_capability: rename_allow_assignment
+
+ROW a = 1, b = "two"
+| RENAME a = b
+;
+
+a:keyword
+two
+;
+
+multipleRenamesWithAssignment
+required_capability: rename_sequential_processing
+required_capability: rename_allow_assignment
+
+ROW a="keyword", b=5, c=null
+| RENAME c = a, a = b
+| RENAME b = c
+| RENAME b = a, a = b
+;
+
+a:integer
+5
+;

x-pack/plugin/esql/src/main/antlr/EsqlBaseParser.g4

@@ -212,6 +212,7 @@ renameCommand
 
 renameClause:
     oldName=qualifiedNamePattern AS newName=qualifiedNamePattern
+    | newName=qualifiedNamePattern ASSIGN oldName=qualifiedNamePattern
     ;
 
 dissectCommand

x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/action/EsqlCapabilities.java

@@ -439,6 +439,11 @@ public enum Cap {
          */
         RENAME_SEQUENTIAL_PROCESSING,
 
+        /**
+         * Support for assignment in RENAME, besides the use of `AS` keyword.
+         */
+        RENAME_ALLOW_ASSIGNMENT,
+
         /**
          * Support for removing empty attribute in merging output.
          * See <a href="https://github.com/elastic/elasticsearch/issues/126392"> ESQL: EVAL after STATS produces an empty column #126392 </a>