Smalyshev added a comment.
Yes, but it would be done only once per redirect, and even that should be rare
True, once per redirect, but redirects are not that rare... It may be an option
though. We need to consider performance impact for this carefully.
As far as I can tell, there are
daniel added a comment.
In https://phabricator.wikimedia.org/T96490#1225281, @Smalyshev wrote:
we have to replace all occurrences of A in the graph with B (and delete
triples with A as the subject, since A's old content is now gone)
Deletion happens automatically as part of the update,
daniel added a comment.
@Smalyshev mentioned that Blazegraph has a rewrite mechanism we could use to
resolve redirects when processing updates and queries. That works when we know
that A redirects to B (we have A owl:same B). Problems arise when a
redirect is created or undone, that is, when A
Smalyshev added a comment.
Do you know if this would include only same-as for instances or also for
properties and classes?
Currently, property redirects are not allowed, though it may happen in the
future, at least in theory.
TASK DETAIL
https://phabricator.wikimedia.org/T96490
REPLY
Thompsonbry.systap added a comment.
One approach is to update the forward dictionary to make the IRIs onto one of
the existing IVs and then rewrite all of the statements. However, this sort of
destructive rewrite of does not help if you need the redirects to be
reversible.
I am pretty sure
Smalyshev added a comment.
if you need the redirects to be reversible.
I don't think redirect is reversible, but that's a good point, need to verify
that. Technically it can be reversed, as pretty much every action on wiki, but
I'm not sure if it's a normal occurrence. Will check.
Do you
