Bullet Core 1.5.2 and BQL 1.3.2

Upgrades to Bullet Core 1.5.2 and Bullet BQL 1.3.2

Bullet Core 1.5.1 and BQL 1.3.1

Updates to Bullet Record 1.5.1 and Bullet BQL 1.3.1

[BUGFIX] Fixes Commons Lang3 transitive dependency being masked

Since bullet-service uses Commons Lang 3 as a test dependency, it masked the same transitive dependency of bullet-core and prevented bullet-service from having Commons Lang3 in its embedded jar. This fixes that.

Nested Lateral View Explode and subqueries with Bullet Core 1.5.0

This release updates to Bullet Core 1.5.0 and Bullet BQL 1.3.0.

Core 1.4.4 and BQL 1.2.5

Updates to Core 1.4.4 and BQL 1.2.5

QueryService removal, retrieval and cleanup metrics only increment actual messages

The metrics released in the previous version incremented the query.storage.retrieve.success, query.storage.cleanup.success and query.storage.remove.success metrics even when there was no storage actually being used. This release no longer does that. If the message from the storage is null, then these metrics are not incremented.

Conversely, the query.storage.add.success is still incremented if an actual storage is not used.

Query Metrics

Adds the following metrics to the QueryService that hooks into a configured MetricPublisher if used:

QueryService#submitQuery(String, Query,String):
query.pubsub.submit.success
query.pubsub.submit.fail
query.storage.add.success
query.storage.add.fail

QueryService#kill(String)
query.storage.remove.success
query.storage.remove.fail
query.pubsub.kill.success
query.pubsub.kill.fail

QueryService#get(String)
query.storage.retrieve.success
query.storage.retrieve.fail

QueryService#respond
query.storage.cleanup.success
query.storage.cleanup.fail
(For each configured PubSubResponder):
query.pubsub.response.success
query.pubsub.response.fail

These metrics are incremented for the methods listed above.

Core 1.4.2 and BQL 1.2.4

Uses Bullet Core 1.4.2 and Bullet BQL 1.2.4

[BUGFIX] Fixes QueryService#get not using the PubSubSerDe

This release fixes the issue with the get in QueryService not sending the read PubSubMessage through any configured PubSubMessageSerDe

Uses ByteArrayPubSubMessageSerDe by default

Updates to Bullet Core 1.4.1 and uses the ByteArrayPubSubMessageSerDe by default instead of the base IdentityPubSubMessageSerDe. This makes (if the backend uses the same SerDe) Bullet work like it used to before SerDes by storing Query as byte[] in the PubSubMessageSerDe till Query#getContentAsQuery is called, preventing needless reification.