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
Created by Guest
Created on Sep 29, 2021

JSON and JSONB maximum size on NPS

Message systems like Kafka are often used as an enterprise nervous system for data. A datawarehouse like Netezza Performance Server needs to be able to consume this data for analysis and reporting. Most organizations prefer the loading of their data warehouse to happen in two stages: One that ingests data in a staging area or data lake and one that loads this further into facts and dimensions. The first requires a data store where data can be inserted in its raw format with little transformation. The latter loads this data and transforms it into an efficient but flexible structure that can be reported on. Recent versions of NPS introduced JSON and JSONB datatypes. These make it possible to use NPS as such data lake/staging/event store because messages from Kafka can be ingested at high insert rates with little transformation, preserving the structure of the original message, while making them queryable by NPS embedded indexes e.g. with a connector like this one Preliminary testing results show that projecting, filtering and aggregating JSONB columns with help of the json functions gave excellent performance and looks very promising. However the implementation of JSON on Netezza uses nvarchar behind the covers. This restricts data stored as this datatype to maximum 16000 character, 64 kilobytes in size. It is this size restriction that are a blocker for real life implementations where an NPS database is used as event store. Realistic events payloads quickly exceed this size. PostgreSql and Oracles equivalent implementation which use respective Text and BLOB do not impose this restriction. This enhancement request is about increasing the size limit of JSON and JSONB on NPS so that NPS with its excellent MPP performance can be used in event store patterns with realistically sized messages.
Needed By Yesterday (Let's go already!)