Log4j provided and only Slf4j

Upgrades to Bullet Core 1.5.2

We now only have a compile time dependency on slf4j-api. The binding to log4j is marked as provided so dependent projects can use whatever logging implementation they want. If log4j is desired, then those projects can depend on the binding and mark it as as scope compile. Note this is true even in the fat jar.

Bullet Core 1.5.1

Updates to Bullet Core 1.5.1

Bullet Core 1.5.0

This release updates to Bullet Core 1.5.0

Bullet Core 1.4.4

Updates to Bullet Core 1.4.4

Bullet Core 1.4.2

Updates to Bullet Core 1.4.2

Bullet Core 1.3.1

Bullet Core 1.3.1

[BUGFIX] Fixes response partitions not being used if partition routing is disabled

This fixes a bug with KafkaResponsePublisher when bullet.pubsub.kafka.partition.routing.enable was set to false and bullet.pubsub.kafka.response.partitions was configured with a subset of the partitions of the topic. The latter was not honored and the KafkaResponsePublisher would send a PubSubMessage to any of the partitions of the topic. This release fixes that issue and honors the partitions configured and sends to any of those partitions instead.

KafkaSubscriber now supports rate limiting, optional disabling of partition routing

This release uses bullet-core-1.3.0 and adds rate limiting capabilities to the KafkaSubcriber. This can be enabled and configured using the following settings:

bullet.pubsub.kafka.subscriber.rate.limit.enable: To enable or disable rate limting. By default, disabled.
bullet.pubsub.kafka.subscriber.rate.limit.max.messages: The maximum messages that will be read in a rate limit interval. Defaults to 50
bullet.pubsub.kafka.subscriber.rate.limit.interval.ms: The duration of a rate limit interval in milliseconds. Defaults to 10.

This release also makes using the partitions of a Kafka topic optional. Previously, the KafkaQueryPublisher used to pick one of the partitions assigned to the topic (or configured) and place it into the Metadata of the PubSubMessage. This partition would then be used to send the message to that partition by the KafkaResponsePublisher. You can choose to disable this mechanism by setting
bullet.pubsub.kafka.partition.routing.enable to false (defaults to true). This is particularly relevant if a Storage is being used in the WebService to store queries and later being read for replay since the partition information could be stale/useless.

See the configuration for more details.

First release using Screwdriver

No new changes

First release on Maven Central - Bintray EOL

Core 1.2.2 and no other changes