[
https://issues.apache.org/jira/browse/ATLAS-4306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Mestry updated ATLAS-4306:
-----------------------------------
Description:
*Background*
Spooling for messages is enabled for hooks that publish messages to Atlas. This
is available for hooks that choose to add the following properties:
{code:java}
atlas.hook.spool.enabled=true
atlas.hook.spool.dir=/spool-dir{code}
Once the hook is initialized, the directory is created. The user who creates
the directory will have read-write permissions to the spool directly.
There are cases where the hook gets initialized with different users. When that
happen, the directory is accessible to the other user. This causes
initialization failure and the spooling functionality not to be available to
the other user.
*Solution(s)*
This problem can be circumvented by making the 2 users be part of the same
group that will allow for same directory to be present for multiple users.
Multi-user access is currently supported.
For the scenario, where multiple users are not part of the same group, the
situation described above will come into play.
_Approach Used_
**No directory exists, _User1_ first creates the directory specified in the
configuration.
Directory exists, _User1_ has access to the directory and spooling is enabled.
Directory exists, _User2_ does not have access to the directory. New directory
with username suffixed to the existing directory name is created. The directory
created for the user will be
{code:java}
/spool-dir-User1
{code}
was:
*Background*
Spooling for messages is enabled for hooks that publish messages to Atlas. This
is available for hooks that choose to add the following properties:
_atlas.hook.spool.enabled=true_
_atlas.hook.spool.dir=/spool-dir_
Once the hook is initialized, the directory is created. The user who creates
the directory will have read-write permissions to the spool directly.
There are cases where the hook gets initialized with different users. When that
happen, the directory is accessible to the other user. This causes
initialization failure and the spooling functionality not to be available to
the other user.
*Solution(s)*
This problem can be circumvented by making the 2 users be part of the same
group that will allow for same directory to be present for multiple users.
Multi-user access is currently supported.
For the scenario, where multiple users are not part of the same group, the
situation described above will come into play.
_Approach Used_
**No directory exists, _User1_ first creates the directory specified in the
configuration.
Directory exists, _User1_ has access to the directory and spooling is enabled.
Directory exists, _User2_ does not have access to the directory. New directory
with username suffixed to the existing directory name is created.
> Atlas Spooling: Support for User-specific Spool Directory
> ---------------------------------------------------------
>
> Key: ATLAS-4306
> URL: https://issues.apache.org/jira/browse/ATLAS-4306
> Project: Atlas
> Issue Type: Bug
> Reporter: Ashutosh Mestry
> Assignee: Ashutosh Mestry
> Priority: Major
>
> *Background*
> Spooling for messages is enabled for hooks that publish messages to Atlas.
> This is available for hooks that choose to add the following properties:
> {code:java}
> atlas.hook.spool.enabled=true
> atlas.hook.spool.dir=/spool-dir{code}
> Once the hook is initialized, the directory is created. The user who creates
> the directory will have read-write permissions to the spool directly.
> There are cases where the hook gets initialized with different users. When
> that happen, the directory is accessible to the other user. This causes
> initialization failure and the spooling functionality not to be available to
> the other user.
> *Solution(s)*
> This problem can be circumvented by making the 2 users be part of the same
> group that will allow for same directory to be present for multiple users.
> Multi-user access is currently supported.
> For the scenario, where multiple users are not part of the same group, the
> situation described above will come into play.
> _Approach Used_
> **No directory exists, _User1_ first creates the directory specified in the
> configuration.
> Directory exists, _User1_ has access to the directory and spooling is enabled.
> Directory exists, _User2_ does not have access to the directory. New
> directory with username suffixed to the existing directory name is created.
> The directory created for the user will be
>
> {code:java}
> /spool-dir-User1
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
