From b4b995889f55d37857d02070f49161ad902457b4 Mon Sep 17 00:00:00 2001 From: snyk-bot Date: Tue, 26 Jul 2022 18:40:04 +0000 Subject: [PATCH 01/11] fix: upgrade com.datastax.oss:pulsar-jms from 2.4.1 to 2.4.2 Snyk has created this PR to upgrade com.datastax.oss:pulsar-jms from 2.4.1 to 2.4.2. See this package in Maven Repository: https://mvnrepository.com/artifact/com.datastax.oss/pulsar-jms/ See this project in Snyk: https://app.snyk.io/org/jshook/project/eb02b5e3-2668-4f0f-a63a-47871c96a9ff?utm_source=github&utm_medium=referral&page=upgrade-pr --- driver-jms/pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/driver-jms/pom.xml b/driver-jms/pom.xml index 6a46eb2be..f38fbeb7e 100644 --- a/driver-jms/pom.xml +++ b/driver-jms/pom.xml @@ -92,7 +92,7 @@ com.datastax.oss pulsar-jms - 2.4.1 + 2.4.2 From 9528ee003fd98ecdf02d72e5300c23544032e784 Mon Sep 17 00:00:00 2001 From: snyk-bot Date: Wed, 27 Jul 2022 05:07:33 +0000 Subject: [PATCH 02/11] fix: upgrade org.apache.logging.log4j:log4j-jcl from 2.17.2 to 2.18.0 Snyk has created this PR to upgrade org.apache.logging.log4j:log4j-jcl from 2.17.2 to 2.18.0. See this package in Maven Repository: https://mvnrepository.com/artifact/org.apache.logging.log4j/log4j-jcl/ See this project in Snyk: https://app.snyk.io/org/jshook/project/1830e4b8-f3ac-4d17-97f7-6ab4f6b54ef9?utm_source=github&utm_medium=referral&page=upgrade-pr --- mvn-defaults/pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mvn-defaults/pom.xml b/mvn-defaults/pom.xml index 775bc2848..4b98ad685 100644 --- a/mvn-defaults/pom.xml +++ b/mvn-defaults/pom.xml @@ -408,7 +408,7 @@ org.apache.logging.log4j log4j-jcl - 2.17.2 + 2.18.0 From 5dc479c97322cfcbf7703ff26ead816605a5e43f Mon Sep 17 00:00:00 2001 From: snyk-bot Date: Wed, 27 Jul 2022 23:35:58 +0000 Subject: [PATCH 03/11] fix: upgrade com.github.oshi:oshi-core-java11 from 6.1.6 to 6.2.1 Snyk has created this PR to upgrade com.github.oshi:oshi-core-java11 from 6.1.6 to 6.2.1. See this package in Maven Repository: https://mvnrepository.com/artifact/com.github.oshi/oshi-core-java11/ See this project in Snyk: https://app.snyk.io/org/jshook/project/fc9e1bd9-1d9a-474f-bde4-efb614c52ffe?utm_source=github&utm_medium=referral&page=upgrade-pr --- mvn-defaults/pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mvn-defaults/pom.xml b/mvn-defaults/pom.xml index 775bc2848..6cdc82007 100644 --- a/mvn-defaults/pom.xml +++ b/mvn-defaults/pom.xml @@ -260,7 +260,7 @@ com.github.oshi oshi-core-java11 - 6.1.6 + 6.2.1 From c08865d55ce6c5b2c51be1d642aee37c9991d6b5 Mon Sep 17 00:00:00 2001 From: snyk-bot Date: Wed, 27 Jul 2022 23:36:02 +0000 Subject: [PATCH 04/11] fix: upgrade net.java.dev.jna:jna from 5.11.0 to 5.12.1 Snyk has created this PR to upgrade net.java.dev.jna:jna from 5.11.0 to 5.12.1. See this package in Maven Repository: https://mvnrepository.com/artifact/net.java.dev.jna/jna/ See this project in Snyk: https://app.snyk.io/org/jshook/project/fc9e1bd9-1d9a-474f-bde4-efb614c52ffe?utm_source=github&utm_medium=referral&page=upgrade-pr --- mvn-defaults/pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mvn-defaults/pom.xml b/mvn-defaults/pom.xml index 775bc2848..db33063e8 100644 --- a/mvn-defaults/pom.xml +++ b/mvn-defaults/pom.xml @@ -100,7 +100,7 @@ net.java.dev.jna jna - 5.11.0 + 5.12.1 net.java.dev.jna From e1689098d7c5daf08dff9c92521e7978432600a0 Mon Sep 17 00:00:00 2001 From: snyk-bot Date: Wed, 27 Jul 2022 23:36:04 +0000 Subject: [PATCH 05/11] fix: upgrade net.java.dev.jna:jna-platform from 5.11.0 to 5.12.1 Snyk has created this PR to upgrade net.java.dev.jna:jna-platform from 5.11.0 to 5.12.1. See this package in Maven Repository: https://mvnrepository.com/artifact/net.java.dev.jna/jna-platform/ See this project in Snyk: https://app.snyk.io/org/jshook/project/fc9e1bd9-1d9a-474f-bde4-efb614c52ffe?utm_source=github&utm_medium=referral&page=upgrade-pr --- mvn-defaults/pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mvn-defaults/pom.xml b/mvn-defaults/pom.xml index 775bc2848..cbfb1aa3b 100644 --- a/mvn-defaults/pom.xml +++ b/mvn-defaults/pom.xml @@ -105,7 +105,7 @@ net.java.dev.jna jna-platform - 5.11.0 + 5.12.1 From caf10522270773081d2c7a4f6c62e643e90218e3 Mon Sep 17 00:00:00 2001 From: snyk-bot Date: Mon, 1 Aug 2022 08:30:46 +0000 Subject: [PATCH 06/11] fix: driver-pulsar/pom.xml to reduce vulnerabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-2326698 - https://snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-2421244 --- driver-pulsar/pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/driver-pulsar/pom.xml b/driver-pulsar/pom.xml index f4615339c..7c0b8e58f 100644 --- a/driver-pulsar/pom.xml +++ b/driver-pulsar/pom.xml @@ -77,7 +77,7 @@ org.apache.avro avro - 1.11.0 + 1.11.1 From 8de258a05d044532127c792b8ebb940ee0c99c21 Mon Sep 17 00:00:00 2001 From: snyk-bot Date: Mon, 1 Aug 2022 18:09:47 +0000 Subject: [PATCH 07/11] fix: driver-kafka/pom.xml to reduce vulnerabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-2326698 - https://snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-2421244 --- driver-kafka/pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/driver-kafka/pom.xml b/driver-kafka/pom.xml index c43f3c7b8..88f4ee778 100644 --- a/driver-kafka/pom.xml +++ b/driver-kafka/pom.xml @@ -47,7 +47,7 @@ org.apache.avro avro - 1.11.0 + 1.11.1 From 067e8694102ece2212f4e1b9e55658ed419781ed Mon Sep 17 00:00:00 2001 From: snyk-bot Date: Thu, 4 Aug 2022 18:21:28 +0000 Subject: [PATCH 08/11] fix: driver-cockroachdb/pom.xml to reduce vulnerabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JAVA-ORGPOSTGRESQL-2970521 --- driver-cockroachdb/pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/driver-cockroachdb/pom.xml b/driver-cockroachdb/pom.xml index 68ff9f1e8..d3b3b5387 100644 --- a/driver-cockroachdb/pom.xml +++ b/driver-cockroachdb/pom.xml @@ -42,7 +42,7 @@ org.postgresql postgresql - 42.4.0 + 42.4.1 From 8f1a29c31a34e825934505fad982cc0305814b29 Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Sat, 6 Aug 2022 06:08:47 +0000 Subject: [PATCH 09/11] build(deps): bump postgresql in /driver-cockroachdb Bumps [postgresql](https://github.com/pgjdbc/pgjdbc) from 42.4.0 to 42.4.1. - [Release notes](https://github.com/pgjdbc/pgjdbc/releases) - [Changelog](https://github.com/pgjdbc/pgjdbc/blob/master/CHANGELOG.md) - [Commits](https://github.com/pgjdbc/pgjdbc/compare/REL42.4.0...REL42.4.1) --- updated-dependencies: - dependency-name: org.postgresql:postgresql dependency-type: direct:production ... Signed-off-by: dependabot[bot] --- driver-cockroachdb/pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/driver-cockroachdb/pom.xml b/driver-cockroachdb/pom.xml index 68ff9f1e8..d3b3b5387 100644 --- a/driver-cockroachdb/pom.xml +++ b/driver-cockroachdb/pom.xml @@ -42,7 +42,7 @@ org.postgresql postgresql - 42.4.0 + 42.4.1 From 7b0c6d07e5525a76d3b662ee918e6bb2411d2bff Mon Sep 17 00:00:00 2001 From: yabinmeng Date: Sun, 7 Aug 2022 13:33:44 -0500 Subject: [PATCH 10/11] 1) Remove NB Pulsar batch processing. By default, Pulsar client API batches message sending with configurable parameters. Update README file accordingly. 2) Remove "driver-jms" module (which is practically useless). Starlight for JMS (S4J) driver that is currently available in "nb4-maintenance" branch will be used for JMS oriented testing against Apache Pulsar. --- .../driver/pulsar/ops/ReadyPulsarOp.java | 24 ++--- .../pulsar/util/PulsarActivityUtil.java | 10 +- driver-pulsar/src/main/resources/pulsar.md | 99 +++---------------- 3 files changed, 33 insertions(+), 100 deletions(-) diff --git a/driver-pulsar/src/main/java/io/nosqlbench/driver/pulsar/ops/ReadyPulsarOp.java b/driver-pulsar/src/main/java/io/nosqlbench/driver/pulsar/ops/ReadyPulsarOp.java index 9b25d479f..eefdd3f20 100644 --- a/driver-pulsar/src/main/java/io/nosqlbench/driver/pulsar/ops/ReadyPulsarOp.java +++ b/driver-pulsar/src/main/java/io/nosqlbench/driver/pulsar/ops/ReadyPulsarOp.java @@ -150,18 +150,18 @@ public class ReadyPulsarOp extends BaseOpDispenser { else if (StringUtils.equalsIgnoreCase(stmtOpType, PulsarActivityUtil.OP_TYPES.MSG_READ.label)) { return resolveMsgRead(clientSpace, topicUriFunc, asyncApiFunc); } - // Regular/non-admin operation: batch message processing - batch start - else if (StringUtils.equalsIgnoreCase(stmtOpType, PulsarActivityUtil.OP_TYPES.BATCH_MSG_SEND_START.label)) { - return resolveMsgBatchSendStart(clientSpace, topicUriFunc, asyncApiFunc); - } - // Regular/non-admin operation: batch message processing - message sending (producer) - else if (StringUtils.equalsIgnoreCase(stmtOpType, PulsarActivityUtil.OP_TYPES.BATCH_MSG_SEND.label)) { - return resolveMsgBatchSend(clientSpace, asyncApiFunc); - } - // Regular/non-admin operation: batch message processing - batch send - else if (StringUtils.equalsIgnoreCase(stmtOpType, PulsarActivityUtil.OP_TYPES.BATCH_MSG_SEND_END.label)) { - return resolveMsgBatchSendEnd(clientSpace, asyncApiFunc); - } +// // Regular/non-admin operation: batch message processing - batch start +// else if (StringUtils.equalsIgnoreCase(stmtOpType, PulsarActivityUtil.OP_TYPES.BATCH_MSG_SEND_START.label)) { +// return resolveMsgBatchSendStart(clientSpace, topicUriFunc, asyncApiFunc); +// } +// // Regular/non-admin operation: batch message processing - message sending (producer) +// else if (StringUtils.equalsIgnoreCase(stmtOpType, PulsarActivityUtil.OP_TYPES.BATCH_MSG_SEND.label)) { +// return resolveMsgBatchSend(clientSpace, asyncApiFunc); +// } +// // Regular/non-admin operation: batch message processing - batch send +// else if (StringUtils.equalsIgnoreCase(stmtOpType, PulsarActivityUtil.OP_TYPES.BATCH_MSG_SEND_END.label)) { +// return resolveMsgBatchSendEnd(clientSpace, asyncApiFunc); +// } // Regular/non-admin operation: end-to-end message processing - sending message else if (StringUtils.equalsIgnoreCase(stmtOpType, PulsarActivityUtil.OP_TYPES.E2E_MSG_PROC_SEND.label)) { return resolveMsgSend(clientSpace, topicUriFunc, asyncApiFunc, useTransactionFunc, seqTrackingFunc); diff --git a/driver-pulsar/src/main/java/io/nosqlbench/driver/pulsar/util/PulsarActivityUtil.java b/driver-pulsar/src/main/java/io/nosqlbench/driver/pulsar/util/PulsarActivityUtil.java index d6b27bd08..6adb24f40 100644 --- a/driver-pulsar/src/main/java/io/nosqlbench/driver/pulsar/util/PulsarActivityUtil.java +++ b/driver-pulsar/src/main/java/io/nosqlbench/driver/pulsar/util/PulsarActivityUtil.java @@ -42,11 +42,11 @@ public class PulsarActivityUtil { ADMIN_TENANT("admin-tenant"), ADMIN_NAMESPACE("admin-namespace"), ADMIN_TOPIC("admin-topic"), - E2E_MSG_PROC_SEND("ec2-msg-proc-send"), - E2E_MSG_PROC_CONSUME("ec2-msg-proc-consume"), - BATCH_MSG_SEND_START("batch-msg-send-start"), - BATCH_MSG_SEND("batch-msg-send"), - BATCH_MSG_SEND_END("batch-msg-send-end"), + E2E_MSG_PROC_SEND("e22-msg-proc-send"), + E2E_MSG_PROC_CONSUME("e22-msg-proc-consume"), +// BATCH_MSG_SEND_START("batch-msg-send-start"), +// BATCH_MSG_SEND("batch-msg-send"), +// BATCH_MSG_SEND_END("batch-msg-send-end"), MSG_SEND("msg-send"), MSG_CONSUME("msg-consume"), MSG_READ("msg-read"), diff --git a/driver-pulsar/src/main/resources/pulsar.md b/driver-pulsar/src/main/resources/pulsar.md index 23a037a37..f202c23d4 100644 --- a/driver-pulsar/src/main/resources/pulsar.md +++ b/driver-pulsar/src/main/resources/pulsar.md @@ -10,12 +10,11 @@ - [5.1. Pulsar Admin API Statement Block - Create/Delete Tenants](#51-pulsar-admin-api-statement-block---createdelete-tenants) - [5.2. Pulsar Admin API Command Block - Create/Delete Namespaces](#52-pulsar-admin-api-command-block---createdelete-namespaces) - [5.3. Pulsar Admin API Command Block - Create/Delete Topics, Partitioned or Not](#53-pulsar-admin-api-command-block---createdelete-topics-partitioned-or-not) - - [5.4. Batch Producer Command Block (Only Applicable with Pulsar Synchronous API)](#54-batch-producer-command-block-only-applicable-with-pulsar-synchronous-api) - - [5.5. Producer Statement Block](#55-producer-statement-block) - - [5.6. Consumer Statement Block](#56-consumer-statement-block) - - [5.7. Reader Statement Block](#57-reader-statement-block) - - [5.8. Multi-topic Consumer Statement Block](#58-multi-topic-consumer-statement-block) - - [5.9. End-to-end Message Latency Statement Block](#59-end-to-end-message-latency-statement-block) + - [5.4. Producer Statement Block](#54-producer-statement-block) + - [5.5. Consumer Statement Block](#55-consumer-statement-block) + - [5.6. Reader Statement Block](#56-reader-statement-block) + - [5.7. Multi-topic Consumer Statement Block](#57-multi-topic-consumer-statement-block) + - [5.8. End-to-end Message Latency Statement Block](#58-end-to-end-message-latency-statement-block) - [6. Generate Message Content](#6-generate-message-content) - [7. Message Schema Support](#7-message-schema-support) - [8. Measure End-to-end Message Processing Latency](#8-measure-end-to-end-message-processing-latency) @@ -53,7 +52,6 @@ At high level, Pulsar driver yaml file has the following structure: * (Pulsar Admin API) **create-tenant-block**: create/delete tenants * (Pulsar Admin API) **create-namespace-block**: create/delete namespaces * (Pulsar Admin API) **create-topic-block**: create/delete topics - * (Pulsar Client API) **batch-producer-block**: batch producer * (Pulsar Client API) **producer-block**: producer * (Pulsar Client API) **consumer-block**: consumer (single topic) * (Pulsar Client API) **reader-block**: reader @@ -140,9 +138,9 @@ Currently, the following configuration parameters are available at this level: * **admin_delop**: For Admin tasks, whether to execute delete operation instead of the default create operation. This can only be statically bound. * **seq_tracking**: Whether to do message sequence tracking. This is used for abnormal message processing error detection such as message loss, message duplication, or message out-of-order. This can only be statically bound. * **e2e_starting_time_source**: Starting timestamp for end-to-end operation. When specified, will update the `e2e_msg_latency` histogram with the calculated end-to-end latency. The latency is calculated by subtracting the starting time from the current time. The starting time is determined from a configured starting time source. The unit of the starting time is milliseconds since epoch. The possible values for `e2e_starting_time_source`: - * `message_publish_time` - uses the message publishing timestamp as the starting time - * `message_event_time` - uses the message event timestamp as the starting time - * `message_property_e2e_starting_time` - uses a message property `e2e_starting_time` as the starting time. + * `message_publish_time` - uses the message publishing timestamp as the starting time + * `message_event_time` - uses the message event timestamp as the starting time + * `message_property_e2e_starting_time` - uses a message property `e2e_starting_time` as the starting time. ## 3.3. Statement Level Parameters @@ -266,66 +264,7 @@ In this statement block, there is only one statement (s1): **NOTE**: The topic name is bound by the document level parameter "topic_uri". -## 5.4. Batch Producer Command Block (Only Applicable with Pulsar Synchronous API) - -**NOTE**: This statement block is only applicable when Pulsar Synchronous API is used as defined by the document level setting ***async_api***. -``` -params: - async_api: "false" -``` - -Batch producer statement block is used to send(produce) a batch of messages all at once to the Pulsar cluster. It has a typical format as below: - -```yaml - - name: batch-producer-block - tags: - phase: batch-producer - statements: - - name: s1 - optype: batch-msg-send-start - # For batch producer, "producer_name" should be associated with batch start - # batch_producer_name: {batch_producer_name} - ratio: 1 - - name: s2 - optype: batch-msg-send - msg_key: "{mykey}" - msg_property: | - { - "prop1": "{myprop1}", - "prop2": "{myprop2}" - } - msg_value: | - { - "SensorID": "{sensor_id}", - "SensorType": "Temperature", - "ReadingTime": "{reading_time}", - "ReadingValue": {reading_value} - } - ratio: 100 - - name: s3 - optype: batch-msg-send-end - ratio: 1 -``` - -This statement block has three statements (s1, s2, and s3) with the following ratios: 1, , 1. - -* Statement **s1** is used to mark the start of a message batch - * (Mandatory) **optype (batch-msg-send-start)** is the statement identifier for this statement - * (Optional) **batch_producer_name**, when provided, specifies the Pulsar producer name that is associated with the batch production of the messages. - * (Optional) **ratio**, when provided, MUST be 1. If not provided, it is default to 1. -* Statement **s2** is the core statement that generates each message that needs to be put in a batch. - * (Mandatory) **optype (batch-msg-send)** is the statement identifier for this statement - * (Optional) **msg_key**, when provided, specifies the key of the generated message - * (Optional) **msg_property**, when provided, specifies the properties of the generated message. It must be a JSON string that contains a series of key-value pairs. - * (Mandatory) **msg_payload** specifies the payload of the generated message - * (Optional) **ratio**, when provided, specifies the batch size (how many messages to be put in one batch). If not provided, it is default to 1. -* Statement **s3** is used to mark the end of a batch - * (Mandatory) **optype (batch-msg-send-end)** is the statement identifier for this statement - * (Optional) **ratio**, when provided, MUST be 1. If not provided, it is default to 1. - -**NOTE**: the topic that the producer needs to publish messages to is specified by the document level parameter ***topic_uri***. - -## 5.5. Producer Statement Block +## 5.4. Producer Statement Block This is the regular Pulsar producer statement block that produces one Pulsar message per NB execution cycle. A typical format of this statement block is as below: @@ -363,7 +302,7 @@ This statement block only has one statement (s1): **NOTE**: the topic that the producer needs to publish messages to is specified by the document level parameter ***topic_uri***. -## 5.6. Consumer Statement Block +## 5.5. Consumer Statement Block This is the regular Pulsar consumer statement block that consumes one message per NB execution cycle. A typical format of this statement block is as below: @@ -389,7 +328,7 @@ This statement block only has one statement (s1): **NOTE**: the topic that the consumer receives messages from is specified by the document level parameter ***topic_uri***. -## 5.7. Reader Statement Block +## 5.6. Reader Statement Block This is the regular Pulsar reader statement block that reads one message per NB cycle execution. It has a typical format as below: @@ -416,7 +355,7 @@ This statement block only has one statement (s1): **NOTE**: the topic that the reader needs to read messages from is specified by the document level parameter ***topic_uri***. -## 5.8. Multi-topic Consumer Statement Block +## 5.7. Multi-topic Consumer Statement Block This is the Pulsar consumer statement block that consumes messages from multiple Pulsar topics per NB execution. It has a typical format as below: @@ -449,7 +388,7 @@ This statement block only has one statement (s1): **NOTE 2**: when both **topic_names** and **topics_pattern** are provided, **topic_names** takes precedence over **topics_pattern**. -## 5.9. End-to-end Message Latency Statement Block +## 5.8. End-to-end Message Latency Statement Block End-to-end message latency statement block is used to simplify the task of measuring the end-to-end message processing (from being published to being consumed)latency. It has a typical format as below: @@ -585,7 +524,6 @@ At the moment, the following Pulsar driver specific** NB activity parameters are Some other common NB activity parameters are listed as below. Please refer to NB documentation for more information. * driver=pulsar -* seq=concat (needed for **batch** producer) * tags=phase: * threads= * cycles= @@ -599,20 +537,15 @@ Some other common NB activity parameters are listed as below. Please refer to NB run driver=pulsar tags=phase:producer threads=100 cycles=100K web_url=http://localhost:8080 service_url=pulsar://localhost:6650 config=/config.properties yaml=/pulsar.yaml ``` -2. Run Pulsar producer batch API to produce 1M messages with 2 NB threads. - **NOTE**: *seq=* must have **concat** value in order to make the batch API working properly! -```bash - run driver=pulsar seq=concat tags=phase:batch-producer threads=2 cycles=1M web_url=http://localhost:8080 service_url=pulsar://localhost:6650 config=/config.properties yaml=/pulsar.yaml --report-csv-to -``` - -3. Run Pulsar consumer API to consume (and acknowledge) 100 messages using +2. Run Pulsar consumer API to consume (and acknowledge) 100 messages using one single NB thread. ```bash run driver=pulsar tags=phase:consumer cycles=100 web_url=http://localhost:8080 service_url=pulsar://localhost:6650 config=/config.properties yaml=/pulsar.yaml ``` # 12. Appendix A. Template Global Setting File (config.properties) -```properties + +``` schema.type = schema.definition = From 0d85dc02b4e8755ad17d902b46288ac60938f941 Mon Sep 17 00:00:00 2001 From: yabinmeng Date: Sun, 7 Aug 2022 13:33:54 -0500 Subject: [PATCH 11/11] 1) Remove NB Pulsar batch processing. By default, Pulsar client API batches message sending with configurable parameters. Update README file accordingly. 2) Remove "driver-jms" module (which is practically useless). Starlight for JMS (S4J) driver that is currently available in "nb4-maintenance" branch will be used for JMS oriented testing against Apache Pulsar. --- nb/pom.xml | 6 ------ pom.xml | 1 - 2 files changed, 7 deletions(-) diff --git a/nb/pom.xml b/nb/pom.xml index 4c65e5865..39a1245ec 100644 --- a/nb/pom.xml +++ b/nb/pom.xml @@ -114,12 +114,6 @@ 4.17.20-SNAPSHOT - - io.nosqlbench - driver-jms - 4.17.20-SNAPSHOT - - diff --git a/pom.xml b/pom.xml index 69a32d5a1..072b04cc2 100644 --- a/pom.xml +++ b/pom.xml @@ -92,7 +92,6 @@ driver-jdbc driver-cockroachdb driver-pulsar - driver-jms