Thompsonbry.systap added a comment.

It might be useful to take some of these questions to the bigdata-developers 
mailing list.   Some of these questions already have answers on the wiki.

1. RDR Syntax.  For the RDR exception, please create a unit test.  There are a 
few places where that test could be written.  For example 
TestReificationDoneRightEval (core SPARQL evaluation test suite) or 
TestRDROperations (test evaluation against the REST end point).

2. It would be great to get a set of queries for performance testing the 
wikidata dump.  This might be a query plan issue.  I can try to run it against 
a local copy that I've loaded from the following files, but this might be 
different data.  I suggest that having a SPARQL end point that was open to the 
group might be useful.

wget 
http://tools.wmflabs.org/wikidata-exports/rdf/exports/20150126/wikidata-terms.nt.gz
 
wget 
http://tools.wmflabs.org/wikidata-exports/rdf/exports/20150126/wikidata-properties.nt.gz
wget 
http://tools.wmflabs.org/wikidata-exports/rdf/exports/20150126/wikidata-statements.nt.gz
wget 
http://tools.wmflabs.org/wikidata-exports/rdf/exports/20150126/wikidata-simple-statements.nt.gz
wget 
http://tools.wmflabs.org/wikidata-exports/rdf/exports/20150126/wikidata-taxonomy.nt.gz
wget 
http://tools.wmflabs.org/wikidata-exports/rdf/exports/20150126/wikidata-instances.nt.gz

3. Not sure off hand what is happening here.  However, this could be a type 
casting issue.  xsd:dateTime and xsd:gYear are not the same thing.  They would 
be indexed as different data types.  A key range scan on one would not 
intersect with a key-range scan on the other.

4. We are doing a lot of work on deployers.  The HAJournalServer page of the 
wiki documents a lot of these options.  Try doing "ant stage" and then using 
either the startNSS or the startHAServices scripts.  These share a lot of the 
options and expose a lot of the options that are supported.  @brad is the point 
person on the developers work.

5. Backup: You can not obtain a coherent copy of the journal if there are 
writers executing.  If you suspect writes at the application layer, then this 
works.  HA provides online backup. This is documented on the HAJournalServer 
page of the blazegraph wiki. There are two kinds of online back. Snapshots, 
which are coherent compressed (Gzip) views of the database.  Transaction logs 
(called HALog files) which are per commit point logs of the write set of the 
transaction at the lowest level.  Both are fully online and do not block 
writers or readers.  You can also deploy an HA1 mode that does online backup, 
but the standard NSS does not support this.


TASK DETAIL
  https://phabricator.wikimedia.org/T92308

REPLY HANDLER ACTIONS
  Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign 
<username>.

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Smalyshev, Thompsonbry.systap
Cc: Thompsonbry.systap, Haasepeter, Beebs.systap, Manybubbles, Aklapper, 
Smalyshev, jkroll, Wikidata-bugs, Jdouglas, aude, GWicke, daniel, JanZerebecki



_______________________________________________
Wikidata-bugs mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

Reply via email to