sow_and_delta_subscribe
A sow_and_delta_subscribe
command is used to combine the functionality of commands sow
and a delta_subscribe
in a single command.
The sow_and_delta_subscribe
command is used: (a) to query the contents of a SOW topic (this is the sow
command); and (b) to place a subscription such that any messages matching the subscribed SOW topic and query filter will be published to the AMPS client (this is the delta_subscribe
command). As with the delta_subscribe
command, publish
messages representing updates to SOW records will contain only the information that has changed.
If a sow_and_delta_subscribe
is issued on a record that does not currently exist in the SOW topic, or if it is used on a topic that does not have a SOW-topic store defined, then a sow_and_delta_subscribe
will behave like a sow_and_subscribe
command.
Header Fields
The following table contains the header fields supported by a sow_and_delta_subscribe
command.
Field | Description |
| The command to be executed. Value: |
| The target SOW topic to query and subscribe to. |
| Acknowledgment type for the given command. Value is a comma separated string of one of more of the following: |
| Number of records to return in a single sow query results message. While the default value is 1, it is recommended to use a higher value, as even small increases can yield greater performance in query result delivery. |
| A bookmark specifying the historical state of the SOW to return results from. For SOW topics where historical query is enabled, AMPS returns the saved state of the SOW as of that bookmark. For SOW topics where historical query is not enabled, AMPS ignores this parameter. If the topic is enabled for historical query and AMPS has a transaction log that covers the topic, AMPS returns the saved state of the SOW as of that bookmark and starts a bookmark subscription at a point in the transaction log immediately after the point at which the SOW state was saved. In other words, if the granularity of the historical SOW preserves the state of the SOW at 11:30:10 AM and 11:30:50 AM, a request for a bookmark at 11:30:20 AM will provide the SOW state as of 11:30:10 AM, and begin the replay immediately after that SOW state. This ensures no messages are missed, but means that the subscription may begin before the bookmark. |
| If specified with an AMPS command requesting an acknowledgment message, all |
| If For example, this will remove the SOAP envelope in an XML message. |
| Content filter expression. |
| A comma separated list of flags available to the |
| Return the SOW results sorted by the specified fields. Fields are a comma-delimited list of AMPS identifiers, and may optionally include a sort specifier, |
| Identifier used to identify the client's SOW topic query. This identifier will be added to all messages that represent a response to the |
| If set to Default: |
| Messages that have fallen out of focus from the subscription are sent to the client. Default: |
| Option to instruct AMPS that the client would like to receive the |
| If |
| A comma-delimited list of For example, you might send a query with the SowKeys value |
| The subscription ID for this command. When provided with a new subscription, this is the identifier that AMPS will use for the subscription. When provided with the When provided with a For a new subscription, the AMPS clients will generate a subscription ID if one is not provided. |
| Return up to the number of messages specified from the SOW query. |
Options Field
The following table contains a list of the Options
available and their definitions when used in the AMPS sow_and_delta_subscribe
command.
Option | Description |
| This is the default |
| Specifies that the subscription should return bookmarks, if available, on each publish message. Bookmarks are only available if the topic that is subscribed to is recorded in the transaction log. Notice that this option does not set the starting point for a bookmark subscription: use the This option is not required to receive bookmarks for a bookmark subscription. Those subscriptions always include bookmarks on each publish message. |
| Specifies whether to conflate this subscription. The value provided can be a time interval, When present and set to a value other than none, enables conflation for the subscription. Can also be set to Recognizes the same time specifiers used in the AMPS configuration file (for example, Default: |
| When conflation is enabled, specifies the fields to use to determine message uniqueness. The format of this option is a comma-delimited list of XPath identifiers within brackets. For example, to conflate based on the value of the
Defaults to the SOW key fields for SOW topics. No default for non-SOW topics. This option is required for non-SOW topics. This option is not valid with the |
| For use with aggregated subscriptions. The format of this option is a comma-delimited list of XPath identifiers within brackets. For example, to aggregate entries based on their
This option must contain an entry for every field in the aggregated message. If there is no entry for a field in this option, that field will not appear in the aggregated message, even if the field is in the underlying message. When this option is provided, a This option cannot be used with a bookmark. |
| Tells AMPS to send messages to subscribing clients before they have been persisted to the transaction log. |
| Tells AMPS not to send empty publish messages to matching subscriptions. This can be useful for suppressing messages where no fields have changed. |
| Tells AMPS not to send the AMPS-generated |
| Specifies that the topic name should be a literal match, even if the topic name contains regular expression characters. |
| Send an When focus tracking is enabled, AMPS will also deliver the full message to a subscription when a previously out-of-focus message comes into focus. |
| For use with aggregated subscriptions. Specifies a comma-delimited set of fields to project, within brackets. Each entry has the format described in the AMPS User Guide. This option must contain an entry for every field in the aggregated message. If there is no entry for a field in this option, that field will not appear in the aggregated message, even if the field is in the underlying message. There is no default for this option. When this option is provided, a The maximum size of this option is 64KB. |
| Replace the subscription associated with |
| AMPS will provide at most This option is equivalent to providing a |
| AMPS will skip the specified number of records in the result set before returning results. This option is used with the |
| AMPS will send the SOW keys (that is, the data fields used to identify unique messages in the SOW) back with matching messages from the SOW. |
| Specifies the fields to include in messages provided on this subscription. The contents of this option are a comma-delimited list of inclusion specifiers. |
| AMPS will include a header with the time at which this instance of AMPS processed the incoming publish command for this message. |
Returns
A sow_and_delta_subscribe
command returns the following command types:
Command | Description |
| Indicates the beginning of results from a SOW query. |
| Indicates the end of results from a SOW query. |
| Indicates a record returned from a SOW query. |
| A new message or update published to AMPS. |
| Returned when the |
| Acknowledgements requested, as described in the following section. |
AMPS will send acknowledgment messages for the following AckType
fields: received
and processed
, along with a populated Status
header field describing the acknowledgment message.
If the sow_and_delta_subscribe
command is successful, AMPS will return a group_begin
message to notify the client that a group of messages is being returned as part of the sow
portion of the command. For more information about SOW topic query behavior, see the chapter on Querying the State of the World in the AMPS User Guide. The following table contains the AckType
messages which can be returned by a sow_and_delta_subscribe
.
Acknowledgment | Description |
| No This is the default behavior. |
| The |
| Not supported at this time. |
| AMPS has compiled the filter(s) for the |
| The |
| Returns an |
The stats
acknowledgment message includes three values in the header, the Matches
, TopicMatches
and the RecordsReturned
. These are defined below:
TopicMatches
The total number of records compared across all matching SOW topics.
Matches
The number of records returned that match the topic regular expression and the content filter. This value can be greater than RecordsReturned
in the case where the number of returned records is limited by TopN
.
RecordsReturned
The total number of records returned to the client, which can be limited by the TopN
header value.
Errors
Errors for a sow_and_delta_subscribe
query are either returned in the Status
field if an AckType
has been defined, or the errors may be inserted into the AMPS log.
Last updated