Github user ravwojdyla commented on the issue:
https://github.com/apache/zeppelin/pull/1471
@felixcheung after going through the `BeamInterpreter`, I don't see
immediate technical advantage of sharing the group, current implementation of
`BeamInterpreter`, is actually pure Java interpreter, they would not share any
configuration. That said from strictly logical point of view it makes sense for
them to be in the same group - given they share the same model.
What kind of changes are needed to put scio in the same group as beam? And
what is gonna be the impact on users?
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
