2. 程式人生 > >elasticsearch報InvalidIndexNameException[Invalid index name [demo_indexX1], must be lowercase錯誤

elasticsearch報InvalidIndexNameException[Invalid index name [demo_indexX1], must be lowercase錯誤

阿新 • • 發佈：2018-09-16
cut access nta and r.java ast 相同 zed strong

[demo_indexX1] InvalidIndexNameException[Invalid index name [demo_indexX1], must be lowercase
]
at org.elasticsearch.cluster.metadata.MetaDataCreateIndexService.validateIndexName(MetaDataCreateIndexService.java:151)
at org.elasticsearch.cluster.metadata.MetaDataCreateIndexService.validate(MetaDataCreateIndexService.java:431)
at org.elasticsearch.cluster.metadata.MetaDataCreateIndexService.access$100(MetaDataCreateIndexService.java:95)
at org.elasticsearch.cluster.metadata.MetaDataCreateIndexService$1.execute(MetaDataCreateIndexService.java:190)
at org.elasticsearch.cluster.ClusterStateUpdateTask.execute(ClusterStateUpdateTask.java:45)
at org.elasticsearch.cluster.service.InternalClusterService.runTasksForExecutor(InternalClusterService.java:468)
at org.elasticsearch.cluster.service.InternalClusterService$UpdateTask.run(InternalClusterService.java:772)
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:231)
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:194)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

must be lowercase翻譯過來就是索引名稱必須小寫

在此記錄防止以後再犯相同問題

elasticsearch報InvalidIndexNameException[Invalid index name [demo_indexX1], must be lowercase錯誤

相關推薦

elasticsearch報InvalidIndexNameException[Invalid index name [demo_indexX1], must be lowercase錯誤

cut access nta and r.java ast 相同 zed strong [demo_indexX1] InvalidIndexNameException[Invalid index name [demo_indexX1], must be lowercase

如何在同一臺電腦上同時執行兩個Tomcat(關於Invalid character found in method name.HTTP method names must be token.錯誤資訊)

今天在學習一個專案的時候需要用到Tomcat8，而我的Tomcat版本是7，因為Tomcat7用的久了比較習慣又不想解除安裝，所以打算兩個一起用，在網上查了同一臺電腦上可以執行兩個Tomcat後，就開始部署Tomcat8. 在看了一篇前輩的經驗後將Tomcat8的start

thrift+python 報錯Invalid method name

在用thrift通訊的時候, python寫的客戶端, 發現執行不起來, 報錯Invalid method name "xxx" 我很納悶,因為thrift自動生成了函式程式碼, 名稱絕對沒打錯, 引數也對,為什麼就不行? 後來我發現  16    transport =

python報錯：TypeError: slice indices must be integers or None or have an __index__ method

宣告：本文為博主原創文章，不可轉載 https://blog.csdn.net/jjddss/article/details/73469104 在使用Python進行矩陣操作時，當內部含有除法時，會產生錯誤： TypeError: slice indices must be integers

If ngModel is used within a form tag, either the name attribute must be set or the form contro

背景：angular中使用form表單時報錯。 報錯資訊：If ngModel is used within a form tag, either the name attribute must be set or the form control must b

python 之報錯：TypeError: write() argument must be str, not bytes

在用 pickle.dump() 儲存二進位制檔案時，一直報錯，程式如下： with open(os.path.join(FLAGS.train_data_dir, 'files.log'), 'w') as f: pickle.dump([training_paths, testing_

faster rcnn報錯：TypeError: slice indices must be integers or None or have an __index__ method

https://blog.csdn.net/qq_27637315/article/details/78849756 faster rcnn報錯：TypeError: slice indices must be integers or None or have an __index__ method

本地開發Spark，執行JavaSparkPi例子報錯：A master URL must be set in your configuration

錯誤資訊： Using Spark's default log4j profile: org/apache/spark/log4j-defaults.properties 18/08/21 18:39:27 INFO SparkContext: Running Spark versi

java AES 加密,報javax.crypto.IllegalBlockSizeException: Input length must be multiple of 16 when decryp

java 使用AES解密報這個異常,字面理解很容易,就是解密的字串的陣列必須是16的倍數javax.crypto.IllegalBlockSizeException: Input length must be multiple of 16 when decrypting wi

npm run dev 報錯 iview TypeError [ERR_INVALID_CALLBACK]: Callback must be a function

執行npm run dev報這個錯,什麼辦法都試了, 刪除專案下node_modules檔案下,然後再次安裝沒有用, 解除安裝nodejs，重新安裝也沒有用 然後查看了下報錯資訊如下圖示記：  D:\iview\iview-admin-dev\build\webpac

javax.mail 報錯 501 mail from address must be same as authorization user 解決方法

從一個郵箱傳送郵件 從一個郵箱傳送郵件報錯 501 mail from address must be same as authorization user，是由於獲取Session時的賬號和Message中設定的郵箱地址setFrom不一致引起的 程式碼如

執行gulp專案報錯：AssertionError: Task function must be specified。

gulp 3 和 gulp 4執行方式是不一樣的，所以會出現錯誤。具體細節，可以看這裡 gup3 VS gulp4 區別

Service Intent must be explicit錯誤

解決方案： 使用隱式方式繫結： **1.在service中新增action：** <service android:name="your service" android:exported="true"> <inte

django 啟動錯誤：Generator expression must be parenthesized 錯誤資訊：

錯誤為： Unhandled exception in thread started by <function check_errors.<locals>.wrapper at 0x10f03b8c8> Traceback (most recent call last):

【常見錯誤】佈局檔案新增edittext報：The following classes could not be found錯誤

一、問題描述 android專案佈局檔案中，新增edittext後佈局報以下錯誤： Exception raised during rendering: java.lang.System.arr

PLS-00201: identifier 'SYS.DBMS_JOB' must be declared 錯誤處理辦法

定義一個Job，SYS.DBMS_JOB.SUBMIT(...) 之後，執行發生錯誤。 ORA-06550: 第 4 行, 第 3 列:  PLS-00201: identifier 'SYS.DB

Tomcat報錯：Invalid character found in method name. HTTP method names must be tokens

問題： 報錯資訊：Invalid character found in method name. HTTP method names must be tokens 原因：Tomcat的header緩衝區大小不夠 解決方法：只需要在server.xml中增加maxHt

springboot專案請求報錯Invalid character found in method name. HTTP method names must be tokens

2018-01-26 09:57:23.845 INFO 12872 — [nio-8080-exec-7] o.apache.coyote.http11.Http11Processor : Error parsing HTTP request heade

專案半夜凌晨宕機，報錯Invalid character found in method name. HTTP method names must be tokens|the HTTP protoco

這幾天專案總是在凌晨掛機，檢視日誌發現以下錯誤：Http11Processor - Error parsing HTTP request header Note: further occurrences of HTTP header parsing errors will

Invalid character found in method name. HTTP method names must be tokens

error 緩沖 pan img cut ade odi port col o.apache.coyote.http11.Http11Processor : Error parsing HTTP request header Note: furt