Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/3024
I plan to introduce one paragraph property to indicate whether the result
should be put into ResourcePool (Because I think most of time people don't want
to save it into ResourcePool, so it doesn't make sense to save it into
ResourcePool by default). The following is what I imagine.
```
%spark(saveToResourcePool=true)
...
spark code
...
```
Regarding your scenario of multiple tables, I am not sure the exact
scenario, But at least we could introduce more fine grained properties to
control that. It would be better to share your real scenario, so that we can
see which approach is better.
---
