Skip to content
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

🎉Destination-s3: added support for AWS Glue crawler #11173

Conversation

etsybaev
Copy link
Contributor

@etsybaev etsybaev commented Mar 15, 2022

What

A user wants to use the AWS Glue crawler feature, but currently, all special symbols transform to "_" symbol.

How

Updated logic to do not transform special symbols in stream name if user adds the "=" symbol in prefix.

Tested locally:
Selection_041

Selection_042

🚨 User Impact 🚨

No breaking changes expected

Pre-merge Checklist

Expand the relevant checklist and delete the others.

New Connector

Community member or Airbyter

  • Community member? Grant edit access to maintainers (instructions)
  • Secrets in the connector's spec are annotated with airbyte_secret
  • Unit & integration tests added and passing. Community members, please provide proof of success locally e.g: screenshot or copy-paste unit, integration, and acceptance test output. To run acceptance tests for a Python connector, follow instructions in the README. For java connectors run ./gradlew :airbyte-integrations:connectors:<name>:integrationTest.
  • Code reviews completed
  • Documentation updated
    • Connector's README.md
    • Connector's bootstrap.md. See description and examples
    • docs/SUMMARY.md
    • docs/integrations/<source or destination>/<name>.md including changelog. See changelog example
    • docs/integrations/README.md
    • airbyte-integrations/builds.md
  • PR name follows PR naming conventions

Airbyter

If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.

  • Create a non-forked branch based on this PR and test the below items on it
  • Build is successful
  • If new credentials are required for use in CI, add them to GSM. Instructions.
  • /test connector=connectors/<name> command is passing
  • New Connector version released on Dockerhub by running the /publish command described here
  • After the connector is published, connector added to connector index as described here
  • Seed specs have been re-generated by building the platform and committing the changes to the seed spec files, as described here
Updating a connector

Community member or Airbyter

  • Grant edit access to maintainers (instructions)
  • Secrets in the connector's spec are annotated with airbyte_secret
  • Unit & integration tests added and passing. Community members, please provide proof of success locally e.g: screenshot or copy-paste unit, integration, and acceptance test output. To run acceptance tests for a Python connector, follow instructions in the README. For java connectors run ./gradlew :airbyte-integrations:connectors:<name>:integrationTest.
  • Code reviews completed
  • Documentation updated
    • Connector's README.md
    • Connector's bootstrap.md. See description and examples
    • Changelog updated in docs/integrations/<source or destination>/<name>.md including changelog. See changelog example
  • PR name follows PR naming conventions

Airbyter

If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.

  • Create a non-forked branch based on this PR and test the below items on it
  • Build is successful
  • If new credentials are required for use in CI, add them to GSM. Instructions.
  • /test connector=connectors/<name> command is passing
  • New Connector version released on Dockerhub by running the /publish command described here
  • After the new connector version is published, connector version bumped in the seed directory as described here
  • Seed specs have been re-generated by building the platform and committing the changes to the seed spec files, as described here
Connector Generator
  • Issue acceptance criteria met
  • PR name follows PR naming conventions
  • If adding a new generator, add it to the list of scaffold modules being tested
  • The generator test modules (all connectors with -scaffold in their name) have been updated with the latest scaffold by running ./gradlew :airbyte-integrations:connector-templates:generator:testScaffoldTemplates then checking in your changes
  • Documentation which references the generator is updated as needed

Tests

Unit

Put your unit tests output here.

Integration

Put your integration tests output here.

Acceptance

Put your acceptance tests output here.

@github-actions github-actions bot added the area/connectors Connector related issues label Mar 15, 2022
@etsybaev etsybaev changed the title Destination-s3: added support for AWS Glue crawler 🎉Destination-s3: added support for AWS Glue crawler Mar 15, 2022
@etsybaev
Copy link
Contributor Author

/test connector=connectors/destination-s3

@etsybaev etsybaev temporarily deployed to more-secrets March 16, 2022 11:46 Inactive
@etsybaev etsybaev temporarily deployed to more-secrets March 16, 2022 11:46 Inactive
@etsybaev etsybaev requested review from VitaliiMaltsev and removed request for alexandr-shegeda March 16, 2022 12:39
Copy link
Contributor

@alexandr-shegeda alexandr-shegeda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. please reformat the code and update the related documentation

@etsybaev etsybaev linked an issue Mar 17, 2022 that may be closed by this pull request
@etsybaev etsybaev temporarily deployed to more-secrets March 17, 2022 13:17 Inactive
@etsybaev etsybaev temporarily deployed to more-secrets March 17, 2022 13:17 Inactive
@etsybaev
Copy link
Contributor Author

/test connector=connectors/destination-s3

@etsybaev etsybaev requested a review from girarda March 17, 2022 15:56
@etsybaev
Copy link
Contributor Author

/test connector=connectors/destination-s3

@etsybaev etsybaev marked this pull request as ready for review March 18, 2022 13:18
// more details https://docs.aws.amazon.com/glue/latest/dg/crawler-s3-folder-table-partition.html
paths.add(streamName);
}else {
paths.add(NAME_TRANSFORMER.convertStreamName(streamName));
Copy link
Contributor

@ChristopheDuong ChristopheDuong Mar 21, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't we create a specific NamingConventionTransformer nameTransformer for S3 when instantiating the S3Destination?
It would be S3NameTransformer instead of a generic ExtendedNameTransformer:

public static final ExtendedNameTransformer NAME_TRANSFORMER = new ExtendedNameTransformer();

That would allow us to specify what are the allowed characters in the bucket name/path such as = or other characters, no?
Non-allowed characters are then following the rule:

all special symbols transform to "_" symbol.

Here are some examples of how it's done in other connectors:

Or at least, when we construct the consumer, we pass it to the factory:

WDYT @tuliren?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree. We should hide that complexity in a custom NameTransformer

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as I understood, this converter is used for creating a stream name only. A user wants to use some specific feature([AWS Glue crawler). That's why I removed any auto-replacement if "=" symbol is used

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@etsybaev the logic is sound, but we should encapsulate it into a S3NameTransformer

// more details https://docs.aws.amazon.com/glue/latest/dg/crawler-s3-folder-table-partition.html
paths.add(streamName);
}else {
paths.add(NAME_TRANSFORMER.convertStreamName(streamName));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree. We should hide that complexity in a custom NameTransformer

@etsybaev
Copy link
Contributor Author

etsybaev commented Mar 23, 2022

/test connector=connectors/destination-s3

🕑 connectors/destination-s3 https://github.com/airbytehq/airbyte/actions/runs/2028994172
✅ connectors/destination-s3 https://github.com/airbytehq/airbyte/actions/runs/2028994172
No Python unittests run

@etsybaev etsybaev temporarily deployed to more-secrets March 23, 2022 17:14 Inactive
@etsybaev etsybaev temporarily deployed to more-secrets March 23, 2022 17:14 Inactive
@etsybaev
Copy link
Contributor Author

etsybaev commented Mar 23, 2022

/publish connector=connectors/destination-s3

🕑 connectors/destination-s3 https://github.com/airbytehq/airbyte/actions/runs/2029751587
✅ connectors/destination-s3 https://github.com/airbytehq/airbyte/actions/runs/2029751587

@github-actions github-actions bot added the area/documentation Improvements or additions to documentation label Mar 23, 2022
@etsybaev etsybaev merged commit bf9a189 into master Mar 23, 2022
@etsybaev etsybaev deleted the etsybaev/4654-destination-s3-added-support-for-aws-glue-crawler branch March 23, 2022 18:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/connectors Connector related issues area/documentation Improvements or additions to documentation
Projects
No open projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Destination S3: Allow special chars for table_prefix
5 participants