The UI display is accelerated, but there are no specific acceleration details

Hi,
I compiled and built Dremio with the following commands:

mvn clean install -DskipTests -Ddremio.oss-only=true

After that I configured and ran Dremio.
I created a virtual table and created data reflection on the virtual table.

I execute sql query:

select * from henghe."es-person";

The accelerated icon is displayed in the job list, but there is no specific information related to acceleration,

According to the execution time, this job has indeed been accelerated.But I don’t know why it shows that no data reflection is used.
What is the reason for a situation like mine? Seek your help.

Good luck.

You would have to share a query profile with us so we can see what the exact issue is.

Hi,
First of all, thank you for your reply.And this is my query profile.
query profile (14.5 KB)
Looking forward to your next reply.
Good luck.

Hi,@doron Can you help me deal with my problem?
Thank you very much and look forward to your reply.

@thirdparty-core Seems like mis-reporting, can we get output of the below query, you should be able to download the result as JSON

select * from sys.reflections where reflection_id = '6c8077a9-2e82-4c16-8850-77b3b783750a'
select * from sys.materializations where reflection_id = '6c8077a9-2e82-4c16-8850-77b3b783750a'

Hi,@balaji.ramaswamy
The screenshot below is the same as my original question:




query profile (14.2 KB)
According to the method you provided, I queried sys.reflections and sys.materializations, but there was no result.


Seems like mis-reporting,but I don’t know what the reason is, and I look forward to your reply again.

Hi,

I used the wrong place here, reflection_id should be used.

After I use reflection_id, the query results are as follows:

select * from sys.reflections where reflection_id = '54a3b73f-cb6b-4a14-b5a7-4a7021826cda'
{
	"reflection_id": "54a3b73f-cb6b-4a14-b5a7-4a7021826cda",
	"name": "Raw Reflection",
	"type": "RAW",
	"status": "CAN_ACCELERATE",
	"num_failures": 0,
	"datasetId": "8e6a1d6f-68ae-48c0-82d8-855d9aa5e048",
	"dataset": "henghe.person",
	"datasetType": "VIRTUAL_DATASET",
	"sortColumns": "",
	"partitionColumns": "",
	"distributionColumns": "",
	"dimensions": "",
	"measures": "",
	"displayColumns": "address, gender, name, id, salary, age",
	"externalReflection": "",
	"arrow_cache": false
}
select * from sys.materializations where reflection_id = '54a3b73f-cb6b-4a14-b5a7-4a7021826cda'
{"reflection_id":"54a3b73f-cb6b-4a14-b5a7-4a7021826cda","materialization_id":"239aaf40-9eba-47f6-9d78-735a1c4bc941","create":"2022-01-09 23:22:51.368","expiration":"2022-01-10 02:22:51.368","bytes":35257933,"seriesId":1641770571452,"init_refresh_job_id":"1e2491b3-c690-7fc1-4963-5abb2d0ac400","series_ordinal":0,"join_analysis":"{\"joinTables\":[{\"tableId\":0,\"tableSchemaPath\":[\"es\",\"persons\",\"doc\"]}]}","state":"DEPRECATED","failure_msg":"NONE","data_partitions":"","last_refresh_from_pds":"2022-01-09 23:22:51.368"}
{"reflection_id":"54a3b73f-cb6b-4a14-b5a7-4a7021826cda","materialization_id":"7e3b1f20-9039-4135-92e2-7e4591d18976","create":"2022-01-10 00:22:52.132","expiration":"2022-01-10 03:22:52.132","bytes":35240481,"seriesId":1641774172219,"init_refresh_job_id":"1e2483a3-72a0-88a4-5e9c-60564ec52500","series_ordinal":0,"join_analysis":"{\"joinTables\":[{\"tableId\":0,\"tableSchemaPath\":[\"es\",\"persons\",\"doc\"]}]}","state":"DEPRECATED","failure_msg":"NONE","data_partitions":"","last_refresh_from_pds":"2022-01-10 00:22:52.132"}
{"reflection_id":"54a3b73f-cb6b-4a14-b5a7-4a7021826cda","materialization_id":"95f79b9d-7f6b-4f53-93f0-b65375b6f19e","create":"2022-01-10 01:22:52.843","expiration":"2022-01-10 04:22:52.842","bytes":35220596,"seriesId":1641777772858,"init_refresh_job_id":"1e247593-7e87-ee36-c794-d8a9eaefce00","series_ordinal":0,"join_analysis":"{\"joinTables\":[{\"tableId\":0,\"tableSchemaPath\":[\"es\",\"persons\",\"doc\"]}]}","state":"DONE","failure_msg":"NONE","data_partitions":"","last_refresh_from_pds":"2022-01-10 01:22:52.842"}
{"reflection_id":"54a3b73f-cb6b-4a14-b5a7-4a7021826cda","materialization_id":"bc094c22-1071-4f53-8f2e-87d66ded5348","create":"2022-01-09 22:22:50.636","expiration":"2022-01-10 01:22:50.635","bytes":35238048,"seriesId":1641766970692,"init_refresh_job_id":"1e249fc5-5742-7318-1232-2cceca38fa00","series_ordinal":0,"join_analysis":"{\"joinTables\":[{\"tableId\":0,\"tableSchemaPath\":[\"es\",\"persons\",\"doc\"]}]}","state":"DEPRECATED","failure_msg":"NONE","data_partitions":"","last_refresh_from_pds":"2022-01-09 22:22:50.635"}
{"reflection_id":"54a3b73f-cb6b-4a14-b5a7-4a7021826cda","materialization_id":"ee3aa995-5284-40cc-a8cc-8c0777c3f43b","create":"2022-01-09 21:22:49.903","expiration":"2022-01-10 00:22:49.902","bytes":35257933,"seriesId":1641763369954,"init_refresh_job_id":"1e24add5-a90f-dc43-9b05-eb39a09e3e00","series_ordinal":0,"join_analysis":"{\"joinTables\":[{\"tableId\":0,\"tableSchemaPath\":[\"es\",\"persons\",\"doc\"]}]}","state":"DEPRECATED","failure_msg":"NONE","data_partitions":"","last_refresh_from_pds":"2022-01-09 21:22:49.902"}
{"reflection_id":"54a3b73f-cb6b-4a14-b5a7-4a7021826cda","materialization_id":"ff917cba-77c6-417b-af02-f243de9bc917","create":"2022-01-05 06:21:27.163","expiration":"2022-01-05 09:21:27.163","bytes":35220596,"seriesId":1641363687234,"init_refresh_job_id":"1e2ac717-f039-7b0f-c3bb-0ea8da552a00","series_ordinal":0,"join_analysis":"{\"joinTables\":[{\"tableId\":0,\"tableSchemaPath\":[\"es\",\"persons\",\"doc\"]}]}","state":"DELETED","failure_msg":"NONE","data_partitions":"","last_refresh_from_pds":"2022-01-05 06:21:27.163"}

look forward to your reply again.

@thirdparty-core I do not see the materialization ID used in the query under sys.materializations, any chance you can re-run the query again and see if it uses “95f79b9d-7f6b-4f53-93f0-b65375b6f19e” and the reflection details are printed under the acceleration tab

Hi, @balaji.ramaswamy
As shown in my last reply, when querying 'select * from sys.materializations where reflection_id = ‘54a3b73f-cb6b-4a14-b5a7-4a7021826cda’, there is a record for materialization ID 95f79b9d-7f6b-4f53-93f0-b65375b6f19e.

However, when I re-query, the record with materialization ID 95f79b9d-7f6b-4f53-93f0-b65375b6f19e is gone.

I didn’t delete my cluster data.

I have tried to use the command mvn clean install -DskipTests when packaging, and did the deployment and query of the same environment, and the result did not appear that the problems we discussed above exist.

Did adding the parameter ‘-Ddremio.oss-only=true’ when compiling and packaging cause this exception? Because I have noticed that this problem exists in version 18 and version 19.
Are there any specific diagnostic steps that can help me resolve this issue? Although it’s just a UI display issue.

Best wishes and look forward to hearing from you again.

@thirdparty-core

Would you be able to download the community edition and see if the problem exists?

@balaji.ramaswamy the community edition is ok。
Then I’ll find out if there is something wrong with my own compilation.
Thanks for your participation.

Good luck.