Strange UI bug for advanced query

Community Support
1

1
13124×752 177 KB
2
23110×890 164 KB
3
33102×738 179 KB
4
43104×858 117 KB
5
53110×1052 158 KB

Checked the requests. The one worked is:
/api/namespaces/default/workflows/closed?startTime=2020-12-20T08%3A00%3A00.000Z&endTime=2020-12-24T07%3A59%3A59.999Z&queryString=WorkflowType%20%3D%20%22NonExisting%22

The one did not work is: /api/namespaces/default/workflows/list?startTime=2020-12-20T08%3A00%3A00.000Z&endTime=2020-12-24T07%3A59%3A59.999Z&queryString=WorkflowType%20%3D%20%22NonExisting%22

So when “All” it uses “list” and does not work

2

All which uses list requires ElasticSearch to work. We have a work item to disable it in UI when ES is not configured.

3

Oh, but I do have ElasticSearch configured. I probably made some configuration mistake. I modified the helm chart project in order to add search attribute index for searching workflow

4

How do I test if ElasticSearch is working properly or not for Temporal? Thank you very much!

5

I’m pretty sure my ElasticSearch is good. I tried curl and it returns properly. How can I find out why the UI is not calling ElasticSearch or why it thinks ElasticSearch is broken? Thank you

➜  helm-charts git:(master) ✗ kubectl exec -it services/temporal-frontend /bin/bash
kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] -- [COMMAND] instead.

bash-5.0# curl -X GET "http://elasticsearch-master:9200/temporal-visibility-dev/_search"

{"took":2,"timed_out":false,"_shards":{"total":5,"successful":5,"skipped":0,"failed":0},"hits":{"total":2,"max_score":1.0,"hits":[{"_index":"temporal-visibility-dev","_type":"_doc","_id":"0e11cf61-125e-4beb-a112-aa1ff1e79d99~0540b41e-7a76-42ae-97c2-48ef5b6d98d7","_score":1.0,"_source":{"Attr":{"orderId":"V4C2xXFxEY","status":"\"readyForFulfillment\""},"CloseTime":1608783026813515025,"ExecutionStatus":2,"ExecutionTime":0,"HistoryLength":15,"KafkaKey":"0-1600","NamespaceId":"1754a5fc-b235-4ea7-8b6d-c5cb726840ed","RunId":"0540b41e-7a76-42ae-97c2-48ef5b6d98d7","StartTime":1608783025939637359,"TaskQueue":"ORDER_TASK_QUEUE","WorkflowId":"0e11cf61-125e-4beb-a112-aa1ff1e79d99","WorkflowType":"OrderWorkflow"}},{"_index":"temporal-visibility-dev","_type":"_doc","_id":"temporal-sys-history-scanner~76ad0770-c659-4806-b40e-d7e5cd0a6ea3","_score":1.0,"_source":{"Attr":{},"ExecutionStatus":1,"ExecutionTime":1608811206552890780,"KafkaKey":"0-1597","NamespaceId":"32049b68-7872-4094-8e63-d0dd59896a83","RunId":"76ad0770-c659-4806-b40e-d7e5cd0a6ea3","StartTime":1608781312552890780,"TaskQueue":"temporal-sys-history-scanner-taskqueue-0","WorkflowId":"temporal-sys-history-scanner","WorkflowType":"temporal-sys-history-scanner-workflow"}}]}}
7

Hello, how can I check if Temporal thinks the ES is properly configured and using it to query workflows? How to make sure the UI and cli is querying workflows from ES?

Thank you very much!

8

Hi Gordon, sorry for late reply (holidays time, you know).

I think your ES is configured properly and is used for read operations. If it is not enabled, you will something like this:

image
image1329×197 15.4 KB

I was able to reproduce it and can confirm that advanced query doesn’t work when “All” status selected. I filed a bug for it. For now, I would recommend you to select either “Open” or “Close” before switching to “Advance” mode.

1 Like
9

Thank you @alex. Could you post the bug link here?