Releases: nats-io/nats-spark-connector
v1.2.4
The time stamp in the second column is now the time at which the adapter received the message from NATS rather than the time at which the message was recorded in the stream (as that time stamp is available in the JS Metadata for the message).
You can adjust the format of the time stamp through the "nats.datetime.format" configuration attribute.
You can now pass the name of your own class implementing the SSL context factory through the "nats.ssl.context.factory.class" configuration attribute.
v1.2.3
v1.2.2
Adds support for compressed payload to the source:
- The source configuration optional parameter "nats.storage.payload-compression" specifies the compression type to be used to decompress the payload of the message. Currently supported values are:
"zlib"
(plus"uncompressed"
and"none"
). If the payload of a particular message cannot be decompressed, it is then passed on as-is.
Improve handling of possible underlying connectivity issues.
Use fast binding when subscribing to the consumer to remove the requirement on the $JS API Stream info subject being exported when sourcing and using an existing durable consumer imported from another account.
v1.2.0 Use a single consumer with multiple subject filters
NOTE: Now requires NATS servers version 2.10 or above.
Balanced:
- Using the new multi-subject filters in consumers feature of NATS 2.10. Now only creates and uses a single consumer for all the subjects being listed in the config, rather than one consumer per subject.
Partitioned:
- no change (as it already assumes the streams/consumers are defined administratively)
v1.1.5 Config improvements: can control whether the balanced connector tries to define the stream/consumer (enabled by default, can be adjusted)
Balanced:
- Adds new "nats.js.define-consumer" config parameter (defaults to true) which means the connector will not try to create the stream consumer
- "nats.js.define-stream" config parameter now defaults to true
Partitioned:
- no change (as it already assumes the streams/consumers are defined administratively)
v1.1.4 Config improvements, doesn't try to define the stream to consume from (by default, can be adjusted)
1.1.4 TLS connection, stream creation is configurable and off by default
- Balanced doesn't try to create the stream unless the property
nats.js.define-stream
is set to"true"
- Update NATS Java library to 2.17.1-SNAPSHOT
- Uses the new functionality of the Java NATS library to construct the SSL context
- You can specify only the truststore and not the keystore if you don't want to do mTLS but still check the server's cert using the truststore
- You can specify the log4j properties file that is used when isLocal is set to true using the
LOG_PROP_PATH
environment variable. This means that the file which was previously hard-coded doesn't even need to exist for the connector to run whenisLocal
is false. - Assembly SBT plugin and task added if you want to create an uber-jar
v1.1.3 [ADDED] JS API prefix and user name/password config options.
[ADDED] JS API prefix and user name/password config options.
v1.1.2: 1.1.2 [IMPROVED] Defines the stream only if not already defined
Release v1.1.2
Balanced connector: only defines the stream if it is not already defined, adds the ability to specify the replica count.
Release v1.1.1
Can now use both NATS creds and TLS client certificates at the same time
Default stream storage type for balanced is now "file"
Release v1.1.0
Version 1.1 adds the ability to connect using SSL credentials.
Will connect and authenticate using SSL when the following environment variables are set:
NATS_TLS_KEY_STORE
NATS_TLS_KEY_STORE_PASSWORD
NATS_TLS_TRUST_STORE
NATS_TLS_TRUST_STORE_PASSWORD
Optionally NATS_TLS_ALGO
to override the default "SunX509"
and NATS_TLS_STORE_TYPE
to override the default store type "JKS"