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 Not under consideration
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.