[
https://issues.apache.org/jira/browse/JENA-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-403.
--------------------------------
Resolution: Fixed
Fix Version/s: Jena 2.10.1
Assignee: Andy Seaborne
RIOT logging set to "error" when "-q" specificied.
(BTW the commands look for a "log4j.properties" file in the current directory
before using a built-in settings)
> sparql -q doesn't suppress riot warnings
> ----------------------------------------
>
> Key: JENA-403
> URL: https://issues.apache.org/jira/browse/JENA-403
> Project: Apache Jena
> Issue Type: Bug
> Components: Cmd line tools
> Affects Versions: Jena 2.10.0
> Reporter: Richard Cyganiak
> Assignee: Andy Seaborne
> Priority: Minor
> Fix For: Jena 2.10.1
>
>
> With an example input file test.ttl containing this single line:
> <> a < >.
> I run this command:
> bin/sparql --quiet --data test.ttl "SELECT * { ?s ?p ?o }"
> The output:
> 15:04:56 WARN riot :: [line: 1, col: 6 ] Bad IRI:
> <file:///Users/RichardCyganiak/Desktop/Jena/ > Code: 18/DOUBLE_WHITESPACE in
> PATH: Either two or more consecutive whitespace characters, or leading or
> trailing whitespace. These match no grammar rules of URIs/IRIs. These
> characters are permitted in RDF URI References, XML system identifiers, but
> not XML Schema anyURIs.
> ------------------------------------------------------------------------
> | s | p | o |
> ========================================================================
> | <test.ttl> | <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> | < > |
> ------------------------------------------------------------------------
> While the warning from riot is generally helpful, I would have expected it to
> be suppressed by the -q parameter. Having a way of suppressing such warnings
> would be rather useful for things like CONSTRUCT output, where the warnings
> make the output invalid.
> From a brief look through the code, it looks like CmdGeneral.isQuiet() is
> correctly initialized but then never read.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
