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 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!)