当我尝试运行“ PIO状态”时,字段“状态”重复

时间:2018-09-20 13:21:04

标签: apache elasticsearch predictionio

每当我print (dfs['squares_1']) square x y brightness time 1.0 1.0 243 233 1000 2.0 1.0 293 436 1200 3.0 5.0 176 203 2000 4.0 7.0 111 171 1300 print (dfs['squares_2']) square x y brightness time 1.0 2.0 189 230 4000 2.0 2.0 189 233 5000 5.0 8.0 239 284 4300 print (dfs['squares_3']) Empty DataFrame Columns: [square, x, y, brightness] Index: [] print (dfs['squares_4']) square x y brightness time 3.0 6.0 374 394 8000 出现以下错误

pio status

我的[INFO] [Management$] Inspecting PredictionIO... [INFO] [Management$] PredictionIO 0.13.0 is installed at /Users/prvns/tools/PredictionIO-0.13.0 [INFO] [Management$] Inspecting Apache Spark... [INFO] [Management$] Apache Spark is installed at /Users/prvns/tools/PredictionIO-0.13.0/vendors/spark-2.3.1-bin-hadoop2.7 [INFO] [Management$] Apache Spark 2.3.1 detected (meets minimum requirement of 1.6.3) [INFO] [Management$] Inspecting storage backend connections... [INFO] [Storage$] Verifying Meta Data Backend (Source: ELASTICSEARCH)... [ERROR] [Management$] Unable to connect to all storage backends successfully. The following shows the error message from the storage backend. PUT http://localhost:9200/pio_meta/_mapping/engine_instances: HTTP/1.1 400 Bad Request {"error":{"root_cause":[{"type":"parse_exception","reason":"Failed to parse content to map"}],"type":"parse_exception","reason":"Failed to parse content to map","caused_by":{"type":"json_parse_exception","reason":"Duplicate field 'status'\n at [Source: org.elasticsearch.common.compress.DeflateCompressor$1@6b496f00; line: 1, column: 462]"}},"status":400} (org.apache.predictionio.shaded.org.elasticsearch.client.ResponseException) Dumping configuration of initialized storage backend sources. Please make sure they are correct. Source Name: ELASTICSEARCH; Type: elasticsearch; Configuration: HOME -> /usr/local/Cellar/elasticsearch/6.2.4/, HOSTS -> localhost, PORTS -> 9200, SCHEMES -> http, TYPE -> elasticsearch 看起来像

pio-env.sh

为什么这不起作用?

1 个答案:

答案 0 :(得分:0)

我正在使用ElasticSearch 6.x。我将其替换为ElasticSearch 5.x,并且可以正常工作。