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,
Post an idea
Upvote ideas that matter most to you
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.
Redshift connector slow in IIS DataStage for Insert/Update
We have a use case in which we need to process records from IIS DataStage into an aws Redshift instance. When using the stage as currently implemented, we're seeing a throughput that averages 2-6 records a second which is far below the acceptable range when considering load sizes in the range of hundred of thousands. Additionally depending on your configuration, the connection to Redshift will eventually timeout after several hours. Currently the stage implements inserts and updates using a JDBC insert which is not a best practice according to aws documentation. Instead the stage should be using the Redshift COPY command to bulk load the finished data set which is far faster than inserts.
Do not place IBM confidential, company confidential, or personal information into any field.