Query editor v2 on Redshift show Error:Parsed manifest is not a valid JSON object

Hello,

This issue usually happens for a couple of reasons.

1. Table associated with the database might not have the permissions to allow the specified user, querying the table, to perform the necessary Lake Formation actions. Granting the user who executes the query, to needed Lake Formation permissions on the given table for the database might fix the issue.
2. Table that had been created with their LOCATION set to a specific file in an S3 path (rather than an S3 path prefix) might fail with above error. Based on this I would recommend placing the files for each table into separate subfolders(instead of specific file) to make the data queryable as described in this article

To recrawl the s3 data source with specific s3 prefix as shown below,

1. Navigate to the Glue Crawler Page.

2. Click on Create Crawler, and enter a crawler name and click Next.

3. Click on Add a Data Source.

4. Choose S3 as the data source and the include path of your files 's3://<bucket-name>/data_table/' (Please note that folder 'data_table' contains source files) and click on Update S3 data source. Click Next

5. Create an IAM Role and enter a name and click Next.

6. Click on Add database and enter a database name.

7. Select Run on demand for the frequency and click Next.

8. Select all remaining defaults. Once the Crawler has been created, click on Run Crawler.

9. Once the Crawler has completed its run, you will see a new table in the Glue Catalo

10. Run 'Select' command in Redshift

Reference here