Fails to parse ES query result · cube-js/cube#3128

(1 留言) (0 反應) (0 負責人)Rust (19,563 star) (1,965 fork)batch import

driver:elasticsearchhelp wanted

描述

Describe the bug Cubejs fails to parse ES query result.

To Reproduce Steps to reproduce the behavior:

Create a valid cube schema connecting to AWS ES 7.7
Build a query using cubejs play ground with just measure and dimension
Run the query
See error

Expected behavior Generated SQL query from cubejs log can be copied to kibana and executed successfully. So, query result should be shown in chart.

Screenshots Screen shot attached.

Error: Cannot read property 'map' of undefined
    at QueryQueue.parseResult (/cube/node_modules/@cubejs-backend/query-orchestrator/src/orchestrator/QueryQueue.js:125:13)
    at QueryQueue.executeInQueue (/cube/node_modules/@cubejs-backend/query-orchestrator/src/orchestrator/QueryQueue.js:114:19)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at /cube/node_modules/@cubejs-backend/query-orchestrator/src/orchestrator/QueryCache.ts:330:17
    at QueryOrchestrator.fetchQuery (/cube/node_modules/@cubejs-backend/query-orchestrator/src/orchestrator/QueryOrchestrator.ts:92:20)
    at OrchestratorApi.executeQuery (/cube/node_modules/@cubejs-backend/server-core/src/core/OrchestratorApi.ts:57:20)
    at /cube/node_modules/@cubejs-backend/api-gateway/src/gateway.ts:797:26
    at async Promise.all (index 0)
    at ApiGateway.load (/cube/node_modules/@cubejs-backend/api-gateway/src/gateway.ts:782:23)
    at /cube/node_modules/@cubejs-backend/api-gateway/src/gateway.ts:281:7
Orchestrator error: 65ef53e6-1fed-4417-978d-5d36c946e066-span-1 (953ms)

Version: v0.27.53 AWS ES 7.7

Additional context Generated SQL query has be run through kibana to verify there is no issue with query.

貢獻者指南

技術棧: typescriptnodejsrest api
領域: backendapidatabase
議題類型: bug
難度: 2
預計時間: under 1 hour
活動狀態: stale
清晰度: clear
前置要求: TypeScriptNode.jsCube.js query orchestration
新手友善度: 70
研究方向: Investigate the parseResult method in QueryQueue.js line 125. The error occurs because the result object is undefined when calling .map. Check the Elasticsearch driver's response format for the case when there are no results. Consider adding a guard clause to handle undefined or non array results.