-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[low-code-connectors] Replace JelloExtractor with DpathExtractor #15514
Conversation
"_", | ||
None, | ||
[], | ||
[], |
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.
the returned value is [{}]
without the fix
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.
could you document this behavior in the record selector docs section and docstrings?
on your PR description note: maybe dpath is really the way to go and we're making this too complicated for ourselves. It seems the contract might more easily just be:
- either there is a single JSON returned from the response, in which case wrap it in
[]
- there are many responses returned, in which case point to an array field containing that data
like we discussed though i'd rather wrap up the CDK work for the week and call that change a follow up
airbyte-cdk/python/airbyte_cdk/sources/declarative/extractors/jello.py
Outdated
Show resolved
Hide resolved
airbyte-cdk/python/airbyte_cdk/sources/declarative/extractors/record_selector.py
Outdated
Show resolved
Hide resolved
…jello.py Co-authored-by: Sherif A. Nada <[email protected]>
…record_selector.py Co-authored-by: Sherif A. Nada <[email protected]>
from airbyte_cdk.sources.declarative.interpolation.interpolated_string import InterpolatedString | ||
from airbyte_cdk.sources.declarative.types import Config, Record | ||
from dataclasses_jsonschema import JsonSchemaMixin | ||
from jello import lib as jello_lib | ||
|
||
|
||
@dataclass | ||
class JelloExtractor(JsonSchemaMixin): | ||
class JelloExtractor(RecordExtractor, JsonSchemaMixin): |
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.
We can delete this class in a follow up PR
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.
LGTM but Why not make dpath the default?
@@ -50,11 +52,12 @@ | |||
InterpolatedString: InterpolatedString, | |||
MinMaxDatetime: MinMaxDatetime, | |||
Paginator: NoPagination, | |||
ParentStreamConfig: ParentStreamConfig, | |||
RecordExtractor: JelloExtractor, |
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.
should this be the Dpath one instead?
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.
yes, done
/publish-cdk dry-run=false |
/publish-cdk dry-run=false |
/publish-cdk dry-run=false
|
What
Replace JelloExtractor with DpathExtractor which has a simple contract.
How
RecordExtractor
interface, which JelloExtractor implementsDpathExtractor
which implementsRecordExtractor
and usesdpath.util.get
to extract records from the decoded responseTesting
Recommended reading order
airbyte-cdk/python/airbyte_cdk/sources/declarative/extractors/record_extractor.py
airbyte-cdk/python/airbyte_cdk/sources/declarative/extractors/dpath_extractor.py
airbyte-cdk/python/unit_tests/sources/declarative/extractors/test_dpath_extractor.py
airbyte-cdk/python/airbyte_cdk/sources/declarative/extractors/record_selector.py
airbyte-cdk/python/unit_tests/sources/declarative/extractors/test_record_selector.py
airbyte-cdk/python/airbyte_cdk/sources/declarative/extractors/jello.py
airbyte-cdk/python/unit_tests/sources/declarative/extractors/test_jello.py
Follow up items
🚨 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.