Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Submitted
Categories Global Mailbox
Created by Guest
Created on Oct 22, 2024

Utility to keep Cassandra tables in sync

There are times when Cassandra nodes may get out of sync and some of the nodes may deem it appropriate to bring back records that should no longer belong in the tables.


For example: mailbox.messages, mailbox.messages_by_name and mailbox.messages_by_id - these tables should all have the same information in slightly different forms, but what we have discovered is that it is possible for mailbox.messages and mailbox.messages_by_name to have duplicate records, even though mailbox.messages_by_id would have only one version of that same record.

This situation causes deleted files to be "resurrected" and downloaded again by the end users.


There needs to be a utility that will analyze Cassandra tables and take an action (or at the very least provide an alert) whenever this type of situation occurs. Especially, since in the Cassandra NoSQL world, it's virtually impossible to query for this type of information.

What is your industry? Healthcare
How will this idea be used?

This utility will be similar to the Sterling B2B "dataSweeper" or the Sterling FileGateway "sfgdbcheck" and will keep Cassandra tables in check before the table discrepancies cause business impact.