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.
merge node: join small local dataset to large remote dataset by sending the local data literally in the sql query
In a merge node, when joining a small local dataset to a large remote database table, Modeler downloads the entire contents of the large table in order to perform the join. This is often prohibitive. Instead, if the local dataset is small enough (thousands), send all the items from the local dataset as literals in the query to the remote database. E.g. SELECT * FROM BIGTABLE WHERE KEY IN (123, 4365, 4545, ......... , 45434) where the listed keys are those from the local dataset. As a current workaround, many of us copy and paste the local keys into a SELECT node to get only the needed rows and *then* join it with the local dataset.
Do not place IBM confidential, company confidential, or personal information into any field.