Dear Guillaume,
On Thu, 9 Jul 2020 at 15:23, Guillaume Lederrey
wrote:
> We've been hard at work on Wikimedia Commons Query Service (WCQS) [2].
> This will be a SPARL endpoint similar to WDQS, but serving the Structured
> Data on Commons dataset. Our goal is to open a beta service, hosted on
>
On Thu, Jul 9, 2020 at 4:52 PM Egon Willighagen
wrote:
>
> Dear Guillaume,
>
> On Thu, Jul 9, 2020 at 3:23 PM Guillaume Lederrey
> wrote:
>
>> Some very preliminary analysis indicates that less then 2% of the queries
>> on WDQS generate more than 90% of the load. This is definitely something we
Dear Guillaume,
On Thu, Jul 9, 2020 at 3:23 PM Guillaume Lederrey
wrote:
> Some very preliminary analysis indicates that less then 2% of the queries
> on WDQS generate more than 90% of the load. This is definitely something we
> need to better understand.
>
Is the data behind that available? I
On Thu, Jul 9, 2020 at 3:35 PM Gerard Meijssen
wrote:
> Hoi,
> Is this different from Special:MediaSearch ??
>
I'm assuming that you are asking if the new WCQS is different from the
Special:MediaSearch prototype [1].
And yes, it is quite different. WCQS is a low level SPARQL interface,
Hoi,
Is this different from Special:MediaSearch ??
Thanks,
GerardM
On Thu, 9 Jul 2020 at 15:23, Guillaume Lederrey
wrote:
> Hello all!
>
> The Search Platform team will join the WIkidata office hours on July 21st
> 16:00 UTC [1]. We are looking forward to discussing Wikidata Query Service
Hello all!
The Search Platform team will join the WIkidata office hours on July 21st
16:00 UTC [1]. We are looking forward to discussing Wikidata Query Service
and anything else you might find of interest.
We've been hard at work on Wikimedia Commons Query Service (WCQS) [2]. This
will be a
Hello all!
I hope you are all doing well in these interesting times! We are doing our
best to continue moving forward, but there is no doubt that the COVID-19
situation is affecting our work. Unexpected schedules, kids homeschooling,
loved ones and family affected, or just the overall stress
You'll love Flink. I'd encourage using Apache Beam on top of Flink and use
the unified API. That way you can take advantage of Java AND Python and Go
(something that will be important for your teams)
https://flink.apache.org/ecosystem/2020/02/22/apache-beam-how-beam-runs-on-top-of-flink.html
Hello all!
Here is a short update on what we have been doing around WDQS lately.
The update lag over the last 30 days has been slightly better [1]. We have
not done anything more to improve it, or to analyze why it was less
problematic lately. My guess is that it is a combination of being lucky
