Skip to Main Content
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 Under review
Workspace DataStage
Created by Guest
Created on Jun 14, 2022

File Connector - Definition for Internal table Location

We need the table location to be optional when we define it as an internal table. When the location is not user-defined, the Datastage must define the create table command, but it does not need to define the location.

This is important because the hive has a controlled area in HDFS to store the internal hive table data.

For security reasons this area cannot be used by external users. This area should only be used by Hive.

In this way, we remove the risk of deleting data that should not be deleted because of incorrect location definitions:

An example:

create internal table IF NOT EXISTS databasename.tablename (dm_timestamp column, int id) row format delimited fields terminated by '\t' location '/user/hive/warehouse/databasename.db'.

When we run a drop table databasename.tablename the databasename.db will be dropped. In this situation, we lost all data from database "databasename"

Needed By Yesterday (Let's go already!)
  • Guest
    Jul 12, 2022

    Customer mentioned:

    We still think it's important for the parameter to be optional in the case of non-EXTERNAL tables because we would like to continue to use the IBM product

    for the creation of the tables and not just add another process to this just because of one parameter.

    Note that even for the hadoop cluster provider, this location parameter is already optional for non-EXTERNAL tables. What would already suit us would be datastage keep being compatible, making this location parameter as in Cloudera, that is, optional and not mandatory.