create or rebuild job executes successfully but the data has not been in sycn with es when the fulltext index name in upper case

[henry202108]

Please check the FAQ documentation before raising an issue

Describe the bug (required)
When the fulltext index name is in uppercase(in fact es can not support index name in uppercase ), the create or rebuild job executes successfully but the data has not been in sycn with es and no error return in the log(log level v sets to 0)

Your Environments (required)

• OS: uname -a
• Compiler: g++ --version or clang++ --version
• CPU: lscpu
• Commit id (e.g. a3ffc7d8)
  Linux 192-168-8-191 3.10.0-1160.36.2.el7.x86_64 Parser framework #1 SMP Wed Jul 21 11:57:15 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  g++ (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44)

Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1

f895632

How To Reproduce(required)

Steps to reproduce the behavior:

1. Step 1
   create two fulltext indexes, one is in uppercase one is in lowercase
2. Step 2
   rubuild fulltext index ,the one in uppercase is not in sycn with es
3. Step 3
   check the log and no errer return
4. Step 4
   if set up the v to 3 the error message shows:
   standardDataItem] ElasticsearchStatusException[Elasticsearch exception [type=invalid_index_name_exception, reason=Invalid index name [standardDataItem], must be lowercase]]

Expected behavior
Two options

1. create or rubuild fail in nebula and return the error information
2. do case conversion in the code and ensure that all the letter is in lowercase when interact with es

Additional context