Skip to Main Content
IBM Data and AI Ideas Portal for Customers

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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 (

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

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

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at

Status Future consideration
Workspace Db2
Components NoSQL
Created by Guest
Created on Mar 6, 2023

make FS/Db2 generate some good remote execution plans against big Mongo collections

Problem statement/pain points - refer to what elaborated in TS012101437 for details

*for multi-way joins (>2), FS/Db2 currently always generate bad remote SQL execution plans involving full scan of some large collections w/ no filters pushed down as expected or w/ right JOIN method and sequence as expected to avoid full scan


Current workarounds

*use Db2 optimizer guidelines to update the FS/Db2 bad remote execution plans into some functioning versions containing right join method, join order, join predicate, and access paths consistent w/ data statistics in the backend Mongo collections


Proposed solutions

*extend Db2/FS cost-based-optimizer(CBO) into handling Mongo collections to avoid generating always wrong remote execution plans for multi-way joins (>2) by enabling automatic collections of data statistics essential to improve chances of making Mongo based queries not stuck all the time



*currently, Db2/FS Mongo wrapper simply cannot generate any good remote execution plan in handling multi-way joins (>2) involving big Mongo collections - the always wrong remote execution plans FS/Db2 generates makes it impossible to count on Db2/FS in handling real Mongo data usage scenarios correctly - by enabling automatic collections of data statistics available in Mongo data store, it will allow Db2/FS cost-based-optimizer(CBO) to improve chances of generating good remote execution plans

Needed By Yesterday (Let's go already!)