[jira] [Commented] (JENA-2055) handle properly the denied access generated by jena-permission security evaluator

2021-02-27 Thread info parlepeuple (Jira)
[ https://issues.apache.org/jira/browse/JENA-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17292317#comment-17292317 ] info parlepeuple commented on JENA-2055: [~andy] thank you for looking into this issue. I can

[jira] [Updated] (JENA-2055) handle properly the denied access generated by jena-permission security evaluator

2021-02-27 Thread info parlepeuple (Jira)
[ https://issues.apache.org/jira/browse/JENA-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] info parlepeuple updated JENA-2055: --- Attachment: localData.ttl ShiroEvaluator.java pom.xml >

Re: Having arq accept stdin as alternative to --data parameter?

2021-02-27 Thread Bob DuCharme
riot does it nicely. That's what inspired me to request that arq do it. Thanks, Bob On 2/27/21 5:01 PM, Colin Gross wrote: Bob, Yes. I mistakenly tested passing stdin as the --query argument. The --data argument apparently keys the input type from the suffix of the filename. That makes

[jira] [Commented] (JENA-2055) handle properly the denied access generated by jena-permission security evaluator

2021-02-27 Thread Andy Seaborne (Jira)
[ https://issues.apache.org/jira/browse/JENA-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17292246#comment-17292246 ] Andy Seaborne commented on JENA-2055: - [~infoplp] - what operation are you using to test the patch? I

Re: Having arq accept stdin as alternative to --data parameter?

2021-02-27 Thread Colin Gross
Bob, Yes. I mistakenly tested passing stdin as the --query argument. The --data argument apparently keys the input type from the suffix of the filename. That makes it a bit more of a pain to deal with. #!/bin/sh # Write some sample data. cat << DATADOC > /tmp/data.n3 @prefix :

Re: Having arq accept stdin as alternative to --data parameter?

2021-02-27 Thread Bob DuCharme
That looked promising to me, but with Jena 3.3 under Ubuntu it gave me "Failed to load data". Wouldn't there need to be some way to indicate which serialization the data was using? Thanks, Bob On 2/27/21 2:47 PM, Colin Gross wrote: Bob, Have you tried passing /dev/stdin as the argument

Re: Having arq accept stdin as alternative to --data parameter?

2021-02-27 Thread Colin Gross
Bob, Have you tried passing /dev/stdin as the argument for --data? E.g: arq --query=example.rq --data=/dev/stdin That should wait on stdin until it hits EOF (ctrl+d). This should let you piping from a file or wherever E.g. cat people.n3 | arq --query=example.rq --data=/dev/stdin If you need to

[jira] [Updated] (JENA-2056) Remove oaj.riot.checker code, replace with a library

2021-02-27 Thread Andy Seaborne (Jira)
[ https://issues.apache.org/jira/browse/JENA-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne updated JENA-2056: Summary: Remove oaj.riot.checker code, replace with a library (was: Remove oaj.riot.checker code,

Having arq accept stdin as alternative to --data parameter?

2021-02-27 Thread Bob DuCharme
This is just an idea. I like how jena's riot utility accepts data from stdin as long as you provide a --syntax parameter to tell it what serialization the stdin triples are. When I was at TopQuadrant I liked SPARQLMotion, their proprietary system for pipelining RDF through various steps to