-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
configuration documentation #5
Conversation
ac1269f
to
19108df
Compare
|
||
Fivetran has a similar feature, where at configuration time, it detects the scheme of the data source and allows a user to select a subset of the columns discovered. | ||
|
||
## Source |
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.
Can we add a section about supported sources/destinations? here are some imo good MVP candidates:
Sources:
- Postgres
- S3 CSV
- MySQL
Destinations:
- BigQuery
- RedShift
- Postgres
- MySQL
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 should also have one SaaS source
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 goal here is to describe how configuration works, can we keep this conversation in the reqs doc: https://docs.google.com/document/d/1X6M3qhbg9E9adykdI8KmO3xV7mr0XK7O3jLbN5Z7ydw/edit#?
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.
Left some comments, might have some more tomorrow when I've had some time to think about it
docs/configuration_data_model.md
Outdated
}, | ||
"dataType": { | ||
"type": "string", | ||
"enum": ["string", "number", "uuid", "boolean"] |
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 enum seems overly restrictive since we could custom data types e.g: postgres dates or json blobs. What is the value of making this an enum vs. having it be a string? Or are we pooling anything that isn't a uuid/number/boolean into string? in that case, should uuid also be pooled into string?
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.
good question. the value of having these be an enum in the future is that we can make sure we are matching up columns in different tables that are compatible. like recognize if we are piping a uuid into a string column is maybe not what we want to do. for right now it doesn't matter probably?
i was being lazy when i wrote this enum, just putting in values as an example; i would definitely include more types.
i think defining our own types will probably be valuable at some point, but kinda ambivalent as to whether we need to do it MVP or do what you said and just use strings. what would your preference be @sherifnada ?
* Receive feedback on whether Dataline was able to reach the source with the given credentials. | ||
* Insert credentials for a destination. | ||
* Receive feedback on whether Dataline was able to reach the destination with the given credentials. | ||
* Show intent to connect source to destination. |
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.
What does this point mean?
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.
lol. yeah awkward phrasing. all steps so far have just been source or destination. this step is where you say i want to connect source X to destination Y.
* Show intent to connect source to destination. | ||
* Receives schema of the source. | ||
* Selects which part of the schema will be synced. | ||
* Triggers a manual sync or inputs schedule on which syncs should take place. |
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.
in the case the user triggers a manual sync, is this saying the line would be a one-time transient transfer?
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.
it would just attempt to run a sync (using whatever existing configuration is, full_refresh or append).
docs/configuration_data_model.md
Outdated
|
||
### Conduit Types | ||
|
||
#### StandardConduitConfiguration |
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.
Why the Standard
prefix?
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.
as in you don't think this should be the same across all taps. what parts do you think can't be standardized? i think the goal here is to try to get the conduit configuration to be the mode (which is standard) and the part of the schema that we want to sync (which is standardized in tables/columns).
docs/configuration_data_model.md
Outdated
Configuration that is the SAME for all tap / target combinations. Describes the sync mode (full refresh or append) as well what part of the schema will be synced. | ||
|
||
```json | ||
{ |
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 also have a handle to source and destination?
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.
yeah... i actually all of these input configs are missing sourceId or destinationId. do you have an opinion about putting these in the configs versus just adding them to interface of the methods. (e.g. sync(sourceId, destinationId, etc...)
). i'm a little inclined to take this approach since ConnectionConfiguration
is not standard. if we did add the id to the configs, then we would maybe need to add a StandardConnectionConfiguration
as well.
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.
talked offline. i will add the source destination id into the objects.
|
||
1. Add a source _without_ needing to write HTML. They should be responsible for only 2 things: | ||
1. Define Configuration: define a json object which describes which properties need to be collected by a user. Then the UI figures out how to render it. | ||
1. Implement: `testConnection`, `discoverSchema`, and `sync`. These functions should only rely on the configurations defined in the json and should return objects that match the interfaces that are described below. |
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 wonder if we should are more granularity in the sync
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.
can you say more? you think the configuration should be more granular? or are you talking about splitting up the steps in the sync step more? if the latter, we can figure that out in sherif's work doc.
|
||
Fivetran has a similar feature, where at configuration time, it detects the scheme of the data source and allows a user to select a subset of the columns discovered. | ||
|
||
## Source |
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 should also have one SaaS source
} | ||
``` | ||
|
||
#### StandardConnectionStatus |
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.
Why is it prefixed with Standard?
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.
so the configuration for a connection is not standard, but i was imagining that when you implement a test connection check you need to return something against a standard interface (i.e. it connected or it didn't). is there something you feel is non standard here?
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.
or is the question just what standard
means? it means it's a configuration / interface that is the same for all taps or targets.
8fc2613
to
da5d407
Compare
da5d407
to
01c3ec4
Compare
…-dbt Bump Redshift No DBT version
Feat/source shipstation
* Replaced sidebar menu with headlessui * Removed unnecessary tag li * Removed unnecessary Sidebar Popout * Changed export type * Added keyboard support * Removed styled-components * Removed commented code * Disabled ESLint rule css-modules/no-undef-class * Review fixes * Fixed shorthand property * Review fixes * Review fixes #2 * Review fixes #3 * Review fixes #4 * Review fixes #5 * Review fixes #6 * Review fixes #7 * Update airbyte-webapp/src/packages/cloud/views/layout/SideBar/SideBar.module.scss Co-authored-by: Vladimir <[email protected]> * Update airbyte-webapp/src/packages/cloud/views/layout/SideBar/SideBar.module.scss Co-authored-by: Vladimir <[email protected]> Co-authored-by: Vladimir <[email protected]>
* Replaced sidebar menu with headlessui * Removed unnecessary tag li * Removed unnecessary Sidebar Popout * Changed export type * Added keyboard support * Removed styled-components * Removed commented code * Disabled ESLint rule css-modules/no-undef-class * Review fixes * Fixed shorthand property * Review fixes * Review fixes airbytehq#2 * Review fixes airbytehq#3 * Review fixes airbytehq#4 * Review fixes airbytehq#5 * Review fixes airbytehq#6 * Review fixes airbytehq#7 * Update airbyte-webapp/src/packages/cloud/views/layout/SideBar/SideBar.module.scss Co-authored-by: Vladimir <[email protected]> * Update airbyte-webapp/src/packages/cloud/views/layout/SideBar/SideBar.module.scss Co-authored-by: Vladimir <[email protected]> Co-authored-by: Vladimir <[email protected]>
* Replaced sidebar menu with headlessui * Removed unnecessary tag li * Removed unnecessary Sidebar Popout * Changed export type * Added keyboard support * Removed styled-components * Removed commented code * Disabled ESLint rule css-modules/no-undef-class * Review fixes * Fixed shorthand property * Review fixes * Review fixes airbytehq#2 * Review fixes airbytehq#3 * Review fixes airbytehq#4 * Review fixes airbytehq#5 * Review fixes airbytehq#6 * Review fixes airbytehq#7 * Update airbyte-webapp/src/packages/cloud/views/layout/SideBar/SideBar.module.scss Co-authored-by: Vladimir <[email protected]> * Update airbyte-webapp/src/packages/cloud/views/layout/SideBar/SideBar.module.scss Co-authored-by: Vladimir <[email protected]> Co-authored-by: Vladimir <[email protected]>
initial files for source walmart seller
* https://prima-assicurazioni-spa.myjetbrains.com/youtrack/issue/SSDP-165/Enable-schema-evolution-in-the-Airbyte-Databricks-connector * bump minor version * bump minor version * Edit connector doc
…Merge) #26658 (#26942) * https://prima-assicurazioni-spa.myjetbrains.com/youtrack/issue/SSDP-165/Enable-schema-evolution-in-the-Airbyte-Databricks-connector (#1) * Ssdp 165/enable schema evolution in the airbyte databricks connector (#4) * https://prima-assicurazioni-spa.myjetbrains.com/youtrack/issue/SSDP-165/Enable-schema-evolution-in-the-Airbyte-Databricks-connector * bump minor version * bump minor version * Ssdp 165/add doc (#5) * https://prima-assicurazioni-spa.myjetbrains.com/youtrack/issue/SSDP-165/Enable-schema-evolution-in-the-Airbyte-Databricks-connector * bump minor version * bump minor version * Edit connector doc
Doc that tries to enumerate the requirements for the source side of our product. Proposes what configuration needs to be taken in. Still rough, but hopefully enough to push the conversation forwards.