Thanks Andrey.
I think option one is a bad UX, cause creating an interpreter isn't
a) a simple button click (might be improved later on by Z. folks)
b) what if I have 25 different caches and the equal number of interpreters
and need to make a change to all of them? The second option sounds good, yet the interpreter still needs to have a particular cache name in the configuration, which now looks weird because I am working with multiple caches at once. It is possible to avoid specifying the cache name all together, in which case a user will have to simply go with what you call cross-cache queries? Cos On Thu, Jan 14, 2016 at 07:22PM, Andrey Gura wrote: > Cos, > > you have two options in order to create different notebooks for separate > caches: > > 1. You can create separate interpreter with cpecific configuration for each > notebook. Then you can bind interpreters to notebooks. You can also bind > many interpreters to oone notebook and use different interpreters in > different paragraphs. > > 2. You can use cross-cache like queries with one interpreter. From docs: > "In this case, cache names act as schema names in regular SQL. This means > all caches can be referred by cache names in quotes."
signature.asc
Description: Digital signature
