Releases: jitsucom/jitsu
Jitsu 1.44.4
This hotfix release includes the following changes:
Global destination feature
In multi-project setups it is now possible to select a 'global destination' that will capture events from all API keys in all projects.
Read more
Other changes
Jitsu 1.44.3
This hotfix release includes the following changes:
- Fixed bug that could lead to loss of events for streaming destination during config update.
- #1007 Google Sheets source: deprecate Singer based source in favor of Airbyte version
- Added Facebook Pages airbyte source
- Added SFTP and SFTP Bulk airbyte source connectors
Jitsu 1.44.2
This hotfix release includes the following changes:
- #1006 Facebook Marketing Source: upgrade API to v16
- Snowflake destination: respect max allowed SQL query length and payload size
- Snowflake destination: quote reserved words for column names
Jitsu 1.44.1
This hotfix release includes the following changes:
- Auth0 SSO: /api/v1/users/info response is enriched with sso provider's profile data
- Merged #1003 PR that made possible to use auth0 SSO service for other OIDC providers
Jitsu 1.44.0
We're pleased to announce Jitsu v1.44 with following changes:
Google Ads Source switched to API v13:
Google Ads API v11 will stop accepting requests starting March 29, 2023. In JItsu 1.44 we have upgraded protocol version to v13.
Please update your Jitsu version if you are using Google Ads source.
With protocol upgrade Google changed the list of supported resources and fields. After update please check source task logs for errors – it may be necessary to remove fields that is no longer supported from queries.
'Fetch' support in JavaScript transformations
Added support for fetch
method in destination transformation code. For example, now it is possible to use external resources to make a decision what to do with event or to enrich event with extra data
Other changes
- Google Ads Source: fixed bug when it wasn't possible to sync more than 10000 rows per collections
- Google Analytics Source UI: added support for custom dimensions and metrics
- #979 Snowflake Destination: removed redundant query in table existence check step to reduce usage costs
- #979 Snowflake Destination: added
snowflake.always_cache_schema: true
option to enable table schema caching in batch mode. That may reduce usage costs a bit more - #978 Added additional date format to increase flexibility of parsing date values coming from different sources
- #994 Added
transform.log.level: info
option to direct console.log from transformation to jitsu main log - Experimental Source Transformation: added readonly parameter
JITSU_TABLE_NAME
to object that helps to distinguish what collection event is coming from
Jitsu 1.43.6
This hotfix release includes the following fixes:
- Auth0 SSO: fix authorization error that happens on some providers with large profile object
- Configurator API: properly pass clickhouse destination's custom engine fields to server
Jitsu 1.43.5
This hotfix release includes the following fixes:
- Google Analytics source: use correct data types for integer and float metrics instead of strings (applied to newly created tables only)
- Logging: Introduce config variable 'max_file_size_mb' to control max size that log file can reach before gets rotated. E.g.:
server.log.max_file_size_mb
- Added Elasticsearch destination community plugin
Jitsu 1.43.4 (reuploaded)
Reuploaded: Initial 1.43.4 docker images were shipped with UI initialization bug, but was shortly replaced with fixed one. If affected please refresh the image: docker pull jitsucom/jitsu:latest
This hotfix release includes the following changes:
- SSO: support for Auth0 service. Read more
- Source UI: Added "Cron expression" option for configuring source schedule time.
- MongoDB v2 source: primary key column now uses value of object's '_id' column
Jitsu 1.43.3
This hotfix release includes the following changes:
Experimental Sources transformation
Added experimental JavaScript transformation for Sources data. Can be enabled with experimental.source_transform_enabled: true
yaml property or EXPERIMENTAL_SOURCE_TRANSFORM_ENABLED=true
environment variable.
If one destination ingests data from multiple Sources and API-Keys, the same JavaScript code will be applied to all kinds of data.
In this case it may be required to distinguish what source each particular object is coming from by properties of that object.
For that purpose _source_id
property was added for all data ingested from sources
Other changes
- Don't treat cases when API-Key has no linked destinations yet as errors.
Jitsu 1.43.2
This hotfix release includes the following fixes:
- Configurator UI: Added support for
JITSU_SERVER_PUBLIC_URL
environment variable to customize jitsu server URL offered in Onboarding tour and ApiKey connection docs snippets