[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

MPhamWMF removed a project: Discovery-Search (Current work). TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: MPhamWMF Cc: Kristbaum, Jelabra, bking, pmokeefe, YOUR1, AWesterinen, CtrlZvi,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

cicalese removed a project: MediaWiki-Stakeholders-Group. TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: cicalese Cc: Jelabra, bking, pmokeefe, YOUR1, AWesterinen, CtrlZvi, Bugreporter, SirkoS,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Gehel closed subtask T299460: Evaluate the Apache Jena Framework as Resolved. TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Gehel Cc: YOUR1, AWesterinen, CtrlZvi, Bugreporter, SirkoS,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Gehel closed subtask T297473: Evaluate RDF4j API as Resolved. TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Gehel Cc: YOUR1, AWesterinen, CtrlZvi, Bugreporter, SirkoS, Eposthumus, Lectrician1,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Gehel closed subtask T206561: Evaluate Virtuoso as alternative to Blazegraph as Resolved. TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Gehel Cc: YOUR1, AWesterinen, CtrlZvi, Bugreporter,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

MPhamWMF closed subtask T306724: [EPIC] Create testing strategy for Blazegraph alternatives as Resolved. TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: MPhamWMF Cc: YOUR1, AWesterinen, CtrlZvi,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

TallTed added a comment. In T206560#7775800 , @Bugreporter wrote: > Query performance is an important point to consider - I found a query that will run one million time slower in one database engine than in another one Claims

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

MPhamWMF added a subtask: T306724: [EPIC] Create testing strategy for Blazegraph alternatives. TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: MPhamWMF Cc: AWesterinen, CtrlZvi, Bugreporter,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

MPhamWMF closed subtask T289760: Evaluate Oxigraph as alternative to Blazegraph as Declined. TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: MPhamWMF Cc: AWesterinen, CtrlZvi, Bugreporter,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

MPhamWMF closed subtask T289621: Evaluate Halyard as alternative to Blazegraph as Declined. TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: MPhamWMF Cc: AWesterinen, CtrlZvi, Bugreporter, SirkoS,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

MPhamWMF closed subtask T289561: Evaluate Apache Rya as alternative to Blazegraph as Declined. TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: MPhamWMF Cc: AWesterinen, CtrlZvi, Bugreporter,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

AWesterinen closed subtask T275398: Create an updated survey of graph backends for WDQS as Resolved. TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: AWesterinen Cc: CtrlZvi, Bugreporter, SirkoS,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Bugreporter added a comment. Query performance is an important point to consider - I found a query that will run one million time slower in one database engine than in another one TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

So9q added a subtask: T301227: Create test RDF dataset for evaluating alternatives to Blazegraph. TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: So9q Cc: Lectrician1, driib, Bovlb,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

MPhamWMF moved this task from Epics to Current work on the Wikidata-Query-Service board. MPhamWMF added a project: Discovery-Search (Current work). TASK DETAIL https://phabricator.wikimedia.org/T206560 WORKBOARD https://phabricator.wikimedia.org/project/board/891/ EMAIL PREFERENCES

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

So9q closed subtask T290082: Evaluate Apache HBase and RDF4J as alternative to Blazegraph as Declined. TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: So9q Cc: Bovlb, Dr.uesenfieber,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

AndySeaborne added a comment. Are there any timescale/triple scale goals currently being stated? With a baseline minimum of 1B triples/3 months, and assuming a 5-10 year goal for any choice, that gets to

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Justin0x2004 added a comment. also, any thoughts on https://cambridgesemantics.com/anzograph/ ? "Horizontally Scalable Graph Database Built for Online Analytics and Data Harmonization" it looks like anzograph could handle

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

nguyenm9 added a comment. any thoughts on https://github.com/IBM/expressive-reasoning-graph-store ? TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: nguyenm9 Cc: Bovlb, Dr.uesenfieber,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

AndySeaborne added a comment. We can be objective about feature support. The working group tests for SPARQL 1.1 (updated for RDF 1.1) are maintained by the community: https://w3c.github.io/rdf-tests/. They have reasonable coverage of features. In addition, engines can an do

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Hannah_Bast added a comment. In T206560#7562538 , @Fnielsen wrote: > I am taking the liberty to polute the thread with a reference to "MillenniumDB: A Persistent, Open-Source, Graph Database" https://arxiv.org/pdf/2111.01540.pdf from

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Fnielsen added a comment. I am taking the liberty to polute the thread with a reference to "MillenniumDB: A Persistent, Open-Source, Graph Database" https://arxiv.org/pdf/2111.01540.pdf from November 2021. Millennium may have some serious limitations in terms of requirements that can be

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Lydia_Pintscher added a comment. In T206560#7517212 , @BenAtOlive wrote: > Hey all, apologies if this has already been covered elsewhere, but I'm curious why Apache Jena Fuseki is not on the list of Blazegraph alternatives? It seems

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

BenAtOlive added a comment. Hey all, apologies if this has already been covered elsewhere, but I'm curious why Apache Jena Fuseki is not on the list of Blazegraph alternatives? It seems to meet the We've used Jena from time to time and really like it (it has a lot of features out of the

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Iamamz3 added a comment. There is this ticket Create list of criteria for graph backend candidates for WDQS to help reason about the future choice. TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

namedgraph added a comment. @DanBri I would agree if this issue was not specifically about "alternatives to BlazeGraph" (RDF triplestore), with explicit requirements. Finding such alternative will already be difficult if not impossible, mostly due to the open-source requirement. If you

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

AndreasKuczera added a comment. I would agree @DanBri. TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: AndreasKuczera Cc: namedgraph, Versant.2612, AndreasKuczera, DD063520, Michael, toan,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

DanBri added a comment. “Pollution” is a strong word that comes off as needlessly hostile. It seems prudent and rational to get a broad sense of the landscape(and where it is moving). The Wikidata data model is not trivially 1:1 with RDF/SPARQL and there may be scope for hybrid

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

namedgraph added a comment. @So9q @AndreasKuczera @Versant.2612 why are you polluting the thread by suggesting projects/products that clearly do not meet the requirements? This includes JanusGraph, Ontop, Neo4J etc. TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Versant.2612 added a comment. Consider property graph back ends such as Neo4J and TigerGraph Kovács, T., Simon, G., & Mezei, G. (2019). Benchmarking Graph Database Backends—What Works Well with Wikidata?. Acta Cybernetica, 24(1), 43-60. https://doi.org/10.14232/actacyb.24.1.2019.5 TASK

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Versant.2612 added a comment. Consider relational databases with particular schema as graph backends Daniel Hernández, Aidan Hogan, Cristian Riveros, Carlos Rojas, Enzo Zerega. "Querying Wikidata: Comparing SPARQL, Relational and Graph Databases". In the Proceedings of the 15th

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Versant.2612 added a comment. Create a query set (extracted from the WDQS log) and a Wikidata subset of data to benchmark against graph databases (such as TPC). Ask graph database vendors to test their products and publish the results to the community. See http://tpc.org/

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Hannah_Bast added a comment. In T206560#7430950 , @AndreasKuczera wrote: > I imported the wikidata-DB into neo4j and it works quite well. Can you be more specific? When we tested Wikidata on Neo4j several years ago, it worked in

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

AndreasKuczera added a comment. I imported the wikidata-DB into neo4j and it works quite well. TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: AndreasKuczera Cc: AndreasKuczera, DD063520,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Hannah_Bast added a comment. For whoever is interested, I wrote more about the QLever SPARQL engine on this thread: https://phabricator.wikimedia.org/T290839 . TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

So9q added a subtask: T290839: Evaluate a double backend strategy for WDQS. TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: So9q Cc: Hannah_Bast, RShigapov, Izno, KingsleyIdehen, Daniel_Mietchen,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

KingsleyIdehen added a comment. A few things: 1. This behavior is configurable i.e., we just have a restrictive timeout associated with the current public instance 2. We could also include HTML-level messaging to complement the HTTP-level messaging This feature is the result of a

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Hannah_Bast added a comment. Thanks, Kingsley, that explains it! I think it's a useful feature, but it's quite confusing that this important bit of information (whether the query result is correct or just an approximation) is contained only in the result header, but neither on the HTML

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

GreenReaper added a comment. In some cases that feature could be useful, though I suspect many would be surprised to get results from an ordered query that might not be correct with respect to the entire data set. I tried the mentioned query, setting a timeout of 0 which disables this

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

KingsleyIdehen added a comment. That's a consequence of the "Anytime Query" feature in Virtuoso that provides partial solutions in situations where a query cannot be completed within a specific timeframe. This timeframe takes the form of a configurable timeout, and is an critical feature

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Hannah_Bast added a comment. > [1] Our Live Wikidata SPARQL Query Endpoint Thanks, Kingsley. We tried your Wikidata SPARQL endpoint, in particular some queries with an ORDER BY in the end, which require the computation of a fairly large

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Gehel removed a subtask: T290244: Evaluate whether RDF Thrift is a suitable dump format. TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Gehel Cc: Izno, KingsleyIdehen, Daniel_Mietchen, Majavah,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Gehel added a subtask: T290244: Evaluate whether RDF Thrift is a suitable dump format. TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Gehel Cc: Izno, KingsleyIdehen, Daniel_Mietchen, Majavah,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Gehel added a subtask: T290240: Evaluate whether RDF Delta is a good idea to have in the backend. TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Gehel Cc: Izno, KingsleyIdehen, Daniel_Mietchen,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

So9q added a comment. I recommend the Search Team to attend the ApacheCon to gather insights from others using Big Data succesfully: https://www.apachecon.com/acah2021/tracks/bigdata.html e.g.: - Containing an Elephant: How we moved Hadoop/HBase into Kubernetes and Public Cloud

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

So9q added a subtask: T290082: Evaluate Apache HBase as alternative to Blazegraph. TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: So9q Cc: KingsleyIdehen, Daniel_Mietchen, Majavah,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

So9q added a comment. In T206560#7235915 , @So9q wrote: > See my proposal (JanusGraph with a distribued backend like Cassandra) and discussion here

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

KingsleyIdehen added a comment. For the record. At the time of our first rendezvous re Wikidata hosting, handling 20 billion+ triples would have typically required our Cluster Edition (a Commercial Only offering). That was the deal-breaker back at the time of initial Blazegraph

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

So9q added a subtask: T289760: Evaluate Oxigraph as alternative to Blazegraph. TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: So9q Cc: Daniel_Mietchen, Majavah, karapayneWMDE, MarioGom,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

So9q added a subtask: T289561: Evaluate Rya as alternative to Blazegraph. TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: So9q Cc: Majavah, karapayneWMDE, MarioGom, Mohammed_Sadat_WMDE, Hjfocs,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Thadguidry added subscribers: Tpt, Thadguidry. Thadguidry added a comment. +1 for Oxigraph. @TPT has been putting in a ton of good effort, research, features, and stability. Sponsoring him now in GitHub as well for his effort. As it's being developed in Rust, it automatically takes

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Justin0x2004 added a comment. In T206560#7248377 , @DanBri wrote: > @Lydia_Pintscher mentioned a conversation with the Data Commons team at Google, they have this opensource codebase that's somewhat in this area:

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

DanBri added subscribers: Lydia_Pintscher, DanBri. DanBri added a comment. @Lydia_Pintscher mentioned a conversation with the Data Commons team at Google, they have this opensource codebase that's somewhat in this area: https://github.com/datacommonsorg/mixer TASK DETAIL

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

So9q added a comment. See discussion here https://www.wikidata.org/wiki/Wikidata:Project_chat#Blazegraph_is_unmaintained_and_does_not_scale_-_is_JanusGraph_a_viable_replacement_for_WDQS? TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Ostrzyciel added a comment. In T206560#7068941 , @So9q wrote: > Today I presented a new found alternative to Blazegraph and the bridge in the telegram wikidata chat. > See https://github.com/ontop/ontop > Can it do the job? > No

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

So9q added a comment. Today I presented a new found alternative to Blazegraph and the bridge in the telegram wikidata chat. See https://github.com/ontop/ontop Can it do the job? No need for sparql update and moving data around it seems. Could someone take a closer look? TASK

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

GreenReaper added a comment. In T206560#6864268 , @Krabina wrote: > I don't understand the "I don't like Java" argument. Blazegraph - which is in discussion here - is also written in Java als are most (all?) other triplestores or graph

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Krabina added a comment. I don't understand the "I don't like Java" argument. Blazegraph - which is in discussion here - is also written in Java als are most (all?) other triplestores or graph databases. Do you suggest to write a new storage backend from scratch? TASK DETAIL

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Salgo60 added a comment. neo4j: I spoke with the CIO Emil last year in Stockholm and pinged Lydia about it see {T234431#5936337 } ... Emil said it was just send him an email if we would like to move this forward F34123693: image.png

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

So9q added a comment. In T206560#6849671 , @Krabina wrote: > Interesting. From my (limited) experience, neo4j seems to get a lot of attention. > > BTW: there was a discussion about triple store

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

So9q added a comment. In T206560#6608418 , @Lucas_Werkmeister_WMDE wrote: > Another option to keep an eye on is QLever . It doesn’t support SPARQL Update yet (and while the stated Wikidata reload

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Krabina added a comment. Interesting. From my (limited) experience, neo4j seems to get a lot of attention. BTW: there was a discussion about triple store experiences at the SMWCon last year inlcuding blazegraph, virtuoso and jena:

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

MPhamWMF added a subtask: T275398: Create an updated survey of graph backends for WDQS. TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: MPhamWMF Cc: Jecummings4, TomT0m, Akuckartz, Susannaanas,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Akuckartz added a comment. I tried to formulate a Wikidata use case for the development of the RDF* / RDF star specification: https://github.com/w3c/rdf-star/issues/29 TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Lucas_Werkmeister_WMDE added a comment. Another option to keep an eye on is QLever . It doesn’t support SPARQL Update yet (and while the stated Wikidata reload time of less than 24 hours is impressive, it’s not enough to replace live updates,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Aklapper changed the status of subtask T206561: Evaluate Virtuoso as alternative to Blazegraph from Stalled to Open. TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Aklapper Cc: Jecummings4,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Gehel raised the priority of this task from "Medium" to "High". TASK DETAIL https://phabricator.wikimedia.org/T206560 WORKBOARD https://phabricator.wikimedia.org/project/board/891/ EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Gehel Cc:

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Gehel added a comment. In T206560#6416757 , @Jecummings4 wrote: > I represent a research group at the Computer Science and Artificial Intelligence Laboratory at MIT. For the past year, we've been doing a lot of work with local copies

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Jecummings4 added a comment. I represent a research group at the Computer Science and Artificial Intelligence Laboratory at MIT. For the past year, we've been doing a lot of work with local copies Wikidata and have experienced our own share of frustrations with Blazegraph. We are currently

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Akuckartz added a project: MediaWiki-Stakeholders-Group. TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Akuckartz Cc: TomT0m, Akuckartz, Susannaanas, Addshore, Andrawaag, Gehel,

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Akuckartz added a comment. I think it is important to keep in mind that significant efforts are being made to unite the RDF and Property Graph communities. One aspect of this is the development of "RDF*" and "SPARQL*" (SPARQL star). BlazeGraph played and continues to play a positive role in

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

Akuckartz added a comment. What are the requirements? TASK DETAIL https://phabricator.wikimedia.org/T206560 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Akuckartz Cc: TomT0m, Akuckartz, Susannaanas, Addshore, Andrawaag, Gehel,