BigData / Apache StreamPark Interview questions
How does the Team concept enable multi-tenancy in StreamPark?
StreamPark's Team is the boundary that lets one shared installation serve multiple departments without them stepping on each other.
Each team functions like an isolated workspace: applications, projects, and (in features like Yarn Queue Management) resource scoping all attach to a specific team. A USER account has no visibility into a team until an ADMIN binds them to it, and once bound, the console only shows that team's data when it's selected. Switching teams from the top-right selector swaps the entire working context.
This gives StreamPark logical multi-tenancy on shared infrastructure — one console, one database, one set of running processes — without needing separate StreamPark installs per department, while still keeping each department's jobs and configuration invisible to the others by default.
More Related questions...
