[GitHub] jena issue #259: JENA-1357: Add support for a StreamManager when building an...

[kinow]

Github user kinow commented on the issue:

https://github.com/apache/jena/pull/259
  
Everything builds fine locally, all tests pass. Code looks good, and the 
few parts I am familiar in the change seem OK too. +1 lgtm


---
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-1357) Add support for setting a StreamManager in RDFParser.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036194#comment-16036194
 ] 

ASF GitHub Bot commented on JENA-1357:
--

Github user kinow commented on the issue:

https://github.com/apache/jena/pull/259
  
Everything builds fine locally, all tests pass. Code looks good, and the 
few parts I am familiar in the change seem OK too. +1 lgtm


> Add support for setting a StreamManager in RDFParser.
> -
>
> Key: JENA-1357
> URL: https://issues.apache.org/jira/browse/JENA-1357
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: RIOT
>Affects Versions: Jena 3.4.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.4.0
>
>
> It can only be done via the {{Context}} currently and it is not frozen when 
> the {{RDFParser}} is built.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] jena pull request #259: JENA-1357: Add support for a StreamManager when buil...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/jena/pull/259


---
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 #258: JENA-1355: Fix to VarFinder for OpPropFunc

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/jena/pull/258


---
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-1357) Add support for setting a StreamManager in RDFParser.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036206#comment-16036206
 ] 

ASF GitHub Bot commented on JENA-1357:
--

Github user asfgit closed the pull request at:

https://github.com/apache/jena/pull/259


> Add support for setting a StreamManager in RDFParser.
> -
>
> Key: JENA-1357
> URL: https://issues.apache.org/jira/browse/JENA-1357
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: RIOT
>Affects Versions: Jena 3.4.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.4.0
>
>
> It can only be done via the {{Context}} currently and it is not frozen when 
> the {{RDFParser}} is built.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (JENA-1357) Add support for setting a StreamManager in RDFParser.

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036208#comment-16036208
 ] 

ASF subversion and git services commented on JENA-1357:
---

Commit e79199a7ae2dd045ca038265ff5f1b9dbabdf2cd in jena's branch 
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=e79199a ]

JENA-1357: Merge commit 'refs/pull/259/head' of github.com:apache/jena

This closes #259.


> Add support for setting a StreamManager in RDFParser.
> -
>
> Key: JENA-1357
> URL: https://issues.apache.org/jira/browse/JENA-1357
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: RIOT
>Affects Versions: Jena 3.4.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.4.0
>
>
> It can only be done via the {{Context}} currently and it is not frozen when 
> the {{RDFParser}} is built.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (JENA-1355) Wrong determination of variables with property functions.

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036205#comment-16036205
 ] 

ASF subversion and git services commented on JENA-1355:
---

Commit ae82c1582039314e1290a46ba431feaf7fe666ea in jena's branch 
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=ae82c15 ]

JENA-1355: Merge commit 'refs/pull/258/head' of github.com:apache/jena

This closes #258.


> Wrong determination of variables with property functions.
> -
>
> Key: JENA-1355
> URL: https://issues.apache.org/jira/browse/JENA-1355
> Project: Apache Jena
>  Issue Type: Bug
>Affects Versions: Jena 3.3.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>
> Bug in {{VarFinder}}:
> {noformat}
> public static void main(String... args) {
> String z = String.join("\n"
>,"(propfunc "
>,"  ?x (?y 1)"
>,"  (table unit))"
>);
> vfind(z); 
> }
> public static void vfind(String z) {
> Op op = SSE.parseOp(z);
> System.out.println(op);
> VarFinder vf = VarFinder.process(op);
> System.out.println(vf);
> }
> {noformat}
> prints
> {noformat}
> (propfunc 
>   ?x (?y 1)
>   (table unit))
> Fixed:[?y], Filter:[], Filter2:[], Opt:[], Assign:[]
> {noformat}
> should be
> {noformat}
> Fixed:[?x, ?y], Filter:[], Filter2:[], Opt:[], Assign:[]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (JENA-1355) Wrong determination of variables with property functions.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036207#comment-16036207
 ] 

ASF GitHub Bot commented on JENA-1355:
--

Github user asfgit closed the pull request at:

https://github.com/apache/jena/pull/258


> Wrong determination of variables with property functions.
> -
>
> Key: JENA-1355
> URL: https://issues.apache.org/jira/browse/JENA-1355
> Project: Apache Jena
>  Issue Type: Bug
>Affects Versions: Jena 3.3.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>
> Bug in {{VarFinder}}:
> {noformat}
> public static void main(String... args) {
> String z = String.join("\n"
>,"(propfunc "
>,"  ?x (?y 1)"
>,"  (table unit))"
>);
> vfind(z); 
> }
> public static void vfind(String z) {
> Op op = SSE.parseOp(z);
> System.out.println(op);
> VarFinder vf = VarFinder.process(op);
> System.out.println(vf);
> }
> {noformat}
> prints
> {noformat}
> (propfunc 
>   ?x (?y 1)
>   (table unit))
> Fixed:[?y], Filter:[], Filter2:[], Opt:[], Assign:[]
> {noformat}
> should be
> {noformat}
> Fixed:[?x, ?y], Filter:[], Filter2:[], Opt:[], Assign:[]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (JENA-1355) Wrong determination of variables with property functions.

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036204#comment-16036204
 ] 

ASF subversion and git services commented on JENA-1355:
---

Commit 688006bf0318c206fc16eba2a8a97239e17060ce in jena's branch 
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=688006b ]

JENA-1355: Fix to VarFinder for OpPropFunc


> Wrong determination of variables with property functions.
> -
>
> Key: JENA-1355
> URL: https://issues.apache.org/jira/browse/JENA-1355
> Project: Apache Jena
>  Issue Type: Bug
>Affects Versions: Jena 3.3.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>
> Bug in {{VarFinder}}:
> {noformat}
> public static void main(String... args) {
> String z = String.join("\n"
>,"(propfunc "
>,"  ?x (?y 1)"
>,"  (table unit))"
>);
> vfind(z); 
> }
> public static void vfind(String z) {
> Op op = SSE.parseOp(z);
> System.out.println(op);
> VarFinder vf = VarFinder.process(op);
> System.out.println(vf);
> }
> {noformat}
> prints
> {noformat}
> (propfunc 
>   ?x (?y 1)
>   (table unit))
> Fixed:[?y], Filter:[], Filter2:[], Opt:[], Assign:[]
> {noformat}
> should be
> {noformat}
> Fixed:[?x, ?y], Filter:[], Filter2:[], Opt:[], Assign:[]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (JENA-1357) Add support for setting a StreamManager in RDFParser.

[Andy Seaborne (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JENA-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Seaborne resolved JENA-1357.
-
Resolution: Fixed

> Add support for setting a StreamManager in RDFParser.
> -
>
> Key: JENA-1357
> URL: https://issues.apache.org/jira/browse/JENA-1357
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: RIOT
>Affects Versions: Jena 3.4.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.4.0
>
>
> It can only be done via the {{Context}} currently and it is not frozen when 
> the {{RDFParser}} is built.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (JENA-1355) Wrong determination of variables with property functions.

[Andy Seaborne (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JENA-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Seaborne resolved JENA-1355.
-
   Resolution: Fixed
Fix Version/s: Jena 3.4.0

> Wrong determination of variables with property functions.
> -
>
> Key: JENA-1355
> URL: https://issues.apache.org/jira/browse/JENA-1355
> Project: Apache Jena
>  Issue Type: Bug
>Affects Versions: Jena 3.3.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
> Fix For: Jena 3.4.0
>
>
> Bug in {{VarFinder}}:
> {noformat}
> public static void main(String... args) {
> String z = String.join("\n"
>,"(propfunc "
>,"  ?x (?y 1)"
>,"  (table unit))"
>);
> vfind(z); 
> }
> public static void vfind(String z) {
> Op op = SSE.parseOp(z);
> System.out.println(op);
> VarFinder vf = VarFinder.process(op);
> System.out.println(vf);
> }
> {noformat}
> prints
> {noformat}
> (propfunc 
>   ?x (?y 1)
>   (table unit))
> Fixed:[?y], Filter:[], Filter2:[], Opt:[], Assign:[]
> {noformat}
> should be
> {noformat}
> Fixed:[?x, ?y], Filter:[], Filter2:[], Opt:[], Assign:[]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] jena pull request #260: JENA-1074: Provide a union graph for DatasetGraph

[afs]

GitHub user afs opened a pull request:

https://github.com/apache/jena/pull/260

JENA-1074: Provide a union graph for DatasetGraph

This PR adds:

`DatasetGraph.getUnionGraph`
`Dataset.getUnionModel`

It also adds a convenience `Graph.find()`.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/afs/jena jena1074_uniongraph

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/jena/pull/260.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #260


commit a6eaa15da666981443dbb803905439449850a7ba
Author: Andy Seaborne 
Date:   2017-06-03T21:37:08Z

Improve javadoc

commit 97e950e76023eb698fb369e621d246861be79e97
Author: Andy Seaborne 
Date:   2017-06-03T21:38:01Z

Block ExtendedIterator.remove

commit c25cbd8bd33cfb08c8a04d0b7f228b361be76f6c
Author: Andy Seaborne 
Date:   2017-06-04T08:41:11Z

JENA-1074: Add Graph.find(), equivalent to find(ANY,ANY,ANY).

commit 462fe53a8fbac8770471251be676a050d29a4d1a
Author: Andy Seaborne 
Date:   2017-06-04T08:43:25Z

JENA-1074: Use DatasetGraph.findNG for dynamic union graph .find.

commit 0a872489d859a78cf0e9e13b2a8ce532a5751d5d
Author: Andy Seaborne 
Date:   2017-06-04T08:44:34Z

JENA-1074: Add DatasetGraph.getUnionGraph

A graph which is the triples fromall named graph in the dataset.
This does not include the default graph.

commit a0169161322a6d65227e0c40cf464a0c879f1af2
Author: Andy Seaborne 
Date:   2017-06-04T08:55:15Z

JENA-1074: Tests for DatasetGraph.getUnionGraph()

commit 8a6ad81cb4692790b6afe2268c2d7310da035cda
Author: Andy Seaborne 
Date:   2017-06-04T08:57:34Z

JENA-1074: Provide Dataset.getUnionModel()




---
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-1074) Add find operations for DatasetGraph for the union graph.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036216#comment-16036216
 ] 

ASF GitHub Bot commented on JENA-1074:
--

GitHub user afs opened a pull request:

https://github.com/apache/jena/pull/260

JENA-1074: Provide a union graph for DatasetGraph

This PR adds:

`DatasetGraph.getUnionGraph`
`Dataset.getUnionModel`

It also adds a convenience `Graph.find()`.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/afs/jena jena1074_uniongraph

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/jena/pull/260.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #260


commit a6eaa15da666981443dbb803905439449850a7ba
Author: Andy Seaborne 
Date:   2017-06-03T21:37:08Z

Improve javadoc

commit 97e950e76023eb698fb369e621d246861be79e97
Author: Andy Seaborne 
Date:   2017-06-03T21:38:01Z

Block ExtendedIterator.remove

commit c25cbd8bd33cfb08c8a04d0b7f228b361be76f6c
Author: Andy Seaborne 
Date:   2017-06-04T08:41:11Z

JENA-1074: Add Graph.find(), equivalent to find(ANY,ANY,ANY).

commit 462fe53a8fbac8770471251be676a050d29a4d1a
Author: Andy Seaborne 
Date:   2017-06-04T08:43:25Z

JENA-1074: Use DatasetGraph.findNG for dynamic union graph .find.

commit 0a872489d859a78cf0e9e13b2a8ce532a5751d5d
Author: Andy Seaborne 
Date:   2017-06-04T08:44:34Z

JENA-1074: Add DatasetGraph.getUnionGraph

A graph which is the triples fromall named graph in the dataset.
This does not include the default graph.

commit a0169161322a6d65227e0c40cf464a0c879f1af2
Author: Andy Seaborne 
Date:   2017-06-04T08:55:15Z

JENA-1074: Tests for DatasetGraph.getUnionGraph()

commit 8a6ad81cb4692790b6afe2268c2d7310da035cda
Author: Andy Seaborne 
Date:   2017-06-04T08:57:34Z

JENA-1074: Provide Dataset.getUnionModel()




> Add find operations for DatasetGraph for the union graph.
> -
>
> Key: JENA-1074
> URL: https://issues.apache.org/jira/browse/JENA-1074
> Project: Apache Jena
>  Issue Type: Brainstorming
>  Components: ARQ
>Affects Versions: Jena 3.0.0
>Reporter: Andy Seaborne
>Priority: Minor
>
> (This follows on from JENA-1064)
> {{DatasetGraphBaseFind}} now has a {{find}} operations for the union graph 
> added to make implementation easier.
> Should operation(s) be exposed in the core interface {{DatasetGraph}} (the 
> application contract)? If so, how?
> The operations to consider include:
> * {{findInUnionGraph}} ({{Iterator}})
> * {{findQuadsInUnionGraph}} ({{Iterator}})
> * {{findInDftGraph}} ({{Iterator}} - inconsistent naming with above)
> At the moment {{findInDftGraph}} returns quads and documents 
> {{DatasetGraph.getDefaultGraph().find()}} as being the way to get triples. 
> This suggests a different style where {{DatasetGraph}} has:
> * {{DatasetGraph.getUnionGraph()}}
> * {{DatasetGraphFind.findInUnionGraph}} ({{Iterator}})



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] jena issue #260: JENA-1074: Provide a union graph for DatasetGraph

[afs]

Github user afs commented on the issue:

https://github.com/apache/jena/pull/260
  
The PR keeps "find" operations on `DatasetGraph` returning 
`Iterator`. A graph is used for`Iterator`.

The PR adds one new operation: `DatasetGraph.getUnionGraph()`.

The implementation in `DatasetGraphBase` uses `GraphUnionRead` which uses 
`DatasetGraph.findNG(Quad.unionGraph, ?, ?, ?)`.

`Graph.find()` (no arguments) is added for convenience and to match 
`DatasetGraph.find()`.



---
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-1074) Add find operations for DatasetGraph for the union graph.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036221#comment-16036221
 ] 

ASF GitHub Bot commented on JENA-1074:
--

Github user afs commented on the issue:

https://github.com/apache/jena/pull/260
  
The PR keeps "find" operations on `DatasetGraph` returning 
`Iterator`. A graph is used for`Iterator`.

The PR adds one new operation: `DatasetGraph.getUnionGraph()`.

The implementation in `DatasetGraphBase` uses `GraphUnionRead` which uses 
`DatasetGraph.findNG(Quad.unionGraph, ?, ?, ?)`.

`Graph.find()` (no arguments) is added for convenience and to match 
`DatasetGraph.find()`.



> Add find operations for DatasetGraph for the union graph.
> -
>
> Key: JENA-1074
> URL: https://issues.apache.org/jira/browse/JENA-1074
> Project: Apache Jena
>  Issue Type: Brainstorming
>  Components: ARQ
>Affects Versions: Jena 3.0.0
>Reporter: Andy Seaborne
>Priority: Minor
>
> (This follows on from JENA-1064)
> {{DatasetGraphBaseFind}} now has a {{find}} operations for the union graph 
> added to make implementation easier.
> Should operation(s) be exposed in the core interface {{DatasetGraph}} (the 
> application contract)? If so, how?
> The operations to consider include:
> * {{findInUnionGraph}} ({{Iterator}})
> * {{findQuadsInUnionGraph}} ({{Iterator}})
> * {{findInDftGraph}} ({{Iterator}} - inconsistent naming with above)
> At the moment {{findInDftGraph}} returns quads and documents 
> {{DatasetGraph.getDefaultGraph().find()}} as being the way to get triples. 
> This suggests a different style where {{DatasetGraph}} has:
> * {{DatasetGraph.getUnionGraph()}}
> * {{DatasetGraphFind.findInUnionGraph}} ({{Iterator}})



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (JENA-1358) UpdateRequest does not properly execute w3c update Example 10

[Claude Warren (JIRA)]

Claude Warren created JENA-1358:
---

 Summary: UpdateRequest does not properly execute w3c update 
Example 10
 Key: JENA-1358
 URL: https://issues.apache.org/jira/browse/JENA-1358
 Project: Apache Jena
  Issue Type: Bug
  Components: ARQ
Affects Versions: Jena 3.3.0
Reporter: Claude Warren


the W3C SPARQL 1.1. update documentation contains an example numbered 10.

https://www.w3.org/TR/sparql11-update/#example_10

When executed in Jena the delete portion of that example is not executed.

Example code to be attached



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (JENA-1358) UpdateRequest does not properly execute w3c update Example 10

[Claude Warren (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JENA-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claude Warren updated JENA-1358:

Attachment: Example10.java

Test code that executes the example 10 from the w3c SPARQL 1.1. documentation. 

> UpdateRequest does not properly execute w3c update Example 10
> -
>
> Key: JENA-1358
> URL: https://issues.apache.org/jira/browse/JENA-1358
> Project: Apache Jena
>  Issue Type: Bug
>  Components: ARQ
>Affects Versions: Jena 3.3.0
>Reporter: Claude Warren
> Attachments: Example10.java
>
>
> the W3C SPARQL 1.1. update documentation contains an example numbered 10.
> https://www.w3.org/TR/sparql11-update/#example_10
> When executed in Jena the delete portion of that example is not executed.
> Example code to be attached



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (JENA-1358) UpdateRequest does not properly execute w3c update Example 10

[Claude Warren (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JENA-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claude Warren closed JENA-1358.
---
Resolution: Not A Problem

Issue was with data  in initial table.


> UpdateRequest does not properly execute w3c update Example 10
> -
>
> Key: JENA-1358
> URL: https://issues.apache.org/jira/browse/JENA-1358
> Project: Apache Jena
>  Issue Type: Bug
>  Components: ARQ
>Affects Versions: Jena 3.3.0
>Reporter: Claude Warren
> Attachments: Example10.java
>
>
> the W3C SPARQL 1.1. update documentation contains an example numbered 10.
> https://www.w3.org/TR/sparql11-update/#example_10
> When executed in Jena the delete portion of that example is not executed.
> Example code to be attached



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (JENA-1352) QueryBuilder should provide UpdateBuilder

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036252#comment-16036252
 ] 

ASF subversion and git services commented on JENA-1352:
---

Commit 7043d34435ca120f738c55035aa6994230f7 in jena's branch 
refs/heads/master from [~cla...@xenei.org]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=7043d34 ]

Merge branch 'requestBuilder'.  Fixes JENA-1352

> QueryBuilder should provide UpdateBuilder
> -
>
> Key: JENA-1352
> URL: https://issues.apache.org/jira/browse/JENA-1352
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: QueryBuilder
>Affects Versions: Jena 3.3.0
>Reporter: Claude Warren
>Assignee: Claude Warren
>Priority: Minor
>
> The QueryBuilder module should include an UpdateRequestBuilder that would 
> apply the same sort of functionality to creating UpdateRequests.
> The QueryBuilder framework will not work but should be extended to add 
> support for UpdateRequest while providing the same Object based API style.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (JENA-1352) QueryBuilder should provide UpdateBuilder

[Claude Warren (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JENA-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claude Warren resolved JENA-1352.
-
   Resolution: Implemented
Fix Version/s: Jena 3.4.0

> QueryBuilder should provide UpdateBuilder
> -
>
> Key: JENA-1352
> URL: https://issues.apache.org/jira/browse/JENA-1352
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: QueryBuilder
>Affects Versions: Jena 3.3.0
>Reporter: Claude Warren
>Assignee: Claude Warren
>Priority: Minor
> Fix For: Jena 3.4.0
>
>
> The QueryBuilder module should include an UpdateRequestBuilder that would 
> apply the same sort of functionality to creating UpdateRequests.
> The QueryBuilder framework will not work but should be extended to add 
> support for UpdateRequest while providing the same Object based API style.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Java 9

[Claude Warren]

I was trying to get a PR for the java9 changes  but am having significant
problems running java at all.

There were very few changes made for Java9 (only 1 test I thing) and
several plugins that did not work.  I think it would be faster to set up a
bigger development box to perform the java 9 builds and fixes.

Because of the problems, I am going to drop  the branch and may start over
again in the future.

Claude

On Wed, May 10, 2017 at 9:48 PM, Andy Seaborne  wrote:

> Claude - could this be turned into a PR so we view the changes?
>
> And in other news, the modules vote was lost: 10 for, 13 against.
>
> https://www.jcp.org/en/jsr/results?id=5959&cm_mc_uid=2651742
> 7955014876736746&cm_mc_sid_5020=1494449092
>
> What that means for Java9 timescale is anyone's guess.
>
> Andy
>
> On 15/02/17 19:07, Claude Warren wrote:
>
>> I have created a repository with the java9 branch in it.  I have not
>> merged
>> in the last big batch of changes.  but take a look.  I got it to compile
>> and run the tests however, the site packaging did not work.  I will be
>> looking at that shortly.  I also removed (commented out)
>> cobertura-maven-plugin
>> and
>> findbugs-maven-plugin
>>
>> from the parent.pom.
>>
>> My strategy has been to comment out anything that is not core to the
>> compile/test/package sequence with a goal to revisit those when the basic
>> build functionality works.
>>
>> Repository is at  https://github.com/Claudenw/jena
>>
>> Claude
>>
>> On Wed, Feb 8, 2017 at 10:17 AM, Andy Seaborne  wrote:
>>
>>
>>>
>>> On 08/02/17 09:21, Claude Warren wrote:
>>>
>>> While at FOSDEM I spoke with one of the developers on Lucene.  He
 indicted
 that there is a new version of the Maven Compiler plugin that works with
 Java 9.  He also had some insight into Memory Mapped files and indicated
 that there was a big change coming in Java 10 around this.  I'm not
 certain
 I understood exactly what the change was but I thought Andy and the
 other
 TDB folks might want to keep and eye out for any announcements in this
 area.

 I will be looking at the Java 9 compiler stuff this weekend.

 Claude


 Thanks for the new news - I hadn't spotted anything about mmap files in
>>> Java 10 ... mainly because of not looking yet.
>>>
>>> Hopefully value types from Project Valhalla will make it.
>>>
>>> https://en.wikipedia.org/wiki/Project_Valhalla_(Java_language)
>>>
>>> Andy
>>>
>>>
>>
>>
>>


-- 
I like: Like Like - The likeliest place on the web

LinkedIn: http://www.linkedin.com/in/claudewarren

Re: Build failed in Jenkins: Jena_Development_Test #2674

[Claude Warren]

Looks like the last number of Dev builds have faild for this reason.

On Fri, Jun 2, 2017 at 11:48 AM, Andy Seaborne  wrote:

> Jena built with maven 3.5.0 locally.
>
> Andy
>
>
> On 02/06/17 11:15, Andy Seaborne wrote:
>
>> Jenkins is having a bad time - I tried kicking the job off (morning, UK
>> time) and it crashed on ubuntu-us1 with
>>
>> java.lang.NoSuchFieldError: DEFAULT_USER_SETTINGS_FILE
>>
>> inside maven. Different error.
>>
>> I see email on bui...@apache.org about that.  Apparently a Jenkins bug
>> when using "latest" maven which is now 3.5.0
>>
>> Maybe that is related to what happened on ubuntu-4 . If thart keeps
>> happening, then it's INFRA time:
>>
>> http://www.apache.org/dev/infra-contact
>>
>> (Hipchat or a ticket.)
>>
>> As a temporary measure, I've kicked off a "mvn deploy" on my machine to
>> get snapshot build done today.
>>
>>  Andy
>>
>>
>> On 01/06/17 13:00, aj...@apache.org wrote:
>>
>>> Urg, we're getting:
>>>
>>> ERROR: Maven Home /home/jenkins/tools/maven/latest3 doesnt exist
>>>
>>> out of that. That doesn't look right. Is that an INFRA ticket or just
>>> wait a bit and see if it comes back?
>>>
>>>
>>> ajs6f
>>>
>>> Apache Jenkins Server wrote on 6/1/17 7:34 AM:
>>>
 See 

 Changes:

 [ajs6f] Upgrade some dependencies to next minor versions

 [ajs6f] Bumping HTTP Core version

 --
 Started by an SCM change
 [EnvInject] - Loading node environment variables.
 Building remotely on ubuntu-4 (ubuntu trusty) in workspace <
 https://builds.apache.org/job/Jena_Development_Test/ws/>
  > git rev-parse --is-inside-work-tree # timeout=10
 Fetching changes from the remote Git repository
  > git config remote.origin.url git://git.apache.org/jena.git #
 timeout=10
 Fetching upstream changes from git://git.apache.org/jena.git
  > git --version # timeout=10
  > git fetch --tags --progress git://git.apache.org/jena.git
 +refs/heads/*:refs/remotes/origin/*
  > git rev-parse origin/master^{commit} # timeout=10
 Checking out Revision 3b3ba37487f6e90dc5aefa48d2b64c22e9c7dca1
 (origin/master)
  > git config core.sparsecheckout # timeout=10
  > git checkout -f 3b3ba37487f6e90dc5aefa48d2b64c22e9c7dca1
  > git rev-list 41ebfe01679a4bee830f53fe54bd9352e4f5a278 # timeout=10
 ERROR: Maven Home /home/jenkins/tools/maven/latest3 doesnt exist




-- 
I like: Like Like - The likeliest place on the web

LinkedIn: http://www.linkedin.com/in/claudewarren

Re: Build failed in Jenkins: Jena_Development_Test #2674

[ajs6f]

I'll take it up with INFRA tomorrow unless someone beats me to it.


ajs6f

Claude Warren wrote on 6/4/17 8:54 AM:

Looks like the last number of Dev builds have faild for this reason.

On Fri, Jun 2, 2017 at 11:48 AM, Andy Seaborne  wrote:


Jena built with maven 3.5.0 locally.

Andy


On 02/06/17 11:15, Andy Seaborne wrote:


Jenkins is having a bad time - I tried kicking the job off (morning, UK
time) and it crashed on ubuntu-us1 with

java.lang.NoSuchFieldError: DEFAULT_USER_SETTINGS_FILE

inside maven. Different error.

I see email on bui...@apache.org about that.  Apparently a Jenkins bug
when using "latest" maven which is now 3.5.0

Maybe that is related to what happened on ubuntu-4 . If thart keeps
happening, then it's INFRA time:

http://www.apache.org/dev/infra-contact

(Hipchat or a ticket.)

As a temporary measure, I've kicked off a "mvn deploy" on my machine to
get snapshot build done today.

 Andy


On 01/06/17 13:00, aj...@apache.org wrote:


Urg, we're getting:

ERROR: Maven Home /home/jenkins/tools/maven/latest3 doesnt exist

out of that. That doesn't look right. Is that an INFRA ticket or just
wait a bit and see if it comes back?


ajs6f

Apache Jenkins Server wrote on 6/1/17 7:34 AM:


See 

Changes:

[ajs6f] Upgrade some dependencies to next minor versions

[ajs6f] Bumping HTTP Core version

--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on ubuntu-4 (ubuntu trusty) in workspace <
https://builds.apache.org/job/Jena_Development_Test/ws/>
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url git://git.apache.org/jena.git #
timeout=10
Fetching upstream changes from git://git.apache.org/jena.git
 > git --version # timeout=10
 > git fetch --tags --progress git://git.apache.org/jena.git
+refs/heads/*:refs/remotes/origin/*
 > git rev-parse origin/master^{commit} # timeout=10
Checking out Revision 3b3ba37487f6e90dc5aefa48d2b64c22e9c7dca1
(origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 3b3ba37487f6e90dc5aefa48d2b64c22e9c7dca1
 > git rev-list 41ebfe01679a4bee830f53fe54bd9352e4f5a278 # timeout=10
ERROR: Maven Home /home/jenkins/tools/maven/latest3 doesnt exist

[jira] [Updated] (JENA-1338) JSON-LD framing not accessible from command line riotcmd.riot.

[Andy Seaborne (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JENA-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Seaborne updated JENA-1338:

Summary: JSON-LD framing not accessible from command line riotcmd.riot.  
(was: [RIOT] JSON-LD framing not working)

> JSON-LD framing not accessible from command line riotcmd.riot.
> --
>
> Key: JENA-1338
> URL: https://issues.apache.org/jira/browse/JENA-1338
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Fuseki, RIOT
>Affects Versions: Jena 3.3.0
> Environment: GNU/Linux
>Reporter: Laura
>Priority: Minor
>
> According to the 
> [documentation|https://jena.apache.org/documentation/io/rdf-output.html#json-ld]
>  "JSON-LD output is supported, in its various flavors ("compacted", 
> "expanded", "flattened", "framed")" but there is no way to tell Jena which 
> one of these to use. In particular it's not possible to obtain "framed 
> JSON-LD" as an output format when querying Fuseki (CONSTRUCT queries).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Build failed in Jenkins: Jena_Development_Test #2674

[Andy Seaborne]

See the thread 
http://mail-archives.apache.org/mod_mbox/www-builds/201706.mbox/%3Cpony-84a3f5a42c31170b6f0cfe9682940d3779cc1a0d-410a725ec4f05db8367902a98b017f9d9e0d72f6%40builds.apache.org%3E


and I fixed it for the development build by setting it to maven 3.3.3, 
not "maven 3 latest".


Andy

On 04/06/17 14:43, aj...@apache.org wrote:

I'll take it up with INFRA tomorrow unless someone beats me to it.


ajs6f

Claude Warren wrote on 6/4/17 8:54 AM:

Looks like the last number of Dev builds have faild for this reason.

On Fri, Jun 2, 2017 at 11:48 AM, Andy Seaborne  wrote:


Jena built with maven 3.5.0 locally.

Andy


On 02/06/17 11:15, Andy Seaborne wrote:


Jenkins is having a bad time - I tried kicking the job off (morning, UK
time) and it crashed on ubuntu-us1 with

java.lang.NoSuchFieldError: DEFAULT_USER_SETTINGS_FILE

inside maven. Different error.

I see email on bui...@apache.org about that.  Apparently a Jenkins bug
when using "latest" maven which is now 3.5.0

Maybe that is related to what happened on ubuntu-4 . If thart keeps
happening, then it's INFRA time:

http://www.apache.org/dev/infra-contact

(Hipchat or a ticket.)

As a temporary measure, I've kicked off a "mvn deploy" on my machine to
get snapshot build done today.

 Andy


On 01/06/17 13:00, aj...@apache.org wrote:


Urg, we're getting:

ERROR: Maven Home /home/jenkins/tools/maven/latest3 doesnt exist

out of that. That doesn't look right. Is that an INFRA ticket or just
wait a bit and see if it comes back?


ajs6f

Apache Jenkins Server wrote on 6/1/17 7:34 AM:


See 

Changes:

[ajs6f] Upgrade some dependencies to next minor versions

[ajs6f] Bumping HTTP Core version

--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on ubuntu-4 (ubuntu trusty) in workspace <
https://builds.apache.org/job/Jena_Development_Test/ws/>
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url git://git.apache.org/jena.git #
timeout=10
Fetching upstream changes from git://git.apache.org/jena.git
 > git --version # timeout=10
 > git fetch --tags --progress git://git.apache.org/jena.git
+refs/heads/*:refs/remotes/origin/*
 > git rev-parse origin/master^{commit} # timeout=10
Checking out Revision 3b3ba37487f6e90dc5aefa48d2b64c22e9c7dca1
(origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 3b3ba37487f6e90dc5aefa48d2b64c22e9c7dca1
 > git rev-list 41ebfe01679a4bee830f53fe54bd9352e4f5a278 # timeout=10
ERROR: Maven Home /home/jenkins/tools/maven/latest3 doesnt exist