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 Not under consideration
Workspace Db2 Big SQL
Created by Guest
Created on May 24, 2017

BI 4.2 - Big SQL cannot create external hadoop table with Ranger policies

External Hadoop Tables + RWX permissions (in Ranger) + No DATAACCESS Privilege = Cannot create external tables

It just works if you either provide DATAACCESS to a specific user or set HDFS ACLs to RWX.

For example, assume that user USERX is granted READ, WRITE, and EXECUTE privileges through a Ranger policy on a given location, and USERX tries to create an external table on that location. USERX will get the SQL0551N error message
SQL0551N "" does not have the privilege to perform operation
"" on object "".
SQLSTATE=42501 "" does not have the privilege to perform operation
"" on object "", SQLCODE=-551, SQLSTATE=42501

Possible workarounds:

1. Provide *DATAACCESS* privilege to user - however, got access to everything
* DATAACCESS is the authority that allows access to data within a specific database.
* For all tables, views, materialized query tables, and nicknames it gives these authorities and privileges:
* LOAD authority on the database
* SELECT privilege (including system catalog tables and views)
* INSERT privilege
* UPDATE privilege
* DELETE privilege
2. Grant RWX privilege on the location and its contents in HDFS


the customer expects that it is working with Apache Ranger - it works for Hadoop Tables (no external), so they expect the same behaviour for External Hadoop Tables too.
  • Guest
    Jul 19, 2019

    There's some confusion on using Ranger capabilities with Hadoop ACLs. Please try the latest version and reach out to us if you still have trouble with Ranger.. many Ranger capabilities were introduced in recent releases. Thanks!