Log4j 2.17.1

Upgrades to Bullet Core 1.5.2 and Bullet DSL 1.2.2

Upgrades to using Log4j 2.17.1

Bullet Core 1.5.1 and DSL 1.2.1, removes unnecessary SerDe call for PubSubMessages

This release updates to Bullet Core 1.5.1 and Bullet DSL 1.2.1.

It also fixes a potential bug where the SerDe was called to deserialize a PubSubMessage unnecessarily in the QueryBolt

Nested Lateral View Explode and subqueries with Bullet Core 1.5.0

This release updates to Bullet Core 1.5.0 and Bullet DSL 1.2.0.

Core 1.4.4 and DSL 1.1.8

This release updates to using Bullet Core 1.4.4 and Bullet DSL 1.1.8

Core 1.4.2 and DSL 1.1.7

This release updates to using Bullet Core 1.4.2 and Bullet DSL 1.1.7

This release also changes what is emitted between the Query Spout and the Filter/Join Bolts upon receiving a query. Instead of emitting a (id, queryBytes, metadata), a (id, PubSubMessage) is emitted instead. Bullet Storm now respects the PubSubMessageSerDe settings released in Bullet Core 1.4.0.

Core 1.3.1 and DSL 1.1.6

This release updates to using Bullet Core 1.3.1 and Bullet DSL 1.1.6

First release using Screwdriver

No new changes

First release on Maven Central - Bintray EOL

Core 1.2.2. No new changes

Bullet Core 1.2.1

Updates Bullet Core to 1.2.1 and (all dependencies that use core to the the latest versions that use 1.2.1)

Spout Connector and Bullet DSL 1.1.1

This release adds a Spout Connector that lets you plug in a IRichSpout as a BulletConnector. It can also behave as a Spout or as a BulletConnector. This exists so that existing spouts can be used in the DSLSpout while still leveraging the BulletDeserializer and BulletRecordConverter aspects of the DSL. The ICredentialsListener is also implemented so credentials sent to the DSL Spout through Storm can be passed into the spout being wrapped.

Take a look at the documentation for more details.

To use the SpoutConnector, simply pass in your subclass of it as the bullet.dsl.connector.class.name and configure DSL as before. You have two additional settings:

1. bullet.topology.dsl.spout.connector.as.spout.enable to use your connector as the spout in the DSLSpout (so credentials, open, activate, deactivate etc are called at the proper spout lifecycle moments)
2. bullet.topology.dsl.spout.connector.class.name to pass in the name of the spout to wrap in the SpoutConnector. If you use this and do not override the SpoutConnector#getSpout, your wrapped spout here must have a constructor that takes in a BulletConfig. If not, you can simply override the SpoutConnector#getSpout to instantiate your spout in some other way.

This release also uses Bullet DSL 1.1.1