Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/745#issuecomment-206705438
The implementation itself looks good to me.
While this PR links 'dynamic form' and 'angular display system', I'd like
to discuss little bit about the direction.
Zeppelin has 'dynamic form' and 'angular display system' for frontend -
backend interaction.
And 'resource pool' for interpreter-interpreter interaction. I can
summarize characteristics of these three, like
| | Dynamic Form | Angular Display System | ResourcePool |
| ------------- | ------------- | ------------- | ------------- |
| Propagate value to the font-end | yes | yes | no |
| Persisted in note.json | yes | yes | no |
| Trigger actions on change | yes | yes | no |
| Store arbitrary java object | no | yes | yes |
| Note / Paragraph scope | no | yes | yes |
| Access value between interpreters | no | no | yes |
'Dynamic Form' and 'Angular Display System' are both does frontend-backend
interaction.
'Angular Display System' and 'Resource pool' are both object store.
While they're sharing similar characteristics, do you see any possibilities
of consolidate these 3 into 1?
If it is, how this PR can be aligned?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
