How to deal with sourceErrorCode: EMPTY_OUTPUT_COLUMN_LIST

Question & Answer
,
1

I encounter this on occasion when using custom SQL, at which point I’m unable to debug and have to redesign my entire script:

Screen Shot 2022-05-05 at 9.36.38 PM

Screen Shot 2022-05-05 at 9.36.50 PM

What is the underlying issue in plain English that I can actually debug? I don’t have access to the underlying RDS instance since it’s embedded Quicksight.

Thanks,

2

Hi, where do you experience this error? during analysis/visual creation time or during data prep edit or during calculated field creation time?

3

I am also facing the same issue during data prep ‘Edit Dataset’ stage.

4

During the data prep edit.

5

The first time this occurred, I had several CTEs with aliases on the final final query such as:

SELECT
    colname AS "Column Name"
...

By removing the alias it worked. In other instances, once the error occurred I got around it by simply copying and pasting the entire script as is into a new dataset custom SQL and it worked, but no matter what once the original dataset showed the error it would never work again.

6

Thank you for letting us know. I would recommend filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a support case (Creating support cases and case management - AWS Support). If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf. Hope this helps!