zhdech opened a new issue, #8752:
URL: https://github.com/apache/seatunnel/issues/8752

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22bug%22)
 and found no similar issues.
   
   
   ### What happened
   
   "sink": [
       {
         "plugin_name": "Elasticsearch",
         "plugin_input": [
           "tran_12bb61"
         ],
         "index": "test_es_${OP_DAY}",
         "partitionKey": "sys_day",
         "isCache": "false",
         "esModel": "",
         "isCount": "false",
         "hosts": [
           "192.168.1.1:9200"
         ],
         "schema_save_mode": "IGNORE",
         "max_batch_size": 200
       }
   Cannot replace capitalized dynamic index names
   
   ### SeaTunnel Version
   
   2.3.9
   
   ### SeaTunnel Config
   
   ```conf
   "sink": [
       {
         "plugin_name": "Elasticsearch",
         "plugin_input": [
           "tran_12bb61"
         ],
         "index": "test_es_${OP_DAY}",
         "partitionKey": "sys_day",
         "isCache": "false",
         "esModel": "",
         "isCount": "false",
         "hosts": [
           "192.168.1.1:9200"
         ],
         "schema_save_mode": "IGNORE",
         "max_batch_size": 200
       }
   ```
   
   ### Running Command
   
   ```shell
   Cannot replace capitalized dynamic index names
   ```
   
   ### Error Exception
   
   ```log
   The log did not report any errors, it's just that the ES index name is 
incorrect
   test_es_${OP_DAY}
   ```
   
   ### Zeta or Flink or Spark Version
   
   _No response_
   
   ### Java or Scala Version
   
   java1.8
   
   ### Screenshots
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to