[jira] [Commented] (JENA-244) Deadlock during SPARQL execution on an inference model

2012-09-11 Thread Stephen Owens (JIRA) 

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

Stephen Owens commented on JENA-244:


Just retested this with 2.9.3, the deadlock is still reproducible with the test 
case. 

> Deadlock during SPARQL execution on an inference model
> --
>
> Key: JENA-244
> URL: https://issues.apache.org/jira/browse/JENA-244
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Jena
>Reporter: Stephen Owens
> Attachments: JenaDeadLockTest.java, JenaDeadLockTest.java
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (JENA-93) Permit cancelAllowDrain on a per query basis

2012-09-11 Thread Andy Seaborne (JIRA) 

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

Andy Seaborne closed JENA-93.
-


> Permit cancelAllowDrain on a per query basis
> 
>
> Key: JENA-93
> URL: https://issues.apache.org/jira/browse/JENA-93
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: ARQ
>Reporter: Simon Helsen
>Assignee: Andy Seaborne
>
> Currently, there is a global static variable 
> queryExecutionBase.cancelAllowDrain to permit partial results on cancelled 
> queries. 
> We would need this ability to be determinable on a per-query basis since we 
> have to mix both use-cases on our back-end and a the same time. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (JENA-320) Unexpected result from SPARQL Tutorial - Filters

2012-09-11 Thread Andy Seaborne (JIRA) 

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

Andy Seaborne resolved JENA-320.


   Resolution: Fixed
Fix Version/s: Jena 2.7.4
 Assignee: Andy Seaborne

Thanks.

The data file was wrong (I can't see how it happened though) -- now fixed and 
republished.

> Unexpected result from SPARQL Tutorial - Filters
> 
>
> Key: JENA-320
> URL: https://issues.apache.org/jira/browse/JENA-320
> Project: Apache Jena
>  Issue Type: Bug
>  Components: TDB, Web site
>Affects Versions: ARQ 2.9.3, TDB 0.9.3, Jena 2.7.3
> Environment: $ java -version
> java version "1.6.0_16"
> Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
> Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode)
> $ lsb_release -a
> LSB Version:
> :core-3.1-amd64:core-3.1-ia32:core-3.1-noarch:graphics-3.1-amd64:graphics-3.1-ia32:graphics-3.1-noarch
> Distributor ID: CentOS
> Description:CentOS release 5.5 (Final)
> Release:5.5
> Codename:   Final
>Reporter: Don Pellegrino
>Assignee: Andy Seaborne
> Fix For: Jena 2.7.4
>
>
> The "Testing Values" section of the Apache Jena "SPARQL Tutorial - Filters" 
> page(http://jena.apache.org/tutorials/sparql_filters.html) does not produce 
> the expected results. I made sure to pull the example files from the site to 
> ensure the issue was not due to typos in transcription:
> $ wget "http://jena.apache.org/tutorials/sparql_data/vc-db-2.rdf";
> --2012-09-04 10:47:20-- 
> http://jena.apache.org/tutorials/sparql_data/vc-db-2.rdf
> Resolving jena.apache.org... 140.211.11.131, 
> 192.87.106.229,2001:610:1:80bc:192:87:106:229
> Connecting to jena.apache.org|140.211.11.131|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 1149 (1.1K) [application/rdf+xml]
> Saving to: `vc-db-2.rdf'
> 100%[=>] 
> 1,149--.-K/s in 0s
> 2012-09-04 10:47:20 (99.6 MB/s) - `vc-db-2.rdf' saved [1149/1149]
> $ wget "http://jena.apache.org/tutorials/sparql_data/q-f2.rq";
> --2012-09-04 10:48:03-- http://jena.apache.org/tutorials/sparql_data/q-f2.rq
> Resolving jena.apache.org... 140.211.11.131, 
> 192.87.106.229,2001:610:1:80bc:192:87:106:229
> Connecting to jena.apache.org|140.211.11.131|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 148 [application/sparql-query]
> Saving to: `q-f2.rq'
> 100%[=>] 
> 148--.-K/s in 0s
> 2012-09-04 10:48:03 (990 KB/s) - `q-f2.rq' saved [148/148]
> I then used the following query command:
> $ sparql --data=vc-db-2.rdf --query=q-f2.rq
> 
> | resource |
> 
> 
> The Tutorial page indicates that the result should have been:
> -
> | resource |
> =
> |  |
> -

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (JENA-320) Unexpected result from SPARQL Tutorial - Filters

2012-09-11 Thread Andy Seaborne (JIRA) 

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

Andy Seaborne closed JENA-320.
--


> Unexpected result from SPARQL Tutorial - Filters
> 
>
> Key: JENA-320
> URL: https://issues.apache.org/jira/browse/JENA-320
> Project: Apache Jena
>  Issue Type: Bug
>  Components: TDB, Web site
>Affects Versions: ARQ 2.9.3, TDB 0.9.3, Jena 2.7.3
> Environment: $ java -version
> java version "1.6.0_16"
> Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
> Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode)
> $ lsb_release -a
> LSB Version:
> :core-3.1-amd64:core-3.1-ia32:core-3.1-noarch:graphics-3.1-amd64:graphics-3.1-ia32:graphics-3.1-noarch
> Distributor ID: CentOS
> Description:CentOS release 5.5 (Final)
> Release:5.5
> Codename:   Final
>Reporter: Don Pellegrino
>Assignee: Andy Seaborne
> Fix For: Jena 2.7.4
>
>
> The "Testing Values" section of the Apache Jena "SPARQL Tutorial - Filters" 
> page(http://jena.apache.org/tutorials/sparql_filters.html) does not produce 
> the expected results. I made sure to pull the example files from the site to 
> ensure the issue was not due to typos in transcription:
> $ wget "http://jena.apache.org/tutorials/sparql_data/vc-db-2.rdf";
> --2012-09-04 10:47:20-- 
> http://jena.apache.org/tutorials/sparql_data/vc-db-2.rdf
> Resolving jena.apache.org... 140.211.11.131, 
> 192.87.106.229,2001:610:1:80bc:192:87:106:229
> Connecting to jena.apache.org|140.211.11.131|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 1149 (1.1K) [application/rdf+xml]
> Saving to: `vc-db-2.rdf'
> 100%[=>] 
> 1,149--.-K/s in 0s
> 2012-09-04 10:47:20 (99.6 MB/s) - `vc-db-2.rdf' saved [1149/1149]
> $ wget "http://jena.apache.org/tutorials/sparql_data/q-f2.rq";
> --2012-09-04 10:48:03-- http://jena.apache.org/tutorials/sparql_data/q-f2.rq
> Resolving jena.apache.org... 140.211.11.131, 
> 192.87.106.229,2001:610:1:80bc:192:87:106:229
> Connecting to jena.apache.org|140.211.11.131|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 148 [application/sparql-query]
> Saving to: `q-f2.rq'
> 100%[=>] 
> 148--.-K/s in 0s
> 2012-09-04 10:48:03 (990 KB/s) - `q-f2.rq' saved [148/148]
> I then used the following query command:
> $ sparql --data=vc-db-2.rdf --query=q-f2.rq
> 
> | resource |
> 
> 
> The Tutorial page indicates that the result should have been:
> -
> | resource |
> =
> |  |
> -

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (JENA-93) Permit cancelAllowDrain on a per query basis

2012-09-11 Thread Andy Seaborne (JIRA) 

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

Andy Seaborne resolved JENA-93.
---

Resolution: Won't Fix
  Assignee: Andy Seaborne

> Permit cancelAllowDrain on a per query basis
> 
>
> Key: JENA-93
> URL: https://issues.apache.org/jira/browse/JENA-93
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: ARQ
>Reporter: Simon Helsen
>Assignee: Andy Seaborne
>
> Currently, there is a global static variable 
> queryExecutionBase.cancelAllowDrain to permit partial results on cancelled 
> queries. 
> We would need this ability to be determinable on a per-query basis since we 
> have to mix both use-cases on our back-end and a the same time. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (JENA-320) Unexpected result from SPARQL Tutorial - Filters

2012-09-11 Thread Don Pellegrino (JIRA) 
Don Pellegrino created JENA-320:
---

 Summary: Unexpected result from SPARQL Tutorial - Filters
 Key: JENA-320
 URL: https://issues.apache.org/jira/browse/JENA-320
 Project: Apache Jena
  Issue Type: Bug
  Components: TDB, Web site
Affects Versions: Jena 2.7.3, TDB 0.9.3, ARQ 2.9.3
 Environment: $ java -version
java version "1.6.0_16"
Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode)

$ lsb_release -a
LSB Version:
:core-3.1-amd64:core-3.1-ia32:core-3.1-noarch:graphics-3.1-amd64:graphics-3.1-ia32:graphics-3.1-noarch
Distributor ID: CentOS
Description:CentOS release 5.5 (Final)
Release:5.5
Codename:   Final
Reporter: Don Pellegrino


The "Testing Values" section of the Apache Jena "SPARQL Tutorial - Filters" 
page(http://jena.apache.org/tutorials/sparql_filters.html) does not produce the 
expected results. I made sure to pull the example files from the site to ensure 
the issue was not due to typos in transcription:

$ wget "http://jena.apache.org/tutorials/sparql_data/vc-db-2.rdf";
--2012-09-04 10:47:20-- http://jena.apache.org/tutorials/sparql_data/vc-db-2.rdf
Resolving jena.apache.org... 140.211.11.131, 
192.87.106.229,2001:610:1:80bc:192:87:106:229
Connecting to jena.apache.org|140.211.11.131|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1149 (1.1K) [application/rdf+xml]
Saving to: `vc-db-2.rdf'
100%[=>] 
1,149--.-K/s in 0s
2012-09-04 10:47:20 (99.6 MB/s) - `vc-db-2.rdf' saved [1149/1149]

$ wget "http://jena.apache.org/tutorials/sparql_data/q-f2.rq";
--2012-09-04 10:48:03-- http://jena.apache.org/tutorials/sparql_data/q-f2.rq
Resolving jena.apache.org... 140.211.11.131, 
192.87.106.229,2001:610:1:80bc:192:87:106:229
Connecting to jena.apache.org|140.211.11.131|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 148 [application/sparql-query]
Saving to: `q-f2.rq'
100%[=>] 
148--.-K/s in 0s
2012-09-04 10:48:03 (990 KB/s) - `q-f2.rq' saved [148/148]

I then used the following query command:

$ sparql --data=vc-db-2.rdf --query=q-f2.rq

| resource |



The Tutorial page indicates that the result should have been:

-
| resource |
=
|  |
-

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (JENA-201) Deliver Fuseki as a WAR file.

2012-09-11 Thread Andy Seaborne (JIRA) 

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

Andy Seaborne commented on JENA-201:


This looks excellent.

One thing I want to check - do you use this with TDB?  If so, do you put the 
absolute file path to the database in fuseki-config.ttl (or at least point to 
outside webapps/) or put the database inside the WAR file?



> Deliver Fuseki as a WAR file.
> -
>
> Key: JENA-201
> URL: https://issues.apache.org/jira/browse/JENA-201
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Fuseki
>Reporter: Andy Seaborne
>Priority: Minor
> Attachments: GruppoImola_fuseki_war_src.rar
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [jira] [Commented] (JENA-189) Jena 3 / technical

2012-09-11 Thread Andy Seaborne 

Claude Warren commented on JENA-189:


I was writing from memory and seem to have gotten the layer wrong.
Yes, ModelChangedListener does what I was saying.  Is there something
similar for the Dataset?



Not yet - the choice I see is whether to add this into the core of the 
datasetgraph code or to add it as a wrapper dataset that sends events.


At the moment, I'm more inclined to put it as a wrapper e.g.

public void add(Quad quad)
{
send "add" event(getWrapped(), quad) ;
getWrapped().add(quad) ;
}

The other choice is the style of event system: publish-subscribe or 
object-notification. The current graph one is object-notification -- the 
object where the event happens sends out the notification.


In publish-subscribe, you can have event about an object without the 
object being involved.  An event manager sends out events, not the 
object the event is about.  Code registered with the event manager to 
listen, not with the object itself.


I've had to use this elsewhere (org.openjena.atlas.event.EventManager) 
but it is a complicated design. Maybe the object-notification is needed 
for convenience but it uses the publish-subscribe style for implementation.


What are the use cases beyond listening to quad add and quad delete?

Andy

[jira] [Commented] (JENA-189) Jena 3 / technical

2012-09-11 Thread Andy Seaborne (JIRA) 

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

Andy Seaborne commented on JENA-189:


Claude - yes, a separate JIRA would be easier from my point-of-view.

I'd like to hear about your ideas for RESTful operation - maybe a discussion on 
a JIRA or on email.

Fuseki does have a additional code for handling direct naming and operations on 
the dataset URL itself.  This (SPARQL_UberServlet*) is not active by default 
yet because I also want to put in place an approach to security (looking at 
Apache Shiro) and it may make it hard to filter fro security if the kind of 
operation (R or W) is within the query string.

See also JENA-201 (Fuseki delivered as a WAR file)



> Jena 3 / technical
> --
>
> Key: JENA-189
> URL: https://issues.apache.org/jira/browse/JENA-189
> Project: Apache Jena
>  Issue Type: Brainstorming
>Reporter: Andy Seaborne
>
> This is a JIRA to discuss and collect technical changes to Jena that would 
> warrant a "Jena3" whether an incompatible change or just sufficient changes 
> to mean bumping the major version number is best.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (JENA-319) If the URI for the named graph in a Dataset does not contain a colon ":" it is accepted but can not be retrieved.

2012-09-11 Thread Andy Seaborne (JIRA) 

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

Andy Seaborne closed JENA-319.
--


> If the URI for the named graph in a Dataset does not contain a colon ":" it 
> is accepted but can not be retrieved.
> -
>
> Key: JENA-319
> URL: https://issues.apache.org/jira/browse/JENA-319
> Project: Apache Jena
>  Issue Type: Bug
>Reporter: Claude Warren
>Assignee: Andy Seaborne
> Attachments: DatasetGraphNameTest.java
>
>
> If dataset.addNamedModel(uri, m) is called and 'uri' does not have a colon 
> the query select * { graph  { ?s ?o ?p }} does not return any results 
> even though select ?g { graph ?g { ?s ?o ?p }} will return the uri as ?g.
> JUnit based test case attached.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira