Stream create with owner fails, even though the owner is same as namespace owner

Description

Steps to reproduce:
1. Create a namespace, impersonating 'alice'
2. Create a stream in this namespace. It will be owned by 'alice', because the namespace is owned by 'alice'.
3. Attempt to create the stream again explicitly specifying 'alice'. It will fail due to the following check. It shouldn't fail though.

Release Notes

None

Activity

Show:
Andreas Neumann
February 23, 2017, 3:24 AM

First of all, the error message is not clear. It only states the new owner principal, but not the existing owner principal. If we add that to the message, then it becomes clear that this case should be valid. How about two apps using the same stream, owned by same principal? It should not matter whether that principal comes form the namespace or the app, right?

Nishith Nand
February 23, 2017, 3:41 AM

Should this extend to the instance too? If we have impersonation enabled but no namespace owner configured should it allow creating at cdap?

Rohit Sinha
February 23, 2017, 7:30 PM

Note to self: We need to do the same fix for dataset and apps.

Andreas Neumann
February 23, 2017, 8:23 PM

why not. The point is that it needs to be the same owner, regardless of how that owner was determined.

Rohit Sinha
February 23, 2017, 11:54 PM
Fixed

Assignee

Rohit Sinha

Reporter

Ali Anwar

Labels

None

Docs Impact

None

UX Impact

None

Components

Fix versions

Affects versions

Priority

Major
Configure