Previously, Stardog used to have the ability when creating a vgraph to specify it should be available to "all databases" and now I'm noticing that selecting a single database appears to be mandatory. This would seem to make it impossible now to query the same vgraph from multiple databases, which in my view is unnecessarily limiting. For example, if I want to materialize data from a vgraph into different databases, or, using edge properties asserted within the vgraph to selectively materialize parts of the vgraph into different databases. Why/when did this behavior change? (Curiously, I still have vestigial vgraphs that are available to all databases that were likely grandfathered through version upgrades.) It also appears that if the database that a vgraph is tied to is dropped that the previously associated vgraph effectively becomes orphaned and unusable?
Ideally, I'd be able to select which databases (or all) a vgraph should be queryable from, not being forced to pick just one. What is my recourse now, replicate vgraphs for every db I want to query them from? This is a maintenance nightmare.
Hey Dan,
indeed, the option "all databases" was recently removed in Studio to prevent an accidental usage of this scope and latencies when querying upon irrelevant databases. Please note, the command line interface (virtual add) still supports and even defaults to this scope ( --database "*"). I am following your explanation of how this GUI restriction impacts the reuse and handling of virtual graphs in Studio and created the feature request STA-800: Restore "all databases" scope for virtual graphs in Studio, adding your valid proposal to explicitly restrict the applicable databases (via a multi-select).
Thank you!
Jaro
Hi Jaro - thanks so much for quick response and action on it. Appreciate the tip that I can still use the all-db option via CLI, will look into that instead. Of course, we'll have other users that won't be CLI-savvy so definitely would like this incorporated back into the Studio UI. And yes, please add multi-select, AND the ability to change this after the vgraph has been created. Currently, it's impossible (via Studio) to change which db(s) the vgraph is tied to, which just creates unnecessary work in deleting and recreating it just to change the db setting. (I'd really welcome the ability to rename vgraphs in Studio post-creation too, but that's likely a separate feature request)
Hello Dan,
apologies for my belated response! I've created the feature request STA-802: Update-able virtual graph metadata along your proposal to support renaming virtual graphs (e.g. in case of typos, versioned names etc.) and changing the associated database, preferably multi-selecting applicable databases.
Cheers!
Jaro