You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jena.apache.org by afs <gi...@git.apache.org> on 2017/11/16 08:51:11 UTC

[GitHub] jena pull request #311: JENA-1424: load http

GitHub user afs opened a pull request:

    https://github.com/apache/jena/pull/311

    JENA-1424: load http

    There is also a has a minor change to `RDFParser`/`RDFParserBuilder` to put the convenience operations for parse-to-graph and parse-to-dataset on a `RDFParser`, not just on `RDFParserBuilder`.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/afs/jena JENA-1424-LOAD-http

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/jena/pull/311.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #311
    
----
commit f0255f1a032753dc8c8c39f83555f8c85945de7c
Author: Andy Seaborne <an...@apache.org>
Date:   2017-11-15T23:26:27Z

    RDFParser.parse for graph and datasetgraph

commit c3d6d17894b98f5fb340964cdd8e2f269e27acf0
Author: Andy Seaborne <an...@apache.org>
Date:   2017-11-15T23:26:47Z

    JENA-1424: LOAD with conneg

----


---

[GitHub] jena pull request #311: JENA-1424: load http

Posted by asfgit <gi...@git.apache.org>.

Github user asfgit closed the pull request at:

    https://github.com/apache/jena/pull/311


---

[GitHub] jena issue #311: JENA-1424: load http

Posted by osma <gi...@git.apache.org>.

Github user osma commented on the issue:

    https://github.com/apache/jena/pull/311
  
    Wow @afs, you're super quick!


---

[GitHub] jena issue #311: JENA-1424: load http

Posted by afs <gi...@git.apache.org>.

Github user afs commented on the issue:

    https://github.com/apache/jena/pull/311
  
    This includes efficiency improvement as well. For a non-SILENT LOAD into one of the fully transactional stores, it is done direct, no read buffering to deal with pesky syntax errors. If it goes wrong, the exception propagates up and the transaction aborts as normal (if `Txn` is used or the transaction cycle is written out long form properly).


---