Does RDF4J offer a way to pretty print results in tabular format?
up vote
1
down vote
favorite
I am trying to pretty print the results I get from a SPARQL query in RDF4J. Is there a method or class, inside RDF4J that offers this functionality? I am not asking for other 3rd party software or additional source code (there is already a question for that with many good answers).
java rdf4j
add a comment |
up vote
1
down vote
favorite
I am trying to pretty print the results I get from a SPARQL query in RDF4J. Is there a method or class, inside RDF4J that offers this functionality? I am not asking for other 3rd party software or additional source code (there is already a question for that with many good answers).
java rdf4j
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I am trying to pretty print the results I get from a SPARQL query in RDF4J. Is there a method or class, inside RDF4J that offers this functionality? I am not asking for other 3rd party software or additional source code (there is already a question for that with many good answers).
java rdf4j
I am trying to pretty print the results I get from a SPARQL query in RDF4J. Is there a method or class, inside RDF4J that offers this functionality? I am not asking for other 3rd party software or additional source code (there is already a question for that with many good answers).
java rdf4j
java rdf4j
asked Nov 11 at 11:58
pgmank
6711826
6711826
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
There's no real "pretty printer" for query results in Rdf4j but I guess the closest is either the CSV (comma-separated-values) or TSV (tab-separated-values) writers. The Rdf4j Workbench offers these formats as options for exporting a query result. If you want to use them for programmatic execution of a query, you'd do something along these lines:
// write TSV result to STDOUT (to write to file, use a FileoutputStream instead)
SPARQLResultsTSVWriter writer = new SPARQLResultsTSVWriter(System.out);
try (RepositoryConnection conn = rep.getConnection()) {
String query = "SELECT ... ";
// execute the query and stream the result to the supplied writer
conn.prepareTupleQuery(query).evaluate(writer);
}
If you need something prettier than that, you could write your own custom query result handler, and use it in place of the SPARQLResultsTSVWriter
. To do this, create a new class that extends AbstractQueryResultWriter, and override any of the methods in there that need customization (in particular, handleNamespace
, handleSolution
, startQueryResult
and endQueryResult
). Or you could log a feature request for such a class to be added to Rdf4j (or even better: write it yourself then contribute to the project :))
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
There's no real "pretty printer" for query results in Rdf4j but I guess the closest is either the CSV (comma-separated-values) or TSV (tab-separated-values) writers. The Rdf4j Workbench offers these formats as options for exporting a query result. If you want to use them for programmatic execution of a query, you'd do something along these lines:
// write TSV result to STDOUT (to write to file, use a FileoutputStream instead)
SPARQLResultsTSVWriter writer = new SPARQLResultsTSVWriter(System.out);
try (RepositoryConnection conn = rep.getConnection()) {
String query = "SELECT ... ";
// execute the query and stream the result to the supplied writer
conn.prepareTupleQuery(query).evaluate(writer);
}
If you need something prettier than that, you could write your own custom query result handler, and use it in place of the SPARQLResultsTSVWriter
. To do this, create a new class that extends AbstractQueryResultWriter, and override any of the methods in there that need customization (in particular, handleNamespace
, handleSolution
, startQueryResult
and endQueryResult
). Or you could log a feature request for such a class to be added to Rdf4j (or even better: write it yourself then contribute to the project :))
add a comment |
up vote
0
down vote
There's no real "pretty printer" for query results in Rdf4j but I guess the closest is either the CSV (comma-separated-values) or TSV (tab-separated-values) writers. The Rdf4j Workbench offers these formats as options for exporting a query result. If you want to use them for programmatic execution of a query, you'd do something along these lines:
// write TSV result to STDOUT (to write to file, use a FileoutputStream instead)
SPARQLResultsTSVWriter writer = new SPARQLResultsTSVWriter(System.out);
try (RepositoryConnection conn = rep.getConnection()) {
String query = "SELECT ... ";
// execute the query and stream the result to the supplied writer
conn.prepareTupleQuery(query).evaluate(writer);
}
If you need something prettier than that, you could write your own custom query result handler, and use it in place of the SPARQLResultsTSVWriter
. To do this, create a new class that extends AbstractQueryResultWriter, and override any of the methods in there that need customization (in particular, handleNamespace
, handleSolution
, startQueryResult
and endQueryResult
). Or you could log a feature request for such a class to be added to Rdf4j (or even better: write it yourself then contribute to the project :))
add a comment |
up vote
0
down vote
up vote
0
down vote
There's no real "pretty printer" for query results in Rdf4j but I guess the closest is either the CSV (comma-separated-values) or TSV (tab-separated-values) writers. The Rdf4j Workbench offers these formats as options for exporting a query result. If you want to use them for programmatic execution of a query, you'd do something along these lines:
// write TSV result to STDOUT (to write to file, use a FileoutputStream instead)
SPARQLResultsTSVWriter writer = new SPARQLResultsTSVWriter(System.out);
try (RepositoryConnection conn = rep.getConnection()) {
String query = "SELECT ... ";
// execute the query and stream the result to the supplied writer
conn.prepareTupleQuery(query).evaluate(writer);
}
If you need something prettier than that, you could write your own custom query result handler, and use it in place of the SPARQLResultsTSVWriter
. To do this, create a new class that extends AbstractQueryResultWriter, and override any of the methods in there that need customization (in particular, handleNamespace
, handleSolution
, startQueryResult
and endQueryResult
). Or you could log a feature request for such a class to be added to Rdf4j (or even better: write it yourself then contribute to the project :))
There's no real "pretty printer" for query results in Rdf4j but I guess the closest is either the CSV (comma-separated-values) or TSV (tab-separated-values) writers. The Rdf4j Workbench offers these formats as options for exporting a query result. If you want to use them for programmatic execution of a query, you'd do something along these lines:
// write TSV result to STDOUT (to write to file, use a FileoutputStream instead)
SPARQLResultsTSVWriter writer = new SPARQLResultsTSVWriter(System.out);
try (RepositoryConnection conn = rep.getConnection()) {
String query = "SELECT ... ";
// execute the query and stream the result to the supplied writer
conn.prepareTupleQuery(query).evaluate(writer);
}
If you need something prettier than that, you could write your own custom query result handler, and use it in place of the SPARQLResultsTSVWriter
. To do this, create a new class that extends AbstractQueryResultWriter, and override any of the methods in there that need customization (in particular, handleNamespace
, handleSolution
, startQueryResult
and endQueryResult
). Or you could log a feature request for such a class to be added to Rdf4j (or even better: write it yourself then contribute to the project :))
edited Nov 13 at 1:50
answered Nov 12 at 22:14
Jeen Broekstra
15.8k43759
15.8k43759
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53248506%2fdoes-rdf4j-offer-a-way-to-pretty-print-results-in-tabular-format%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown