Redshift Federated Query Error Code 25000

Question

We're trying to get the new Redshift federated query service set up to allow us to query across multiple Redshift clusters. We've followed the documentation in setting up the IAM roles properly and external schemas created on the target cluster. But, when we execute a query against the remote cluster we're consistently getting the following error. Setup details and sample query are below the error. Has anyone else seen this? What are we missing or what's a workaround?  
  
Worth noting that the query never seems to make it to the remote cluster.  
  
Thanks!  
  
ERROR:  
  -----------------------------------------------  
  error:  3 is outside the valid range for parameter "extra_float_digits" (-15 .. 2)  
  code:      25000  
  context:  
  query:     0  
  location:  pgclient.cpp:623  
  process:   padbmaster \[pid=10871]  
  
Here is essentially what we did for setup of the external schema (all names changed for confidentiality purposes):  
  
CREATE EXTERNAL SCHEMA IF NOT EXISTS myextschema  
FROM POSTGRES  
DATABASE 'mydb' SCHEMA 'remoteschema'  
URI 'xxxxxxxxxxxxxxxx' PORT 5439  
IAM_ROLE 'arn:aws:iam::xxxxxxxx:role/MyRole'  
SECRET_ARN 'arn:aws:secretsmanager:xxxxxxxxxx';  
  
-- Validated the external schema got created  
SELECT * FROM svv_external_schemas;  
  
-- Execute a simple query hitting the remote cluster  
SELECT 1  
FROM    myextschema.remotetablename;  
  
Edited by: asidari-sp on Jun 3, 2020 3:22 PM  
  
Edited by: asidari-sp on Jun 3, 2020 3:23 PM  
  
Edited by: asidari-sp on Jun 3, 2020 3:24 PM

Accepted Answer

Federated Query does not currently support connections to other Redshift clusters.   
> Federated queries can work with external databases in Amazon RDS for PostgreSQL and Amazon Aurora with PostgreSQL compatibility.  
https://docs.aws.amazon.com/redshift/latest/dg/federated-overview.html  
  
We will consider adding this to our roadmap. When new features are released they are noted in our regular maintenance announcements at the top of the forum.

Answer

Thanks Joe - this was resolved by enabling "Enhanced VPC Routing" on the cluster and resolving our routing.

Answer

Excellent. Thanks for confirming. That may help others.

Answer

Thank you! Also confirming that it helped me to solve the issue. It didn't work immediately after enabling "Enhanced VPC Routing" so I still had to check the route tables, I found an issue there and after establishing correct route, it worked cross accounts.  
  
Edited by: olegAW5 on Sep 12, 2021 4:20 AM

Answer

We're seeing this same error. We're not trying to run a federated query from redshift to redshift but instead trying to access an RDS aurora instance from a different account. The accounts are linked and the VPCs are peered. The error is kind of cryptic here... @Joe any ideas on how to proceed troubleshooting this issue?  
  
ERROR:    
  -----------------------------------------------  
  error:  timeout expired  
  
  code:      25000  
  context:     
  query:     0  
  location:  pgclient.cpp:433  
  process:   padbmaster \[pid=16218]  
  -----------------------------------------------

Answer

Hi, I just wanted to say that our team was experiencing the exact same issue and enabling "Enhanced VPC Routing" worked. Thanks!  
  
Btw I wish the AWS docs here were more clear: https://docs.aws.amazon.com/redshift/latest/dg/getting-started-federated.html. My teams RDS instance was in the same VPC and subnet group as our Redshift cluster so we skipped over this step in the docs.

Answer

Recommend raising your issue with the AWS Support organization. They're equipped to immediately review your specific resources and provide further assistance.   
https://console.aws.amazon.com/support/home#/  
  
Once your issue is resolved, please feel free to update this thread if you think the solution would be generally applicable to others encountering the same behavior.

Answer

Seems no one else has experienced this issue. Has anyone been able to configure and use the federated query service across Redshift clusters.  
  
I've filed a support case for our specific issue but haven't gotten a response yet, unfortunately.

Redshift Federated Query Error Code 25000

Conteúdo relevante