You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pubsubplus-connector-spark_3.x/src/docs/asciidoc/User-Guide.adoc
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,6 +85,10 @@ If rotating access token is present in file accessible by connector use below op
85
85
86
86
NOTE: When access token is read from file, it may lose some of it's expiry time by the time it is accessed by connector. It is recommended to have minimal time difference between writing to file and access by the connector so that a valid new token is updated in solace session before expiry of old token.
87
87
88
+
=== Message Replay
89
+
90
+
Solace Spark Connector can replay messages using Solace Replay Log. Connector can replay all messages or after specific replication group message id or after specific timestamp. Please refer to https://docs.solace.com/Features/Replay/Msg-Replay-Concepts-Config.htm[Message Replay Configuration] to enable replay log in Solace PubSub+ broker.
91
+
88
92
=== Solace Spark Streaming Schema Structure
89
93
90
94
Solace Spark Connector transforms the incoming message to Spark row with below schema definition.
Copy file name to clipboardExpand all lines: pubsubplus-connector-spark_3.x/src/docs/sections/general/configuration/spark-config.adoc
+27-7Lines changed: 27 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@
55
55
| int
56
56
| 0 - 60000
57
57
| 3000
58
-
| How much time in (MS) to wait between each attempt to connect or reconnect to a host. If a connect or reconnect attempt to host is not successful, the API waits for the amount of time set for reconnectRetryWaitInMillis, and then makes another connect or reconnect attempt.
58
+
| How much time in (MS) to wait between each attempt to connect or reconnect to a host. If connect or reconnect attempt to host is not successful, the API waits for the amount of time set for reconnectRetryWaitInMillis, and then makes another connect or reconnect attempt.
| Set the replay strategy if messages need to be replayed from broker to connector. For more information refer to https://docs.solace.com/Features/Replay/Msg-Replay-Concepts-Config.htm#Types[SolaceReplayConfiguration]
162
+
163
+
| replayStrategyReplicationGroupMessageId
164
+
| string
165
+
| valid-replication-group-message-id
166
+
| empty
167
+
| Set the property if replay strategy is REPLICATION-GROUP-MESSAGE-ID. Message playback is started after this replication group message id.
168
+
169
+
| replayStrategyStartTime
170
+
| string
171
+
| datetime string<yyyy-MM-dd'T'HH:mm:ss>
172
+
| empty
173
+
| Set the property if replay strategy is TIMEBASED. Any messages in the replay log equal to, or newer than, the specified date and time that match the endpoint’s subscriptions are replayed to the connector. The date can't be earlier than the date the replay log was created, otherwise replay will fail.
174
+
175
+
| replayStrategyTimeZone
176
+
| string
177
+
| valid timezone
178
+
| UTC
179
+
| Set the property if replay strategy is TIMEBASED.
180
+
157
181
| ackLastProcessedMessages
158
182
| boolean
159
183
| true or false
160
184
| false
161
-
| Set this value to true if connector needs to identify and acknowledge processed messages in last run during restarts. The connector purely depends on checkpoint generated during Spark commit. We recommended enabling this configuration only when your downstream system has processed data in previous run.
185
+
a| Set this value to true if connector needs to identify and acknowledge processed messages in last run during restarts. The connector purely depends on checkpoint generated during Spark commit. We recommended enabling this configuration only when your downstream system has processed data in previous run.
162
186
163
-
| skipDuplicates
164
-
| boolean
165
-
| true or false
166
-
| false
167
-
| Set this value to true if connector needs check for duplicates before adding to Spark row. This scenario occurs when a task is running late and new task is started. The new task may have duplicate message as messages from earlier are not acknowledged by the time it is start.
187
+
NOTE: This property will be void if replay strategy is enabled.
Copy file name to clipboardExpand all lines: pubsubplus-connector-spark_3.x/src/main/java/com/solacecoe/connectors/spark/streaming/SolaceMicroBatch.java
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -40,9 +40,9 @@ public class SolaceMicroBatch implements MicroBatchStream, SupportsAdmissionCont
Copy file name to clipboardExpand all lines: pubsubplus-connector-spark_3.x/src/main/java/com/solacecoe/connectors/spark/streaming/properties/SolaceSparkStreamingProperties.java
+4Lines changed: 4 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,10 @@ public class SolaceSparkStreamingProperties {
0 commit comments