engine to start. GROUP Figure.3 GROUP Share Level An engine will be shared by all sessions created by all users belong to the same primary group name. The engine will be launched by the group name as the here the group name is kind of special user who is able to visit the compute resources/data of a team. It follows the Hadoop GroupsMapping to map user to a primary group. If the primary group is not found and TTL works similarly to USER share level. Tips for authorization in GROUP share level: The session user and the primary group name(as sparkUser/execute user) will be both accessible at engine-side

engine to start. GROUP Figure.3 GROUP Share Level An engine will be shared by all sessions created by all users belong to the same primary group name. The engine will be launched by the group name as the here the group name is kind of special user who is able to visit the compute resources/data of a team. It follows the Hadoop GroupsMapping to map user to a primary group. If the primary group is not found and TTL works similarly to USER share level. Tips for authorization in GROUP share level: The session user and the primary group name(as sparkUser/execute user) will be both accessible at engine-side

engine to start. GROUP Figure.3 GROUP Share Level An engine will be shared by all sessions created by all users belong to the same primary group name. The engine will be launched by the group name as the here the group name is kind of special user who is able to visit the compute resources/data of a team. It follows the Hadoop GroupsMapping to map user to a primary group. If the primary group is not found and TTL works similarly to USER share level. Tips for authorization in GROUP share level: The session user and the primary group name(as sparkUser/execute user) will be both accessible at engine-side

engine to start. GROUP Figure.3 GROUP Share Level An engine will be shared by all sessions created by all users belong to the same primary group name. The engine will be launched by the group name as the here the group name is kind of special user who is able to visit the compute resources/data of a team. It follows the Hadoop GroupsMapping to map user to a primary group. If the primary group is not found and TTL works similarly to USER share level. Tips for authorization in GROUP share level: The session user and the primary group name(as sparkUser/execute user) will be both accessible at engine-side

engine to start. GROUP Figure.3 GROUP Share Level An engine will be shared by all sessions created by all users belong to the same primary group name. The engine will be launched by the group name as the here the group name is kind of special user who is able to visit the compute resources/data of a team. It follows the Hadoop GroupsMapping to map user to a primary group. If the primary group is not found and TTL works similarly to USER share level. Tips for authorization in GROUP share level: The session user and the primary group name(as sparkUser/execute user) will be both accessible at engine-side

engine to start. GROUP Figure.3 GROUP Share Level An engine will be shared by all sessions created by all users belong to the same primary group name. The engine will be launched by the group name as the here the group name is kind of special user who is able to visit the compute resources/data of a team. It follows the Hadoop GroupsMapping to map user to a primary group. If the primary group is not found and TTL works similarly to USER share level. Tips for authorization in GROUP share level: The session user and the primary group name(as sparkUser/execute user) will be both accessible at engine-side

Release 1.7.0 GROUP Figure.3 GROUP Share Level An engine will be shared by all sessions created by all users belong to the same primary group name. The engine will be launched by the group name as the here the group name is kind of special user who is able to visit the compute resources/data of a team. It follows the Hadoop GroupsMapping to map user to a primary group. If the primary group is not found and TTL works similarly to USER share level. Tips for authorization in GROUP share level: The session user and the primary group name(as sparkUser/execute user) will be both accessible at engine-side

engine to start. GROUP Figure.3 GROUP Share Level An engine will be shared by all sessions created by all users belong to the same primary group name. The engine will be launched by the group name as the here the group name is kind of special user who is able to visit the compute resources/data of a team. It follows the Hadoop GroupsMapping to map user to a primary group. If the primary group is not found and TTL works similarly to USER share level. Tips for authorization in GROUP share level: The session user and the primary group name(as sparkUser/execute user) will be both accessible at engine-side

0-SNAPSHOT GROUP Figure.3 GROUP Share Level An engine will be shared by all sessions created by all users belong to the same primary group name. The engine will be launched by the group name as the here the group name is kind of special user who is able to visit the compute resources/data of a team. It follows the Hadoop GroupsMapping to map user to a primary group. If the primary group is not found and TTL works similarly to USER share level. Tips for authorization in GROUP share level: The session user and the primary group name(as sparkUser/execute user) will be both accessible at engine-side

Release 1.8.0 GROUP Figure.3 GROUP Share Level An engine will be shared by all sessions created by all users belong to the same primary group name. The engine will be launched by the group name as the here the group name is kind of special user who is able to visit the compute resources/data of a team. It follows the Hadoop GroupsMapping to map user to a primary group. If the primary group is not found and TTL works similarly to USER share level. Tips for authorization in GROUP share level: The session user and the primary group name(as sparkUser/execute user) will be both accessible at engine-side