[
https://issues.apache.org/jira/browse/JENA-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900510#comment-14900510
]
Stian Soiland-Reyes commented on JENA-1032:
-------------------------------------------
There's also the issue that for multiple files, INFO lines appear in stdout,
and so it's hard to get just the triples/quads from redirecting, requiring
--quiet which might not immediately be obvious. (that might be another issue,
though, perhaps logging should go to stderr from the command line)
Repurposing --output would be ideal if we hadn't already released 3.0.0; that
would be a breaking change for command line users. -o make sense though, if not
a tiny bit confusing as it looks like shortening of --output.
> riot --to-file parameter
> ------------------------
>
> Key: JENA-1032
> URL: https://issues.apache.org/jira/browse/JENA-1032
> Project: Apache Jena
> Issue Type: Improvement
> Components: RIOT
> Affects Versions: Jena 3.0.0
> Reporter: Stian Soiland-Reyes
> Priority: Minor
> Labels: file, output
>
> The {{riot}} command line does not have an option to specify the output file
> to write to, forcing users to use shell redirections, e.g.
> {code}
> riot file.ttl > file.nt
> {code}
> This comes up as an issue for the Docker image
> https://hub.docker.com/r/stain/jena/ - as you can't (easily) do {{>
> file.txt}} as arguments to docker run to do redirections within the Docker
> container.
> Lacking an output file parameter also makes it harder to call riot from other
> programming languages, e.g. called from a Python script.
> The problem is that the {{--output}} parameter (and --out) is already used to
> specify the output FORMAT rather than the output FILE. Perhaps --to-file ?
> Suggested use:
> {code}
> riot --output jsonld --to-file /tmp/output.jsonld /tmp/input.ttl
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
