-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Making introspection more efficient #36
Open
nidhi-akkio
wants to merge
9
commits into
MeltanoLabs:main
Choose a base branch
from
akkio-inc:fixing-introspection
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
3c77f52
fix
c4cd6ac
test-commit
nidhi-akkio 6a52fe1
adding logging
nidhi-akkio 081bfb5
fixed import
nidhi-akkio 0ba04c9
test. must revert
nidhi-akkio 1be1eb0
remove logging
nidhi-akkio 63059c2
adding logging again
nidhi-akkio 78fa22b
added self.logger
nidhi-akkio 6abc66e
done
nidhi-akkio File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@edgarrmondragon I'm curious what you think about this. I know the schema setting was documented to be the schema used to connect to the database but not necessarily meant to be a filter for only data in that database. It seems like this PR would implement it to only consider data in the configured schema.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, is there an update on this? We would really like to merge this in asap.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@edgarrmondragon ping on the previous message in case you have thoughts but we mentioned it in office hours and it looks like this is implementation specific and not related to the SDK as I originally thought.
@nidhi-akkio sorry about the delay. A few more comments but I think we can get this merged soon.
This is a of breaking change for some users who assigned a schema to use for connecting but are expecting the status quo where its not using it for filtering. If they upgrade they'll silently stop syncing tables outside this schema. We can either:
schema_filter
. Avoiding breaking changes but likely making the difference between the 2 options confusing for users, althoughschema
in its current state is already confusing to me 😅 .@nidhi-akkio @edgarrmondragon what do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think, like you say @pnadolny13, that the current usage and description of the
schema
setting, i.e.The initial schema for the Snowflake session.
is rather confusing.My preference would be to not introduce a breaking change, add a new setting
schema_filter
and think about what to do with the existingschema
setting.cc @nidhi-akkio