Skip to content

Update Messaging docs #3625

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
alainjobart merged 1 commit into from
Feb 3, 2018
Merged

Update Messaging docs #3625

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 12 additions & 6 deletions doc/Messaging.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -142,7 +142,7 @@ A received (or processed) message can be acknowledged using the `MessageAck`
API call. This call accepts the following parameters:

* `Name`: Name of the message table.
* `Keyspace`: Keypsace where the message table is present. This field can be
* `Keyspace`: Keyspace where the message table is present. This field can be
empty if the table name is unique across all keyspaces.
* `Ids`: The list of ids that need to be acked.

Expand Down Expand Up @@ -184,18 +184,24 @@ message and the back-off is less aggressive.

You can also view messages using regular `select` queries.

## Known limitations
## Undocumented features

The message feature is currently in alpha, and can be improved. Here is the
list of possible limitations/improvements:
These are features that were previously known limitations, but have since been supported
and are awaiting further documentation.

* Flexible columns: Allow any number of application defined columns to be in
the message table.
* No ACL check for receivers: To be added.
* Proactive scheduling: Upcoming messages can be proactively scheduled for
timely delivery instead of waiting for the next polling cycle.
* Monitoring support: To be added.
* Dropped tables: The message engine does not currently detect dropped tables.

## Known limitations

The message feature is currently in alpha, and can be improved. Here is the
list of possible limitations/improvements:

* Proactive scheduling: Upcoming messages can be proactively scheduled for
timely delivery instead of waiting for the next polling cycle.
* Changed properties: Although the engine detects new message tables, it does
not refresh properties of an existing table.
* A `SELECT` style syntax for subscribing to messages.
Expand Down