Addshore added a comment.
Ping @Lydia_PintscherTASK DETAILhttps://phabricator.wikimedia.org/T209880EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Michael, AddshoreCc: Addshore, Lucas_Werkmeister_WMDE, WMDE-leszek, _jensen, johl, Aklapper, Lydia_Pintscher,
Addshore added a comment.
In T209880#4805698, @Michael wrote:
api url
With this line, I just wanted to point out that we currently have only the entity url configured e.g. https://wikidata.beta.wmflabs.org/entity/, but we may want to explicitly configure the url for the api instead of
Michael added a comment.
Currently, we would only query one federated instance, because any entity type can only be provided by a single repository (the local one or a federated one). That will change in the future, but even then, I don’t think many installs will have more than two or three repos
Lucas_Werkmeister_WMDE added a comment.
Hm, I don’t think that’s something we need to deal with at the Wikibase level… I feel like this is something that’s best dealt with at the HTTP proxy level. Apart from the other repo’s IP address (that the request is coming from), the current instance
Michael added a comment.
In T209880#4800645, @Lucas_Werkmeister_WMDE wrote:
[...] Or is this a blacklist/whitelist on the target repo, so that e. g. Wikidata would refuse to be a foreign repo for Metapedia?
Yes, that was the usage I thought of. How do we handle badly configured instances that
Lucas_Werkmeister_WMDE added a comment.
I don’t understand this part:
blocking/blacklisting Wikibase installations that want to federate
option to whitelist them instead?
The federation setup is part of the site configuration (I assume), so where would a blacklist or whitelist apply? If the
Michael added a comment.
What is Needed to make MultipleRepositoryAwareWikibaseServices use an API?
Case Study: PropertyInfoLookup
Interface: \Wikibase\Lib\Store\PropertyInfoLookup
3 relevant implementations:
CachingPropertyInfoLookup
DispatchingPropertyInfoLookup
PropertyInfoTable
Only
Lydia_Pintscher added a comment.
Yeah. It's definitely something that will come up. But let's take it one step at a time. As the next step not mixing entities from several repositories for the same entity type seems good enough.TASK DETAILhttps://phabricator.wikimedia.org/T209880EMAIL
WMDE-leszek added a comment.
As far as I’m aware, our current federation is not only restricted by the requirement of database access, but also by the fact that each entity type is bound to one repository, and it is not possible to mix entities of the same type from multiple repositories.
Lucas_Werkmeister_WMDE added a comment.
As far as I’m aware, our current federation is not only restricted by the requirement of database access, but also by the fact that each entity type is bound to one repository, and it is not possible to mix entities of the same type from multiple
10 matches
Mail list logo