IBM Data and AI Ideas Portal for Customers

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:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Future consideration
Created by Guest
Created on Mar 10, 2020

Creating Expansions while operation in progress returns 500 instead of 409

Follow up from #1474 which was closed without a resolution.

Currently, if the user initiates a request to POST /v1/environments/${environment_id}/collections/${collection_id}/expansions while a process (such as a snapshot, etc) is running on their collection, they receive a 500 Internal Server Error.

This can be reproduced by creating an expansion list, and then updating it in rapid succession. The creation request will most likely succeed, while the following update request fails with the 500 error.

In the issue that I linked above, @eoehlsch noted that there isn't much that can be done from the service perspective to prevent this issue.

After further discussion with @mkistler @asantiago and @jsstylos , while we may not be able to prevent this issue from happening, we can return a more appropriate 409 Conflict status code.

Description of the 409 status code

The request could not be completed due to a conflict with the current state of the target resource. This code is used in situations where the user might be able to resolve the conflict and resubmit the request.

Returning this status code can better inform the user that their previous action may be the cause of the resource they are attempting being in use.

Ideal solution
  • The POST /v1/environments/${environment_id}/collections/${collection_id}/expansions would return a 409 status code if the resource was in use due to a previous operation

  • We would provide a GET request to get the status of the expansion list (similar to what is provided for stopwords and tokenization dictionaries) so that the user has the ability to poll for a ready status of their resource after a CRUD operation