0884fa74a6
* Additinal details about Windows specific long filename error during cloning * Corrected the path * Revert "Corrected the path" This reverts commitbbd3b78fcb. * Revert "Additinal details about Windows specific long filename error during cloning" This reverts commit0b695eea1a. * Email is mandatory 'Specify your preferences', Link to docker inst guide * Use relative paths while linking * Typo in Destination section * On Windows, fixing long filename error during cloning * For Windows with WSL2 and Docker, clarify steps to locate destination local folder * Link to locating local files on Windows * Update docs/contributing-to-airbyte/updating-documentation.md Co-authored-by: Abhi Vaidyanatha <abhi@airbyte.io> * Update docs/quickstart/set-up-a-connection.md Co-authored-by: Abhi Vaidyanatha <abhi@airbyte.io> * Update docs/examples/postgres-replication.md Co-authored-by: Abhi Vaidyanatha <abhi@airbyte.io> * Update docs/examples/postgres-replication.md Co-authored-by: Abhi Vaidyanatha <abhi@airbyte.io> * Update docs/examples/postgres-replication.md Co-authored-by: Abhi Vaidyanatha <abhi@airbyte.io> * Update docs/deploying-airbyte/local-deployment.md Co-authored-by: Abhi Vaidyanatha <abhi@airbyte.io> * Update docs/deploying-airbyte/local-deployment.md Co-authored-by: Abhi Vaidyanatha <abhi@airbyte.io> Co-authored-by: Patali, Prashanth <ppatali@hidglobal.com> Co-authored-by: Abhi Vaidyanatha <abhi@airbyte.io>
2.2 KiB
Set up a Connection
When we create the connection, we can select which data stream we want to replicate. We can also select if we want an incremental replication. The replication will run at the specified sync frequency.
To set it up, just follow the instructions on the screenshot below.
Check the logs of your first sync
After you've completed the onboarding, you will be redirected to the source list and will see the source you just added. Click on it to find more information about it. You will now see all the destinations connected to that source. Click on it and you will see the sync history.
From there, you can look at the logs, download them, force a sync and adjust the configuration of your connection.
Check the data of your first sync
Now let's verify that this worked:
cat /tmp/airbyte_local/json_data/_airbyte_raw_exchange_rate.jsonl
You should see one line for each day that was replicated.
If you have jq installed, let's look at the evolution of EUR.
cat /tmp/airbyte_local/test_json/_airbyte_raw_exchange_rate.jsonl |
jq -c '.data | {date: .date, EUR: .EUR }'
And there you have it. You've pulled data from an API directly into a file and all of the actual configuration for this replication only took place in the UI.
Note: If you are using Airbyte on Windows with WSL2 and Docker, refer to this tutorial or this section in the local-json destination guide to locate the replicated folder and file.
That's it!
This is just the beginning of using Airbyte. We support a large collection of sources and destinations. You can even contribute your own.
If you have any questions at all, please reach out to us on Slack. We’re still in alpha, so if you see any rough edges or want to request a connector you need, please create an issue on our Github or leave a thumbs up on an existing issue.
Thank you and we hope you enjoy using Airbyte.