Skip to content

Commit

Permalink
incorporate more changes
Browse files Browse the repository at this point in the history
  • Loading branch information
fivetran-abdulsalam committed Jun 20, 2024
1 parent 7f97c0c commit f1a4c2f
Showing 1 changed file with 3 additions and 4 deletions.
7 changes: 3 additions & 4 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,6 @@
**ConfigurationForm Changes**
- We have added options to provide default value and placeholder for `Field`.
- We have introduced `FieldSet` support, which allows to group the `Fields` and add visibility condition to control displaying on the form.
- The `FormField` format is updated to support `FieldSet`. A single attribute should be used to assign the regular fields.

**SourceConnector Changes**
- We have removed `LogEntry` from the Update operation. Now, partners can use `STD::OUT` to send logs. For more details, please refer to the [logging](https://github.com/fivetran/fivetran_sdk/blob/main/development-guide.md#logging) section in the SDK Development Guide.
Expand All @@ -15,10 +14,10 @@

**DestinationConnector Changes**
- We have renamed the service definition from `Destination` to `DestinationConnector`.
- A new rpc method `Capabilities` is introduced. This brings the following functionalities:
- Introduced a new rpc method `Capabilities` which brings the following functionalities:
- Adjust column types: Supports optionally adjusting Partner data type for each Fivetran type.
- Define the maximal value supported for the column types.
- We have added support for providing parquet batch files. Now, partner can choose the file type to create batch files.
- Define maximum value supported for the column types.
- We have added support for parquet batch files.
- We have introduced a new field, `supports_history_mode`, which indicates whether the destination supports history mode.
- Changes in `AlterTableRequest`:
- It now uses `table_name` instead of `Table`
Expand Down

0 comments on commit f1a4c2f

Please sign in to comment.