[jira] [Commented] (JENA-966) LazyIterator
[
https://issues.apache.org/jira/browse/JENA-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14591752#comment-14591752
]
A. Soroka commented on JENA-966:
Yes. Is that problematic? Isn't the larger strategy to shift non-Jena-specific
stuff into {{jena-base}} and Atlas?
LazyIterator
Key: JENA-966
URL: https://issues.apache.org/jira/browse/JENA-966
Project: Apache Jena
Issue Type: Bug
Components: Core
Affects Versions: Jena 3.0.0
Reporter: Claude Warren
Assignee: Claude Warren
LazyIterator is an abstract class. The documentation indicates that the
create() method needs to be overridden to create an instance. From this I
would expect that
now LazyIterator(){
@Override
public ExtendedIteratorModel create() {
...
}};
Would work however LazyIterator does not override:
remoteNext(), andThen(), toList(), and toSet().
I believe these should be implemented in the class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] jena pull request:
Github user ajs6f commented on the pull request: https://github.com/apache/jena/commit/6570c25be8c6e958a5647a7d2c1e23466498b332#commitcomment-11746591 Oh, I see you added a different commit-- cool! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (JENA-966) LazyIterator
[
https://issues.apache.org/jira/browse/JENA-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14591746#comment-14591746
]
A. Soroka commented on JENA-966:
I don't think iterator refactoring is what is being discussed here. I think
what is being discussed is removing classes that aren't ever used and show no
likelihood of being used. But maybe I'm misinterpreting [~claudenw]'s remarks.
LazyIterator
Key: JENA-966
URL: https://issues.apache.org/jira/browse/JENA-966
Project: Apache Jena
Issue Type: Bug
Components: Core
Affects Versions: Jena 3.0.0
Reporter: Claude Warren
Assignee: Claude Warren
LazyIterator is an abstract class. The documentation indicates that the
create() method needs to be overridden to create an instance. From this I
would expect that
now LazyIterator(){
@Override
public ExtendedIteratorModel create() {
...
}};
Would work however LazyIterator does not override:
remoteNext(), andThen(), toList(), and toSet().
I believe these should be implemented in the class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] jena pull request:
Github user ajs6f commented on the pull request: https://github.com/apache/jena/commit/6570c25be8c6e958a5647a7d2c1e23466498b332#commitcomment-11746416 Okay, but isn't the build broken now? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: Lucene index synchro on triple deletion (jena-t...
Github user amiara514 commented on the pull request: https://github.com/apache/jena/pull/53#issuecomment-113273093 @afs like for the other doc I put it in a gist : https://gist.github.com/amiara514/ef839adb7c5cb9dd697d It covers only the Deletion of Indexed Entities section of text-query.mdtext --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: Lucene index synchro on triple deletion (jena-t...
Github user afs commented on the pull request: https://github.com/apache/jena/pull/53#issuecomment-113289019 Great - I'll integrate it as soon as I have a moment free to do so. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
SPARQL 1.1 Graph Store Protocol and Fuseki
I seem to be going around in circles with the fuseki documentation.
Does Fuseki support the POST command as noted at
http://www.w3.org/TR/2013/REC-sparql11-http-rdf-update-20130321/#http-post
(I believe it does from reading the docs)
I am attempting to execute an INSERT
I have started fuseki on my linux system using
fuseki-server -mem /tst
I am using the Apache httpcomponents library
I am posting to http://localhost:3030/tst/data?default
I have set the content type to text/turtle
the text that is being posted is
INSERT DATA
{
urn:foo:s urn:foo:p urn:foo:o .
}
The fuseki log shows:
[2015-06-18 07:20:32] Fuseki INFO [1] POST
http://localhost:3030/tst/data?default
[2015-06-18 07:20:32] Fuseki INFO [1] POST /tst :: 'data' ::
[text/turtle charset=UTF-8] ? default
[2015-06-18 07:20:32] Fuseki ERROR [line: 1, col: 1 ] Out of place:
[KEYWORD:INSERT]
[2015-06-18 07:20:32] Fuseki INFO [1] 400 Parse error: [line: 1, col:
1 ] Out of place: [KEYWORD:INSERT] (62 ms)
The BasicHttpResponse I am getting back is:
HTTP/1.1 400 Parse error: [line: 1, col: 1 ] Out of place: [KEYWORD:INSERT]
[Fuseki-Request-ID: 2, Server: Fuseki (2.0.0-SNAPSHOT), Content-Type:
text/plain; charset=UTF-8, Cache-Control:
must-revalidate,no-cache,no-store, Pragma: no-cache, Content-Length: 147]
ResponseEntityProxy{[Content-Type: text/plain;
charset=UTF-8,Content-Length: 147,Chunked: false]}
I must be doing something silly. Does anyone see what the issue is?
Claude
--
I like: Like Like - The likeliest place on the web
http://like-like.xenei.com
LinkedIn: http://www.linkedin.com/in/claudewarren
Re: [ANN] GSoC 2015 Accepts a Student Project for Jena
Hi Qihong, You may have already received an email from Google, which reminded us of the mid-term evaluation for the GSoC project. The evaluation will start next Friday, 26 June. The deadline to submit your evaluation is 19:00 UTC on Friday, 3 July. Please make sure not to miss it. More importantly, you're supposed to deliver your work according to the proposal before that. At least, I need to check the following output for the evaluation of your work: 1) the grammar definition: normative definition of the syntax 2) the new master.jj, arq.jj, with sparql_11.jj unchanged. 3) the code of new QueryExecution operations: execConstrucQuads(), execConstructDataset() 4) some test code for the above, OR at least some examples/demos to prove your work Best regards, Ying Jiang On Mon, Jun 15, 2015 at 6:54 PM, Qihong Lin confidence@gmail.com wrote: Hi, I just opened 2 new threads. Your comments are welcome! regards, Qihong On Mon, Jun 15, 2015 at 4:45 PM, Rob Vesse rve...@dotnetrdf.org wrote: Folks Could you please either start new threads of change the subject line appropriately for future discussions on this The generic subject line makes it hard when catching up with emails to see at a glance what this thread is about Thanks, Rob On 14/06/2015 12:28, Andy Seaborne a...@apache.org wrote: Hi, Would it be possible to add new methods constructors to Template.java while leaving the existing methods/constructors in-place (reimplemented in Template; that does not affect the SPARQL 1.0 parser). Then the source code for the SPARQL 1.0 parser does not need change. The main (and only, I think) use from the SPARQL 1.0 grammar is the constructor new Template(basic graph pattern). So if there is a constructor to match that, the generated source code for SPARQL 1.0 does not need to change (it may need to recompiled but that's happening anyway). Another constructor can take a QuadPattern. getTriple/getBGP only returns the default graph related triples. A new getQuads returns everything. Is there some code on github for the changes to Template to look at? If you drop some links here, I'll try to find some time to take a look soon. Don't worry too much at this stage - If SPARQL 1.0 gets in the way too much of you making progress, then delete it from your code (but note the fact so we can be careful when merging pull requests later!!) Andy On 14/06/15 05:16, Ying Jiang wrote: Hi Qihong, It doesn't matter. For a temperate solution, just change the code of SPARQL_10 manually to make the compiling work. Please don't wait the answers from the list. Many of the questions do not stop you from coding. We would be glad if you can deliver your code as soon/often as possible. Best regards, Ying Jiang On Fri, Jun 12, 2015 at 9:54 AM, Qihong Lin confidence@gmail.com wrote: Hi, If the checksum and grammar script is OK, I'd like to continue coding. However, the grammar script only generates ARQ and SPARQL_11, without touching SPARQL_10. If I change the code of, e.g. Template [1], it will affect SPARQL_10. Shall I modify the code of SPARQL_10 manually, change the sparql_10.jj grammar manually, or re-generate SPARQL_10 with the grammar script (and how?) ? regards, Qihong [1] https://github.com/confidencesun/jena/blob/master/jena-arq/src/main/java /org/apache/jena/sparql/syntax/Template.java On Fri, Jun 12, 2015 at 12:10 AM, Ying Jiang jpz6311...@gmail.com wrote: Hi Qihong, Have you modified any files? If the grammar file is identical, the checksum of each generated java class should be the same. Best regards, Ying Jiang On Mon, Jun 8, 2015 at 5:27 PM, Qihong Lin confidence@gmail.com wrote: Hi, The grammar has been modified for the problems you pointed out. I've tried to run grammar script to generate arq.jj, sparql_11.jj and their parser java classes, in cygwin with JavaCC 5.0. However the generated java classes are different from those in the code base: 1) ARQParser - the new generated one: public class ARQParser extends ARQParserBase implements ARQParserConstants - the old one in the code base: public class ARQParser extends ARQParserBase There's no such difference for SPARQLParser11 (both new and old ones have implements ...) 2) checksum for Token, ParseException, JavaCharStream and so on - the new generated one (Token.java): /* JavaCC - OriginalChecksum=335d1922781852977208d5cdca0fc164 (do not edit this line) */ - the old one in the code base (Token.java): /* JavaCC - OriginalChecksum=d9b4c8c9332fa3054a004615fdb22b89 (do not edit this line) */ The log from grammar script seems OK: $ ./grammar Process grammar -- sparql_11.jj Java Compiler Compiler Version 5.0 (Parser Generator) (type javacc with no arguments for help) Reading from file sparql_11.jj . . . File TokenMgrError.java does not exist. Will create one. File ParseException.java does not exist. Will create one. File Token.java does not exist. Will
Re: SPARQL 1.1 Graph Store Protocol and Fuseki
On 18/06/15 07:26, Claude Warren wrote:
I seem to be going around in circles with the fuseki documentation.
Does Fuseki support the POST command as noted at
http://www.w3.org/TR/2013/REC-sparql11-http-rdf-update-20130321/#http-post
To reword slightly to make the boundary clear: my emphasis:
[[
POST /rdf-graph-store?default HTTP/1.1
Host: example.com
Content-Type: text/turtle
** RDF payload **
is considered to have the same effect as:
INSERT DATA { ** RDF payload ** }
]]
There are two sections there.
(I believe it does from reading the docs)
It does.
I am attempting to execute an INSERT
which is not in the Graph Store Protocol.
http://www.w3.org/TR/sparql11-protocol/#update-operation
for sending SPARQL Updates.
I have started fuseki on my linux system using
fuseki-server -mem /tst
I am using the Apache httpcomponents library
I am posting to http://localhost:3030/tst/data?default
Graph Store Protocol != SPARQL Update over HTTP
The SPARQL Update endpoint is usually:
http://localhost:3030/tst/update
whereas you can POST RDF data to the default graph, with conneg:
http://localhost:3030/tst/data?default
I have set the content type to text/turtle
the text that is being posted is
INSERT DATA
{
urn:foo:s urn:foo:p urn:foo:o .
}
The fuseki log shows:
[2015-06-18 07:20:32] Fuseki INFO [1] POST
http://localhost:3030/tst/data?default
[2015-06-18 07:20:32] Fuseki INFO [1] POST /tst :: 'data' ::
[text/turtle charset=UTF-8] ? default
Conneg has decided on
text/turtle
INSERT DATA
is not Turtle.
[2015-06-18 07:20:32] Fuseki ERROR [line: 1, col: 1 ] Out of place:
[KEYWORD:INSERT]
[2015-06-18 07:20:32] Fuseki INFO [1] 400 Parse error: [line: 1, col:
1 ] Out of place: [KEYWORD:INSERT] (62 ms)
The BasicHttpResponse I am getting back is:
HTTP/1.1 400 Parse error: [line: 1, col: 1 ] Out of place: [KEYWORD:INSERT]
[Fuseki-Request-ID: 2, Server: Fuseki (2.0.0-SNAPSHOT), Content-Type:
text/plain; charset=UTF-8, Cache-Control:
must-revalidate,no-cache,no-store, Pragma: no-cache, Content-Length: 147]
ResponseEntityProxy{[Content-Type: text/plain;
charset=UTF-8,Content-Length: 147,Chunked: false]}
I must be doing something silly. Does anyone see what the issue is?
Claude
Andy
Re: SPARQL 1.1 Graph Store Protocol and Fuseki
DOH!
Thank you Andy for pointing out the obvious.
Claude
On Thu, Jun 18, 2015 at 8:55 AM, Andy Seaborne a...@apache.org wrote:
On 18/06/15 07:26, Claude Warren wrote:
I seem to be going around in circles with the fuseki documentation.
Does Fuseki support the POST command as noted at
http://www.w3.org/TR/2013/REC-sparql11-http-rdf-update-20130321/#http-post
To reword slightly to make the boundary clear: my emphasis:
[[
POST /rdf-graph-store?default HTTP/1.1
Host: example.com
Content-Type: text/turtle
** RDF payload **
is considered to have the same effect as:
INSERT DATA { ** RDF payload ** }
]]
There are two sections there.
(I believe it does from reading the docs)
It does.
I am attempting to execute an INSERT
which is not in the Graph Store Protocol.
http://www.w3.org/TR/sparql11-protocol/#update-operation
for sending SPARQL Updates.
I have started fuseki on my linux system using
fuseki-server -mem /tst
I am using the Apache httpcomponents library
I am posting to http://localhost:3030/tst/data?default
Graph Store Protocol != SPARQL Update over HTTP
The SPARQL Update endpoint is usually:
http://localhost:3030/tst/update
whereas you can POST RDF data to the default graph, with conneg:
http://localhost:3030/tst/data?default
I have set the content type to text/turtle
the text that is being posted is
INSERT DATA
{
urn:foo:s urn:foo:p urn:foo:o .
}
The fuseki log shows:
[2015-06-18 07:20:32] Fuseki INFO [1] POST
http://localhost:3030/tst/data?default
[2015-06-18 07:20:32] Fuseki INFO [1] POST /tst :: 'data' ::
[text/turtle charset=UTF-8] ? default
Conneg has decided on
text/turtle
INSERT DATA
is not Turtle.
[2015-06-18 07:20:32] Fuseki ERROR [line: 1, col: 1 ] Out of place:
[KEYWORD:INSERT]
[2015-06-18 07:20:32] Fuseki INFO [1] 400 Parse error: [line: 1, col:
1 ] Out of place: [KEYWORD:INSERT] (62 ms)
The BasicHttpResponse I am getting back is:
HTTP/1.1 400 Parse error: [line: 1, col: 1 ] Out of place:
[KEYWORD:INSERT]
[Fuseki-Request-ID: 2, Server: Fuseki (2.0.0-SNAPSHOT), Content-Type:
text/plain; charset=UTF-8, Cache-Control:
must-revalidate,no-cache,no-store, Pragma: no-cache, Content-Length: 147]
ResponseEntityProxy{[Content-Type: text/plain;
charset=UTF-8,Content-Length: 147,Chunked: false]}
I must be doing something silly. Does anyone see what the issue is?
Claude
Andy
--
I like: Like Like - The likeliest place on the web
http://like-like.xenei.com
LinkedIn: http://www.linkedin.com/in/claudewarren
