2.1.0

** New Features **

• use newest version for azure-kusto-java (2.1.2)
• support certificate authentication

v2.0.1

Features:

• Added new option
• KUSTO_BLOB_STORAGE_ENDPOINT_SUFFIX "blobStorageEndpointSuffix" - when providing the storage yourself and using storage key for storage parameters, user can provide this option so that the created config will use the right domain
• Better writing for decimal values

Fixes:

• Fixed support for non-public domains - writing and reading

Note:
This goes along with providing login url of the cloud in the environment variable : AadAuthorityUri

v2.0.0

** Breaking Changes **

This release uses the latest Kusto Java SDK v2 which has a new API for querying. This won't be a affect users who do not use the Java SDK itself in their code.

• KUSTO_AAD_CLIENT_ID ('kustoAADClientID') changed to KUSTO_AAD_APP_ID 'kustoAadAppId'
• KUSTO_AAD_CLIENT_PASSWORD ('kustoClientAADClientPassword') changed to KUSTO_AAD_APP_SECRET ('kustoAadAppSecret')
• KUSTO_AAD_AUTHORITY_ID('kustoAADAuthorityID') changed to KUSTO_AAD_AUTHORITY_ID('kustoAadAuthorityID')

v1.1.6

** New Feature **
Use hadoop configuration to save blob storage credentials

v1.1.5

Bug Fix
Special characters with value larger than 127 were failing in writing of json escaped fields

1.1.4

New Features
Device authentication made easier for python

v1.1.3

Breaking changes
Unsecured dependencies changed to good ones.

New Features
Added support for choosing AAD cloud for device authentication - using the environment variable : 'AadAuthorityUri' (already available for other authentication methods)

v1.1.2

Bugs Fix
Empty strings in structs were ingested wrongly - will now be ("key":"")

v1.1.1

Bugs fix:
'Distributed' mode will execute the kusto export command with tostring over timespan columns so that the schema matches the expected schema

v1.1.0

BREAKING CHANGES:
'Lean' and 'Scaled' mode are now called 'Single' and 'Distributed' respectively.
If the user does'nt specify storage parameters and a 'Distributed' read mode is chose- the storage for reading used will be provided by Kusto ingest service. The user can still provide those explicitly.

FEATURES:
New option - KUSTO_READ_MODE : User to override the connector heuristic to choose between 'Single' and 'Distributed' mode
Staging tables used for ingestion are now hidden