You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are catalogs of interest spread across the kowalski, gloria, and melman machines. It would be optimal to be able to use one query to get data without needing to specify the machine on which it resides.
A good longer-term solution could be sharding (e.g. here). For the short term, see this PR to penquins that introduces a new KowalskiInstances class that authenticates each machine and queries the one containing the catalog of interest. If/when this PR gets approved, we should revise the scope code to include this functionality, preempting confusion amid the growing number of machines.
The text was updated successfully, but these errors were encountered:
There are catalogs of interest spread across the
kowalski
,gloria
, andmelman
machines. It would be optimal to be able to use one query to get data without needing to specify the machine on which it resides.A good longer-term solution could be sharding (e.g. here). For the short term, see this PR to
penquins
that introduces a newKowalskiInstances
class that authenticates each machine and queries the one containing the catalog of interest. If/when this PR gets approved, we should revise the scope code to include this functionality, preempting confusion amid the growing number of machines.The text was updated successfully, but these errors were encountered: