I have a large number of views, ~ 20k. I suspect w...
# replication-troubleshooting
r
I have a large number of views, ~ 20k. I suspect when doing a discover_schema I’m getting a timeout error based on the error below. Is there a way to ignore views on schema discovery for a postgres db?
Copy code
airbyte-server                      | Feb 03, 2023 9:57:20 PM org.glassfish.jersey.server.ServerRuntime$Responder writeResponse
airbyte-server                      | SEVERE: An I/O error has occurred while writing a response message entity to the container output stream.
airbyte-server                      | org.glassfish.jersey.server.internal.process.MappableException: org.eclipse.jetty.io.EofException
j
Could you put your views in a different schema?
You can filter what airbyte can see two ways, limit what the airbyte user can even see, or limit the schema's it pulls here:
If going the grants direction, don't grant the user select on schema, grant them select on object1, object2, object3.. objectn.
n
Rocky, let me know if Jordan's suggestion helps!
r
It was a staging environment so we dropped views we didn’t need. In the future though, will grant select on the objects that we want to EL only. Note: this seems rather cumbersome, any reason not to increase the schema discovery time here?
j
When the airbyte-nginx basic auth was put in, it seemed all requests were hit by a basic timeout. Since then, a version was put out with an environment variable for timeout. Could look in there maybe, see if you can increase it.
r
Are you referring to this environment variable?
Copy code
$ grep BASIC_AUTH_PROXY_TIMEOUT .env
BASIC_AUTH_PROXY_TIMEOUT=600