[
https://issues.apache.org/jira/browse/SENTRY-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Spector updated SENTRY-2027:
----------------------------------
Description:
Need to support triggering full updates from HMS to Sentry and from Sentry to
NameNode. WebUI is natural choice. Need dedicated servlet to pass simple
notifications to intended Sentry components plus some flexible mechanism for
components to receive those notifications. Suggested mechanism is
publish-subscribe, which is very flexible, and once implemented, allows adding
new functionality with virtually no coding effort.
Web form presents Topic and Message text fields, Submit button, and text area
for reporting information / errors back from the server. Message field can be
empty.
For example, topic "hms-sync" can trigger full update from HMS, and topic
"nn-sync" can trigger full update to NameNode.
Securing WebUI will be addressed in a separate JIRA. To mitigate security
concerns, forced sync functionality, as well as the publish-subscribe web
servlet will be disabled by default, and can be activated by reconfiguration.
The implementation is intended to be most basic.
After this mechanism is implemented, will proceed with two more JIRAs to
implement full updates for HMS and NN.
was:
Need to support triggering full updates from HMS to Sentry and from Sentry to
NameNode. WebUI is natural choice. Need dedicated servlet to pass simple
notifications to intended Sentry components plus some flexible mechanism for
components to receive those notifications. Suggested mechanism is
publish-subscribe, which is very flexible, and once implemented, allows adding
new functionality with virtually no coding effort.
Web form presents Topic and Message text fields, Submit button, and text area
for reporting information / errors back from the server. Message field can be
empty.
For example, topic "hms-sync" can trigger full update from HMS, and topic
"nn-sync" can trigger full update to NameNode.
Securing WebUI will be addressed in a separate JIRA. To mitigate security
concerns, forced sync functionality, as well as the publish-subscribe web
servlet will be disabled by default, and can be activated by reconfiguration.
The implementation is intended to be most basic.
After this mechanism is implemented, will proceed with two more JIRAs to
implement full update triggers for HMS and NN.
> Create mechanism of delivering commands via WebUI
> -------------------------------------------------
>
> Key: SENTRY-2027
> URL: https://issues.apache.org/jira/browse/SENTRY-2027
> Project: Sentry
> Issue Type: New Feature
> Reporter: Vadim Spector
> Assignee: Vadim Spector
>
> Need to support triggering full updates from HMS to Sentry and from Sentry to
> NameNode. WebUI is natural choice. Need dedicated servlet to pass simple
> notifications to intended Sentry components plus some flexible mechanism for
> components to receive those notifications. Suggested mechanism is
> publish-subscribe, which is very flexible, and once implemented, allows
> adding new functionality with virtually no coding effort.
> Web form presents Topic and Message text fields, Submit button, and text area
> for reporting information / errors back from the server. Message field can be
> empty.
> For example, topic "hms-sync" can trigger full update from HMS, and topic
> "nn-sync" can trigger full update to NameNode.
> Securing WebUI will be addressed in a separate JIRA. To mitigate security
> concerns, forced sync functionality, as well as the publish-subscribe web
> servlet will be disabled by default, and can be activated by reconfiguration.
> The implementation is intended to be most basic.
> After this mechanism is implemented, will proceed with two more JIRAs to
> implement full updates for HMS and NN.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
