:wave: Hello! I'm new to Airbyte and doing a spike...
# replication-troubleshooting
j
👋 Hello! I'm new to Airbyte and doing a spike right now, having some trouble connecting to a MongoDB source (hosted on Atlas). The error I'm running into is
Unable to execute any operation on the source!
- if anyone has ideas on what might be causing that I'd appreciate any pointers here. Thanks!
n
Hey Jake! Could you include the full logs? I need more info to understand what's happening here.
j
Hey Nataly, I actually just figured it out - totally user error on my part! (I had the wrong database name) Perhaps you can help me with my next question. I am using Snowflake as my destination, and I'd like each connection to use a separate schema within the
AIRBYTE
database - how can I configure this?
u
Could you elaborate on what the error was and how you fixed it? That would help future users :) To make sure I understand: you want to make multiple connectors for the same Snowflake instance but use separate schemas for each connector? If that's correct, that's not currently possible, but feel free to make a feature request on GitHub
j
When testing my new mongodb connection I was getting this error:
Copy code
Check connection job received output: io.airbyte.config.StandardCheckConnectionOutput@1b1abc35[status=failed,message=Message: Unable to execute any operation on the source!]
I was connecting to a dev cluster, and had a
-dev
suffix on my database name, which caused the error. The configured database did not exist.
u
Thanks!
j
I wonder how other folks are handling multiple sources -> snowflake without being able to specify the schema? If thats not a feature right now, I think there are 2 possible options: 1. Specify a table prefix 2. Create each schema manually and configure multiple destinations (this seems messy)
I have multiple source systems, each has a
user
table, ideally those tables would land in
AIRBYTE.{SOURCE_NAME}.USERS
but it seems like the current functionality only allows for
AIRBYTE.PUBLIC.{SOURCE_NAME}_USERS
assuming the snowflake connector is configured to use the PUBLIC schema?
n
Currently you have to specify a default schema when setting up a Snowflake connector, so you wouldn't be able to skip that and not specify it. To your second comment - yes, that's the current functionality. Please feel free to make feature requests on GitHub!
j
So 'default schema' really just means 'schema' since it can't be overridden. The language is a little confusing IMO.
n
Yes, that's correct. Feel free to submit a documentation issue on GitHub too!