-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
🐛 Source S3: Check config settings for CSV file format #20262
Conversation
/test connector=connectors/source-s3
Build FailedTest summary info:
|
/test connector=connectors/source-s3
Build PassedTest summary info:
|
@@ -59,6 +59,7 @@ def check_connection(self, logger: AirbyteLogger, config: Mapping[str, Any]) -> | |||
The error object will be cast to string to display the problem to the user. | |||
""" | |||
try: | |||
self.stream_class(**config)._get_master_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.
This could take way too much time if user has thousands of lines in their files. I believe check should be pretty fast. As an option, could we try doing the same just for a small chunk of data in each of the files?
airbyte-integrations/connectors/source-s3/source_s3/source_files_abstract/source.py
Outdated
Show resolved
Hide resolved
airbyte-integrations/connectors/source-s3/source_s3/source_files_abstract/source.py
Outdated
Show resolved
Hide resolved
/publish connector=connectors/source-s3
if you have connectors that successfully published but failed definition generation, follow step 4 here |
/publish connector=connectors/source-s3
if you have connectors that successfully published but failed definition generation, follow step 4 here |
/publish connector=connectors/source-s3
if you have connectors that successfully published but failed definition generation, follow step 4 here |
/publish connector=connectors/source-s3
if you have connectors that successfully published but failed definition generation, follow step 4 here |
/publish connector=connectors/source-s3
if you have connectors that successfully published but failed definition generation, follow step 4 here |
What
Resolving OC #1164 . Check that file can be readed properly.
How
read schema on check_connection
Recommended reading order
x.java
y.python
🚨 User Impact 🚨
Are there any breaking changes? What is the end result perceived by the user? If yes, please merge this PR with the 🚨🚨 emoji so changelog authors can further highlight this if needed.
Pre-merge Checklist
Expand the relevant checklist and delete the others.
New Connector
Community member or Airbyter
airbyte_secret
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
.README.md
bootstrap.md
. See description and examplesdocs/integrations/<source or destination>/<name>.md
including changelog. See changelog exampledocs/integrations/README.md
airbyte-integrations/builds.md
Airbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
/test connector=connectors/<name>
command is passing/publish
command described hereUpdating a connector
Community member or Airbyter
airbyte_secret
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
.README.md
bootstrap.md
. See description and examplesdocs/integrations/<source or destination>/<name>.md
including changelog. See changelog exampleAirbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
/test connector=connectors/<name>
command is passing/publish
command described hereConnector Generator
-scaffold
in their name) have been updated with the latest scaffold by running./gradlew :airbyte-integrations:connector-templates:generator:testScaffoldTemplates
then checking in your changesTests
Unit
Put your unit tests output here.
Integration
Put your integration tests output here.
Acceptance
Put your acceptance tests output here.