[GitHub] [jena] afs merged pull request #651: JENA-1796: Add missing DV for XSD DateTimeStamp data type

[GitBox]

afs merged pull request #651: JENA-1796: Add missing DV for XSD DateTimeStamp 
data type
URL: https://github.com/apache/jena/pull/651
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (JENA-1796) Add missing DV for XSD DateTimeStamp

[ASF subversion and git services (Jira)]

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

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

Commit 34ea70c7c3511ce34009a2ee848f5b58506445f9 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=34ea70c ]

Merge pull request #651 from georgschmidtdumont/JENA-1796

JENA-1796: Add missing DV for XSD DateTimeStamp data type

> Add missing DV for XSD DateTimeStamp
> 
>
> Key: JENA-1796
> URL: https://issues.apache.org/jira/browse/JENA-1796
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Core
>Reporter: Georg Schmidt-Dumont
>Assignee: Andy Seaborne
>Priority: Major
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> The {{ExtendedSchemaDVFactoryImpl}} is missing a definition for the XSD 
> DateTimeStamp data type.
> It should be included in order to support all XML Schema 1.1 data types.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [jena] afs merged pull request #654: Enum QueryType; use with RDFconnection

[GitBox]

afs merged pull request #654: Enum QueryType; use with RDFconnection
URL: https://github.com/apache/jena/pull/654
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (JENA-1799) Add QueryType enum.

[ASF subversion and git services (Jira)]

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

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

Commit 3f069f468714173a5e2fabda39151c5b7e19517f in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=3f069f4 ]

JENA-1799: QueryType enum.

> Add QueryType enum.
> ---
>
> Key: JENA-1799
> URL: https://issues.apache.org/jira/browse/JENA-1799
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.13.1
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.14.0
>
>
> Small step - replace use of the old-style constants with an enum (keep and 
> deprecate old constants).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (JENA-1800) RDFConnection - provide QueryType to improve conneg for pass-through strings.

[ASF subversion and git services (Jira)]

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

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

Commit 2b218a20b8893b54e3292e2654219be805fa7c8a in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=2b218a2 ]

JENA-1800: Use QueryType with exec*(queryString) operations.

Use QueryType to choose the "Accept" header.
If no known query type, use an all-purpose content negotiation string.


> RDFConnection - provide QueryType to improve conneg for pass-through strings.
> -
>
> Key: JENA-1800
> URL: https://issues.apache.org/jira/browse/JENA-1800
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.13.1
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.14.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (JENA-1801) Thrift encoded result set can have null for the variables list.

[ASF subversion and git services (Jira)]

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

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

Commit 8c1b90eba08dc45e7881bb1f6f185c2a4e8c817a in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=8c1b90e ]

JENA-1801: Put empty vars array into output


> Thrift encoded result set can have null for the variables list.
> ---
>
> Key: JENA-1801
> URL: https://issues.apache.org/jira/browse/JENA-1801
> Project: Apache Jena
>  Issue Type: Bug
>Affects Versions: Jena 3.13.1
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.14.0
>
>
> {{new RDF_VarTuple()}} creates an element with a null array internally and 
> then nothing is written for the array to the Thrift output. On decode, the 
> array is null as well. To be robust, the reader {{Thift2Binding}} should cope 
> with this and writer {{Binding2Thrift}} should send an empty array.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (JENA-1796) Add missing DV for XSD DateTimeStamp

[ASF subversion and git services (Jira)]

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

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

Commit 34ea70c7c3511ce34009a2ee848f5b58506445f9 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=34ea70c ]

Merge pull request #651 from georgschmidtdumont/JENA-1796

JENA-1796: Add missing DV for XSD DateTimeStamp data type

> Add missing DV for XSD DateTimeStamp
> 
>
> Key: JENA-1796
> URL: https://issues.apache.org/jira/browse/JENA-1796
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Core
>Reporter: Georg Schmidt-Dumont
>Assignee: Andy Seaborne
>Priority: Major
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> The {{ExtendedSchemaDVFactoryImpl}} is missing a definition for the XSD 
> DateTimeStamp data type.
> It should be included in order to support all XML Schema 1.1 data types.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (JENA-1796) Add missing DV for XSD DateTimeStamp

[Andy Seaborne (Jira)]

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

Andy Seaborne updated JENA-1796:

Fix Version/s: Jena 3.14.0

> Add missing DV for XSD DateTimeStamp
> 
>
> Key: JENA-1796
> URL: https://issues.apache.org/jira/browse/JENA-1796
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Core
>Reporter: Georg Schmidt-Dumont
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.14.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> The {{ExtendedSchemaDVFactoryImpl}} is missing a definition for the XSD 
> DateTimeStamp data type.
> It should be included in order to support all XML Schema 1.1 data types.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [jena] afs commented on issue #651: JENA-1796: Add missing DV for XSD DateTimeStamp data type

[GitBox]

afs commented on issue #651: JENA-1796: Add missing DV for XSD DateTimeStamp 
data type
URL: https://github.com/apache/jena/pull/651#issuecomment-567879958
 
 
   Merged, thanks!


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [jena] afs merged pull request #655: JENA-1802: Flag --count for riot

[GitBox]

afs merged pull request #655: JENA-1802: Flag --count for riot
URL: https://github.com/apache/jena/pull/655
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (JENA-1802) Add "--count" flag to riot : print the triple/quad, no RDF output.

[ASF subversion and git services (Jira)]

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

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

Commit 4cdcfcefb9c71d86b76a671eb5da0a8fa9bdf89f in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=4cdcfce ]

JENA-1802: Flag --count for riot


> Add "--count" flag to riot : print the triple/quad, no RDF output.
> --
>
> Key: JENA-1802
> URL: https://issues.apache.org/jira/browse/JENA-1802
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: RIOT
>Affects Versions: Jena 3.13.1
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.14.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Add a "–count" flag causes RIOT to output
> {noformat}
>  : Triples = 
> {noformat}
>  and not output the RDF triples themselves (same for quads).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (JENA-1802) Add "--count" flag to riot : print the triple/quad, no RDF output.

[ASF subversion and git services (Jira)]

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

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

Commit a7ed77b56c9f6baa0e86a663d4cc77027d9a61f3 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=a7ed77b ]

Merge pull request #655 from afs/riot-count

JENA-1802: Flag --count for riot

> Add "--count" flag to riot : print the triple/quad, no RDF output.
> --
>
> Key: JENA-1802
> URL: https://issues.apache.org/jira/browse/JENA-1802
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: RIOT
>Affects Versions: Jena 3.13.1
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.14.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Add a "–count" flag causes RIOT to output
> {noformat}
>  : Triples = 
> {noformat}
>  and not output the RDF triples themselves (same for quads).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (JENA-1799) Add QueryType enum.

[Andy Seaborne (Jira)]

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

Andy Seaborne resolved JENA-1799.
-
Resolution: Fixed

> Add QueryType enum.
> ---
>
> Key: JENA-1799
> URL: https://issues.apache.org/jira/browse/JENA-1799
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.13.1
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.14.0
>
>
> Small step - replace use of the old-style constants with an enum (keep and 
> deprecate old constants).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (JENA-1800) RDFConnection - provide QueryType to improve conneg for pass-through strings.

[Andy Seaborne (Jira)]

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

Andy Seaborne resolved JENA-1800.
-
Resolution: Fixed

> RDFConnection - provide QueryType to improve conneg for pass-through strings.
> -
>
> Key: JENA-1800
> URL: https://issues.apache.org/jira/browse/JENA-1800
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.13.1
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.14.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (JENA-1801) Thrift encoded result set can have null for the variables list.

[Andy Seaborne (Jira)]

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

Andy Seaborne resolved JENA-1801.
-
Resolution: Fixed

> Thrift encoded result set can have null for the variables list.
> ---
>
> Key: JENA-1801
> URL: https://issues.apache.org/jira/browse/JENA-1801
> Project: Apache Jena
>  Issue Type: Bug
>Affects Versions: Jena 3.13.1
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.14.0
>
>
> {{new RDF_VarTuple()}} creates an element with a null array internally and 
> then nothing is written for the array to the Thrift output. On decode, the 
> array is null as well. To be robust, the reader {{Thift2Binding}} should cope 
> with this and writer {{Binding2Thrift}} should send an empty array.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [jena] Claudenw merged pull request #656: 1803 fix

[GitBox]

Claudenw merged pull request #656: 1803 fix
URL: https://github.com/apache/jena/pull/656
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Created] (JENA-1804) Fuskei filter: pass on requests that are not matched.

[Andy Seaborne (Jira)]

Andy Seaborne created JENA-1804:
---

 Summary: Fuskei filter: pass on requests that are not matched.
 Key: JENA-1804
 URL: https://issues.apache.org/jira/browse/JENA-1804
 Project: Apache Jena
  Issue Type: Improvement
  Components: Fuseki
Affects Versions: Jena 3.13.1
Reporter: Andy Seaborne
Assignee: Andy Seaborne
 Fix For: Jena 3.14.0


Taken from [users@ 
thread|https://lists.apache.org/thread.html/bd790ba2b02718aba46e4e80ea73a15589179c9fcd4410f4912904aa%40%3Cusers.jena.apache.org%3E].

A request {{/dataset/name}} is routed first to "dataset" then "name" looked up 
in the services. If "name" is not found, a 404 is generated by the Fuseki 
dispatcher.

If, instead, the Fuseki dispatcher just klevas the request alone, the name can 
be provided by a plain servlet or static file in conventional request routing 
by the container.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (JENA-1804) Fuseki filter: pass on requests that are not matched.

[Andy Seaborne (Jira)]

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

Andy Seaborne updated JENA-1804:

Summary: Fuseki filter: pass on requests that are not matched.  (was: 
Fuskei filter: pass on requests that are not matched.)

> Fuseki filter: pass on requests that are not matched.
> -
>
> Key: JENA-1804
> URL: https://issues.apache.org/jira/browse/JENA-1804
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Fuseki
>Affects Versions: Jena 3.13.1
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.14.0
>
>
> Taken from [users@ 
> thread|https://lists.apache.org/thread.html/bd790ba2b02718aba46e4e80ea73a15589179c9fcd4410f4912904aa%40%3Cusers.jena.apache.org%3E].
> A request {{/dataset/name}} is routed first to "dataset" then "name" looked 
> up in the services. If "name" is not found, a 404 is generated by the Fuseki 
> dispatcher.
> If, instead, the Fuseki dispatcher just klevas the request alone, the name 
> can be provided by a plain servlet or static file in conventional request 
> routing by the container.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (JENA-1802) Add "--count" flag to riot : print the triple/quad, no RDF output.

[Andy Seaborne (Jira)]

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

Andy Seaborne resolved JENA-1802.
-
Resolution: Fixed

> Add "--count" flag to riot : print the triple/quad, no RDF output.
> --
>
> Key: JENA-1802
> URL: https://issues.apache.org/jira/browse/JENA-1802
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: RIOT
>Affects Versions: Jena 3.13.1
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.14.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Add a "–count" flag causes RIOT to output
> {noformat}
>  : Triples = 
> {noformat}
>  and not output the RDF triples themselves (same for quads).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (JENA-1798) TDB1 converts small xsd:long literals into xsd:integer

[Andy Seaborne (Jira)]

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

Andy Seaborne resolved JENA-1798.
-
Resolution: Information Provided

> TDB1 converts small xsd:long literals into xsd:integer
> --
>
> Key: JENA-1798
> URL: https://issues.apache.org/jira/browse/JENA-1798
> Project: Apache Jena
>  Issue Type: Bug
>  Components: TDB
>Reporter: Pavel Mikhailovskii
>Priority: Minor
>
> TDB1 converts small xsd:long literals, e.g. "1"^ to xsd:integer. 
> This behavior is specific to TDB1. Even though that might be acceptable in 
> most cases, it breaks validation of SHACL \{{ sh:dataType xsd:long ;}} 
> constraints. The following test demonstrates the issue:
> {code:java}
> @Test public void longLiterals() {
> DatasetGraph dsg = TDBFactory.createDatasetGraph();
> Quad quad1 = SSE.parseQuad("(quad
> \"1\"^^)");
> assertEquals(XSDDatatype.XSDlong, 
> quad1.getObject().getLiteralDatatype());
> dsg.add(quad1);
> Quad quad2 = dsg.find().next();
> assertEquals(XSDDatatype.XSDlong, 
> quad2.getObject().getLiteralDatatype());
> }
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (JENA-1796) Add missing DV for XSD DateTimeStamp

[Andy Seaborne (Jira)]

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

Andy Seaborne resolved JENA-1796.
-
Resolution: Fixed

> Add missing DV for XSD DateTimeStamp
> 
>
> Key: JENA-1796
> URL: https://issues.apache.org/jira/browse/JENA-1796
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Core
>Reporter: Georg Schmidt-Dumont
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.14.0
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> The {{ExtendedSchemaDVFactoryImpl}} is missing a definition for the XSD 
> DateTimeStamp data type.
> It should be included in order to support all XML Schema 1.1 data types.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (JENA-1804) Fuseki filter: pass on requests that are not matched.

[Andy Seaborne (Jira)]

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

Andy Seaborne updated JENA-1804:

Description: 
Taken from [users@ 
thread|https://lists.apache.org/thread.html/bd790ba2b02718aba46e4e80ea73a15589179c9fcd4410f4912904aa%40%3Cusers.jena.apache.org%3E].

A request {{/dataset/name}} is routed first to "dataset" then "name" looked up 
in the services. If "name" is not found, a 404 is generated by the Fuseki 
dispatcher.

If, instead, the Fuseki dispatcher just leaves the request alone, the name can 
be provided by a plain servlet or static file in conventional request routing 
by the container.

  was:
Taken from [users@ 
thread|https://lists.apache.org/thread.html/bd790ba2b02718aba46e4e80ea73a15589179c9fcd4410f4912904aa%40%3Cusers.jena.apache.org%3E].

A request {{/dataset/name}} is routed first to "dataset" then "name" looked up 
in the services. If "name" is not found, a 404 is generated by the Fuseki 
dispatcher.

If, instead, the Fuseki dispatcher just klevas the request alone, the name can 
be provided by a plain servlet or static file in conventional request routing 
by the container.


> Fuseki filter: pass on requests that are not matched.
> -
>
> Key: JENA-1804
> URL: https://issues.apache.org/jira/browse/JENA-1804
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Fuseki
>Affects Versions: Jena 3.13.1
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.14.0
>
>
> Taken from [users@ 
> thread|https://lists.apache.org/thread.html/bd790ba2b02718aba46e4e80ea73a15589179c9fcd4410f4912904aa%40%3Cusers.jena.apache.org%3E].
> A request {{/dataset/name}} is routed first to "dataset" then "name" looked 
> up in the services. If "name" is not found, a 404 is generated by the Fuseki 
> dispatcher.
> If, instead, the Fuseki dispatcher just leaves the request alone, the name 
> can be provided by a plain servlet or static file in conventional request 
> routing by the container.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (JENA-1803) Query builder has no method to merge a where clause

[Claude Warren (Jira)]

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

Claude Warren resolved JENA-1803.
-
Fix Version/s: Jena 3.14.0
   Resolution: Fixed

> Query builder has no method to merge a where clause
> ---
>
> Key: JENA-1803
> URL: https://issues.apache.org/jira/browse/JENA-1803
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: QueryBuilder
>Affects Versions: Jena 3.13.1
>Reporter: Claude Warren
>Assignee: Claude Warren
>Priority: Minor
> Fix For: Jena 3.14.0
>
>
> The AbstractQueryBuilder does not have a mechanism to add entire where clause 
> to the query.
> this would be a addWhere() method that takes a WhereBuilder as an argument, 
> takes the entire where clause of  the argument as an element and adds it to 
> the elements in the queryBuilder.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [jena] afs opened a new pull request #657: JENA-1804: Pass through non-matching service requests

[GitBox]

afs opened a new pull request #657: JENA-1804: Pass through non-matching 
service requests
URL: https://github.com/apache/jena/pull/657
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [jena] Claudenw opened a new pull request #658: Added addPrefix( PrefixMapping ) to builders.

[GitBox]

Claudenw opened a new pull request #658: Added addPrefix( PrefixMapping ) to 
builders.
URL: https://github.com/apache/jena/pull/658
 
 
   Added addPrefixes( PrefixMapping )
   
   cleaned up tests.
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (JENA-1755) Improve documentation of Query Builders

[ASF subversion and git services (Jira)]

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

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

Commit 1871856 from Claude Warren in branch 'site/trunk'
[ https://svn.apache.org/r1871856 ]

Updated documentation as part of JENA-1755

> Improve documentation of Query Builders
> ---
>
> Key: JENA-1755
> URL: https://issues.apache.org/jira/browse/JENA-1755
> Project: Apache Jena
>  Issue Type: Improvement
>Reporter: Jan Martin Keil
>Priority: Major
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> As discussed in JENA-1751, I propose to improve the documentation of the 
> query builders:
> {quote}Unfortunately, I did not find (and I think there isn't) any 
> documentation or tutorial about the query builders explaining more than the 
> very basics. Also the JavaDoc (which is to the best of my knowledge nowhere 
> linked on [https://jena.apache.org/]), is, in my experience, not helpful and 
> makes it often necessary to look into the code to understand what is needed 
> and maybe find out how to get it. If I did not miss a comprehensive 
> documentation somewhere, I think it would be worth, to improve documentation. 
> Even a few words at the builder classes (mentioning e.g. ExprFactory) and 
> small examples at the more complicated methods would help a lot.
> {quote}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (JENA-1805) Add example of StreamRDF to RDFConnection.

[Claude Warren (Jira)]

Claude Warren created JENA-1805:
---

 Summary: Add example of StreamRDF to RDFConnection.
 Key: JENA-1805
 URL: https://issues.apache.org/jira/browse/JENA-1805
 Project: Apache Jena
  Issue Type: Improvement
Reporter: Claude Warren
Assignee: Claude Warren


As discussed on the mailing list back in July this is an addition to the 
examples code to show how to implement an StreamRDF that will write to an 
RDFConnection.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [jena] Claudenw opened a new pull request #659: WIP: 1805 fix

[GitBox]

Claudenw opened a new pull request #659: WIP: 1805 fix
URL: https://github.com/apache/jena/pull/659
 
 
   Added example code for StreamRDF to RDFConnection.
   
   Added query builder methods to make construction easier.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Examples?

[Claude Warren]

I just finished an example of how to write a StreamRDF to an
RDFConnection.  I placed this in the jena-examples project and update the
pom so that it tracks the jena version.

I then noticed that the RDFConnections examples are in the jena-connections
main source tree.

I  think that all examples should go into the examples project so that
there is one place for users to go to get the example code.

I also think that the examples project should be built after the main Jena
build (so that it does not cause the build to fail if the examples fail).

Are there other thoughts about this?

Claude

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

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

Re: Examples?

[ajs6f]

I completely agree about getting the examples all into one place.

But I think I would rather fail the build when they fail to build, because I 
understand examples as a sort of very high-level test. If examples are not 
working we might want to disable some of them instead of investing a bunch of 
time fixing the specific problems, but wouldn't we want to know?

ajs6f

> On Dec 20, 2019, at 10:41 AM, Claude Warren  wrote:
> 
> I just finished an example of how to write a StreamRDF to an
> RDFConnection.  I placed this in the jena-examples project and update the
> pom so that it tracks the jena version.
> 
> I then noticed that the RDFConnections examples are in the jena-connections
> main source tree.
> 
> I  think that all examples should go into the examples project so that
> there is one place for users to go to get the example code.
> 
> I also think that the examples project should be built after the main Jena
> build (so that it does not cause the build to fail if the examples fail).
> 
> Are there other thoughts about this?
> 
> Claude
> 
> -- 
> I like: Like Like - The likeliest place on the web
> 
> LinkedIn: http://www.linkedin.com/in/claudewarren

[GitHub] [jena] afs commented on issue #659: WIP: 1805 fix

[GitBox]

afs commented on issue #659: WIP: 1805 fix
URL: https://github.com/apache/jena/pull/659#issuecomment-568093965
 
 
   It says "WIP" - is it ready?
   
   It would be helpful if the day-to-day commits were squashed to one each for 
the two different contributions.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [jena] afs commented on a change in pull request #659: WIP: 1805 fix

[GitBox]

afs commented on a change in pull request #659: WIP: 1805 fix
URL: https://github.com/apache/jena/pull/659#discussion_r360534650
 
 

 ##
 File path: jena-examples/pom.xml
 ##
 @@ -44,21 +41,27 @@
 
   org.apache.jena
   apache-jena-libs
-  ${ver.jena}
   pom
+  ${project.version}
 
 
   junit
   junit
-  4.10
-  jar
-  compile
 
 
   commons-cli
   commons-cli
-  1.2
+
+
+  org.apache.jena
+  jena-querybuilder
+  ${project.version}
 
   
 
+  
 
 Review comment:
   Please could we follow the style of other POMs with parent at the top.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services