- Newest
- Most votes
- Most comments
Hello,
I understand that you are getting the below timeout error when working with QuickSight . Additionally, you cannot create a new data source with customSQL, but with SPICE.
sourceErrorCode:DATA_SOURCE_TIMEOUT sourceErrorMessage:Server execution exceeded 46 seconds, which is calculated based on client TTL and service config
Please note that the current time limit for executing query/ listing tables from data source is 50 seconds in QuickSight, which results in the ‘Connection timed out’ message being displayed in the QuickSight console. There is usually 46s left for server to execute the query after subtracting network transmission time.
When using SPICE, the queries process faster, which is most likely the reason why you did not get the error [1].
To resolve this issue you may consider either of the following:
- Limit the data that you're importing
- Unselect columns that you don't need.
- Add filters to your dataset in QuickSight.
- Use predicates in your custom SQL query such as WHERE and HAVING.
- Import the data into SPICE
You may refer to AWS Blog on how to resolve query timeout issues in QuickSight [2].
I hope you find the above information helpful.
Have a great day further!
References:
[1] https://docs.aws.amazon.com/quicksight/latest/user/spice.html [2] https://repost.aws/knowledge-center/quicksight-resolve-query-timeout-issues
I have been through this error. How I have troubleshooted it is, try to find the query which is creating this time out error. For my case I have 15 query lines in my Main query, I tried to sort it by first 5 and then next 5. I found that last 2 queries were responsible for the error. Also, remove "*" from you query and try to minimize your query result fields.
Ex. SELECT attributes.lex_intent, attributes.wrap_up_code, FROM "cl-connect-database"."cl-connect_stream_storage"
Instead of
SELECT attributes.lex_intent, attributes.wrap_up_code,
- FROM "cl-connect-database"."cl-connect_stream_storage"
As Athena and Quicksight both have different technology to process the data, we need to limit our query in Quicksight. Also you use calculated fields for processing data within the Quicksight after your attach the dataset.
Relevant content
- asked a year ago
- asked 9 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago