[GitHub] jena pull request: Updated text indexing

[ehedgehog]

GitHub user ehedgehog opened a pull request:

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

Updated text indexing

This change addresses JENA-686, support for cross field conjunctive queries 
in jena-text, by
allowing TextDocProducers to be specified in a TextDatasetAssembler 
assembly and
existing index entities to be updated as well as added. 

DatasetTextGraph - commit's monitor finish() moved to the top
of the method. This is because a batching TextDocProducer
(as we have in our external app) may have quads buffered up
awaiting end-of-batch and they must be flushed by finish();
if they are not, they  are auto-flushed after the commit has
been run and an exception is thrown.

TextDatasetFactory - needed methods to create datasets with
doc producers and close-index-on-close flags

TextIndex - added new operation updateEntity to allow update
of (possibly) existing entities

TextIndexLucene - added implementation of updateEntity. Added
deleteDocuments(Term) for deletion of documents (as is used
in ppd-text-index text doc producer batch).

TextDatasetAssembler - updated to allow specification of doc
producer (since done by mainline Jena) and close-index-on
close.

AbstractTestDatasetWithLuceneIndex, DummyDocProducer,
TestTextDatasetAssembler - fix up some issues in the test 
framework (use of statics vs use of instance variables,
remembering to close datasets @After done, etc).


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

$ git pull https://github.com/epimorphics/jena-config-doc-producer 
updated-text-indexing

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

https://github.com/apache/jena/pull/39.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 #39


commit 1a919696739e60d46f92b1e58d0fbefb50c14dee
Author: Chris Dollin 
Date:   2015-02-19T15:44:20Z

Integrated changes to jena-text
from work on JENA-686.

commit 5c4e91981f3564252cd74d638285497d149229b2
Author: Chris Dollin 
Date:   2015-02-20T11:31:27Z

Merged in the changes since the apache-jena
fork (over 400 commits) and fix up the jena-text changes that get conflicts 
(mostly due to the
automatic merge not handling all the cases well).

commit c702ba48388304dfaf88e84788aed59d3566d685
Author: Chris Dollin 
Date:   2015-02-26T09:40:33Z

Fixed conflicts following merge with latest jena master.

commit d7040a9955a62eeef2e16d38eefb101420a07c06
Author: Chris Dollin 
Date:   2015-02-26T12:02:52Z

Updated dataset assembler so that it can handle dociument
producers that need a dataset as well as a text index, viz, the dependant 
text indexer.




---
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-686) Add support for cross field conjunctive queries in jena-text

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on JENA-686:
-

GitHub user ehedgehog opened a pull request:

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

Updated text indexing

This change addresses JENA-686, support for cross field conjunctive queries 
in jena-text, by
allowing TextDocProducers to be specified in a TextDatasetAssembler 
assembly and
existing index entities to be updated as well as added. 

DatasetTextGraph - commit's monitor finish() moved to the top
of the method. This is because a batching TextDocProducer
(as we have in our external app) may have quads buffered up
awaiting end-of-batch and they must be flushed by finish();
if they are not, they  are auto-flushed after the commit has
been run and an exception is thrown.

TextDatasetFactory - needed methods to create datasets with
doc producers and close-index-on-close flags

TextIndex - added new operation updateEntity to allow update
of (possibly) existing entities

TextIndexLucene - added implementation of updateEntity. Added
deleteDocuments(Term) for deletion of documents (as is used
in ppd-text-index text doc producer batch).

TextDatasetAssembler - updated to allow specification of doc
producer (since done by mainline Jena) and close-index-on
close.

AbstractTestDatasetWithLuceneIndex, DummyDocProducer,
TestTextDatasetAssembler - fix up some issues in the test 
framework (use of statics vs use of instance variables,
remembering to close datasets @After done, etc).


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

$ git pull https://github.com/epimorphics/jena-config-doc-producer 
updated-text-indexing

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

https://github.com/apache/jena/pull/39.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 #39


commit 1a919696739e60d46f92b1e58d0fbefb50c14dee
Author: Chris Dollin 
Date:   2015-02-19T15:44:20Z

Integrated changes to jena-text
from work on JENA-686.

commit 5c4e91981f3564252cd74d638285497d149229b2
Author: Chris Dollin 
Date:   2015-02-20T11:31:27Z

Merged in the changes since the apache-jena
fork (over 400 commits) and fix up the jena-text changes that get conflicts 
(mostly due to the
automatic merge not handling all the cases well).

commit c702ba48388304dfaf88e84788aed59d3566d685
Author: Chris Dollin 
Date:   2015-02-26T09:40:33Z

Fixed conflicts following merge with latest jena master.

commit d7040a9955a62eeef2e16d38eefb101420a07c06
Author: Chris Dollin 
Date:   2015-02-26T12:02:52Z

Updated dataset assembler so that it can handle dociument
producers that need a dataset as well as a text index, viz, the dependant 
text indexer.




> Add support for cross field conjunctive queries in jena-text
> 
>
> Key: JENA-686
> URL: https://issues.apache.org/jira/browse/JENA-686
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Text
>Affects Versions: Jena 2.11.1, Fuseki 1.0.1
>Reporter: Brian McBride
>Assignee: christopher james dollin
> Attachments: TestDatasetWithBatchProducer.java
>
>
> We have a project where we are doing text search on addresses and wish to do 
> jena text queries like "city:liverpool AND street:green".  These queries 
> return no results, whilst queries like "street:green AND street:lane" work 
> fine.
> The reason is that jena text indexes each property in a separate Lucene 
> document, so there is no Lucene document matching city:liverpool AND 
> street:green, there are two documents, one for each property.
> Given the scale of our data, we really want to do the conjunctive query in 
> Lucene and not two separate queries and then a filter in SPARQL.
> I will attach a test case from an attempt to solve this for us to illustrate.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Jena-686, was: release planning 2.13.0

[chris dollin]

To Stephen

(Continuing on-list but asking if it would now be appropriate for
Stephen and I to discuss off-list)

Hi Stephen, I have be queuing up a write-to-you for a while.

On Thursday, February 26, 2015 11:37:50 AM Stephen Allen wrote:
> On Wed, Feb 25, 2015 at 6:56 AM, Chris Dollin 
> wrote:
> > On 02/25/2015 11:30 AM, Andy Seaborne wrote:
> >> Final call for Jena 2.13.0.
> >
> > Stephen wrote:
> >  I finished up and commited some outstanding changes I had for jena-text.
> >
> >>> I
> >>> added the ability to specify an analyzer for the query text itself that
> >>> was
> >>> different than the one used for the document.  I also added some
> >>> documentation explaining it on the site.
> >>
> >> Is there a JIRA for these changes?  I have only a superficial
> >> understanding here
> >> but is any of this  related to JENA-686?
> >>
> >> Stephen+Chris : maybe some discussion of plans and intentions on the dev@
> >> list?
> >
> > Sure. I have some notes about what the 686 changes are about I can
> > transcribe. I have been making the (originally small) changes for
> > 686 compatible with master and have (rightly or wrongly) been delaying
> > discussion until I had something that seemed to be sound.
> >
> > Right Now I'm merging in the latest master changes and am expecting to
> > make a pull request this PM.

And yesterday I successfully integrated against the latest master.

> > I'm guessing that it's unlikely the changes will be reviewed in time
> > to make it into 2.13.0?

We (I) decided that the changes would not have time to be properly reviewed
for 2.13.0 but wish them to be integrated as soon as convenient.

> The query analyzer change is pretty separate from JENA-686, it just exposes
> a capability that Lucene already has.  This is useful for example if you
> are using the StandardAnalyzer to tokenize the stored document, but perhaps
> you want to use one that tokenizes the query string differently.  You
> already could do this with jena-text's Solr implementation, since the
> configuration for that is controlled via the Solr config file.

Yes, the analyzer change doesn't affect JENA-686 except that it's treading
in the same code.

> The conjunctive query idea of Chris' is also something I would look forward
> to.  It actually looks like I may have implemented a feature that Chris
> needed, the ability to specify a custom TextDocProducer.

Yes, our fork had that capability in it. Yesterday I integrated our fork with
your code and switched to the assembler vocabulary you were using.

>  Chris: I would be interested to see your approach for this.

(Credit where credit's due; the code for this was developed by my
colleagues at Epimorphics.)

> Are you planning on waiting until all statements have been inserted
> then querying the RDF store to regenerate the documents for subjects
> that have been changed?  How do you handle triple deletion?

[Answer to follow, so as not to delay this message any more ...]

> I implemented the custom TextDocProducer for a slightly different reason,
> which was to handle triple deletions and remove the document from the
> lucene index.  However, my triple deletion code is kind of a hack (I am
> only currently indexing rdfs:label, and my application enforces a
> cardinality of 1 for that property, so I can just delete all documents with
> a given subject and predicate).  The index does not actually keep the value
> of the document, it only indexes it, so this solution would not work in the
> general case.  I would propose in the future that we actual store and not
> just index the document so that it can be appropriately identified and
> deleted.  This would require a change to existing Lucene databases (we
> should provide a tool to reindex existing data).  An alternative to
> actually storing the value would be to generate a hash of the
> subject+predicate+object and store that as an identifier.

[Likewise]

> Chris, I see in the JIRA that you talk about committing work to a branch,
> but I can't seem to locate it.  Is this in github somewhere?

Yes, we have a fork of apache-jena

https://github.com/epimorphics/jena-config-doc-producer

and the branch is

updated-text-indexing

Chris
-- 
Chris "allusive" Dollin

[jira] [Closed] (JENA-862) NodeFactoryExtra.parseNode() gives wrong result for ""

[Andy Seaborne (JIRA)]

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

Andy Seaborne closed JENA-862.
--
Resolution: Invalid
  Assignee: Andy Seaborne

> NodeFactoryExtra.parseNode() gives wrong result for ""
> -
>
> Key: JENA-862
> URL: https://issues.apache.org/jira/browse/JENA-862
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Jena
>Affects Versions: Jena 2.12.1
>Reporter: Hendy Irawan
>Assignee: Andy Seaborne
>Priority: Trivial
>
> For example:
> {code}
> NodeFactoryExtra.parseNode('')
> {code}
> (prefixMap has no effect, I even tried setting a "default" namespace by 
> adding prefixMap ''='http://yago-knowledge.org/resource/' but has no effect)
> It gives a {{Node_URI}} with:
> * toString() = hasPopulationDensity
> * nameSpace=h
> * localName=asPopulationDensity
> I'd expect {{nameSpace=null}} and {{localName=hasPopulationDensity}} at the 
> minimum.
> Or if possible, support a default namespace in prefixMap so when a "" prefix 
> is configured I can get:
> * toString() = http://yago-knowledge.org/resource/hasPopulationDensity
> * nameSpace=http://yago-knowledge.org/resource/
> * localName=hasPopulationDensity
> Or perhaps I'm doing this wrong?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (JENA-869) Fuseki2: Can't reuse dataset name after DELETE

[Andy Seaborne (JIRA)]

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

Andy Seaborne updated JENA-869:
---
Environment: (was: Docker 
https://registry.hub.docker.com/u/stain/jena-fuseki/)

> Fuseki2: Can't reuse dataset name after DELETE
> --
>
> Key: JENA-869
> URL: https://issues.apache.org/jira/browse/JENA-869
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Affects Versions: Fuseki 2.0.0
>Reporter: Stian Soiland-Reyes
> Fix For: Fuseki 2.0.0
>
>
> In the web interface, I create a persistent dataset "test1". I then remove 
> it. I then create a second one called "test1". Everything works fine.
> However, if I restart Fuseki, now it attemps to register test1 twice:
> {code}
> [2015-01-28 12:47:33] ServletINFO  Initializing Shiro environment
> [2015-01-28 12:47:33] Config INFO  Shiro file: file:///fuseki/shiro.ini
> [2015-01-28 12:47:33] BuilderINFO  Service: TDB test1
> [2015-01-28 12:47:34] BuilderINFO  Service: TDB test1
> [2015-01-28 12:47:34] BuilderINFO  Service: :service1
> [2015-01-28 12:47:34] BuilderINFO  Service: TDB test3
> [2015-01-28 12:47:34] Config INFO  Register: /test1
> [2015-01-28 12:47:34] Config INFO  Register: /test1
> [2015-01-28 12:47:34] Server ERROR Exception in initialization: Already 
> registered: /test1
> [2015-01-28 12:47:34] WebAppContext WARN  Failed startup of context 
> o.e.j.w.WebAppContext@d04ca48{/,file:/jena-fuseki/webapp/,STARTING}
> org.apache.jena.fuseki.FusekiException: Already registered: /test1
>   at 
> org.apache.jena.fuseki.server.DataAccessPointRegistry.register(DataAccessPointRegistry.java:28)
>   at 
> org.apache.jena.fuseki.server.FusekiServer.enable(FusekiServer.java:232)
>   at 
> org.apache.jena.fuseki.server.FusekiServer.initializeDataAccessPoints(FusekiServer.java:226)
>   at 
> org.apache.jena.fuseki.server.FusekiServerListener.init(FusekiServerListener.java:70)
>   at 
> org.apache.jena.fuseki.server.FusekiServerListener.contextInitialized(FusekiServerListener.java:45)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:799)
>   at 
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:446)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
>   at 
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:296)
>   at 
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1347)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:743)
>   at 
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:492)
>   at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
>   at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:117)
>   at org.eclipse.jetty.server.Server.start(Server.java:355)
>   at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:99)
>   at 
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:60)
>   at org.eclipse.jetty.server.Server.doStart(Server.java:324)
>   at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
>   at org.apache.jena.fuseki.jetty.JettyFuseki.start(JettyFuseki.java:137)
>   at 
> org.apache.jena.fuseki.cmd.FusekiCmd$FusekiCmdInner.exec(FusekiCmd.java:331)
>   at arq.cmdline.CmdMain.mainMethod(CmdMain.java:102)
>   at arq.cmdline.CmdMain.mainRun(CmdMain.java:63)
>   at arq.cmdline.CmdMain.mainRun(CmdMain.java:50)
>   at 
> org.apache.jena.fuseki.cmd.FusekiCmd$FusekiCmdInner.innerMain(FusekiCmd.java:97)
>   at org.apache.jena.fuseki.cmd.FusekiCmd.main(FusekiCmd.java:60)
> {code}
> In the HTTP log from before:
> {code}
> [2015-01-28 12:47:02] Admin  INFO  [1] GET http://localhost:3031/$/server
> [2015-01-28 12:47:02] Admin  INFO  [1] 200 OK (11 ms) 
> [2015-01-28 12:47:04] Admin  INFO  [2] GET http://localhost:3031/$/server
> [2015-01-28 12:47:04] Admin  INFO  [2] 200 OK (1 ms) 
> [2015-01-28 12:47:08] Admin  INFO  [3] POST 
> http://localhost:3031/$/datasets
> [2015-01-28 12:47:08] Admin  INFO  [3] Create database : name = /test1
> [2015-01-28 12:47:08] BuilderINFO  Service: TDB test1
> [2015-01-28 12:47:08] Admin  INFO  [3] 200 OK (499 ms) 
> [2015-01-28 12:47:09] Admin  INFO  [4] GET http://localhost:3031/$/server
> [2015-01-28 12:47:09] Admin  INFO  [4] 200 OK (2 ms) 
> [2015-01-28 12:47:12] Admin  INFO  [5] POST 
> http://localhost:3031/$/datasets
> [2015-01-28 12:47:12] Admin  INFO  [5] Create data

[jira] [Commented] (JENA-869) Fuseki2: Can't reuse dataset name after DELETE

[Andy Seaborne (JIRA)]

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

Andy Seaborne commented on JENA-869:


Only affects TDB datasets.

> Fuseki2: Can't reuse dataset name after DELETE
> --
>
> Key: JENA-869
> URL: https://issues.apache.org/jira/browse/JENA-869
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Affects Versions: Fuseki 2.0.0
>Reporter: Stian Soiland-Reyes
> Fix For: Fuseki 2.0.0
>
>
> In the web interface, I create a persistent dataset "test1". I then remove 
> it. I then create a second one called "test1". Everything works fine.
> However, if I restart Fuseki, now it attemps to register test1 twice:
> {code}
> [2015-01-28 12:47:33] ServletINFO  Initializing Shiro environment
> [2015-01-28 12:47:33] Config INFO  Shiro file: file:///fuseki/shiro.ini
> [2015-01-28 12:47:33] BuilderINFO  Service: TDB test1
> [2015-01-28 12:47:34] BuilderINFO  Service: TDB test1
> [2015-01-28 12:47:34] BuilderINFO  Service: :service1
> [2015-01-28 12:47:34] BuilderINFO  Service: TDB test3
> [2015-01-28 12:47:34] Config INFO  Register: /test1
> [2015-01-28 12:47:34] Config INFO  Register: /test1
> [2015-01-28 12:47:34] Server ERROR Exception in initialization: Already 
> registered: /test1
> [2015-01-28 12:47:34] WebAppContext WARN  Failed startup of context 
> o.e.j.w.WebAppContext@d04ca48{/,file:/jena-fuseki/webapp/,STARTING}
> org.apache.jena.fuseki.FusekiException: Already registered: /test1
>   at 
> org.apache.jena.fuseki.server.DataAccessPointRegistry.register(DataAccessPointRegistry.java:28)
>   at 
> org.apache.jena.fuseki.server.FusekiServer.enable(FusekiServer.java:232)
>   at 
> org.apache.jena.fuseki.server.FusekiServer.initializeDataAccessPoints(FusekiServer.java:226)
>   at 
> org.apache.jena.fuseki.server.FusekiServerListener.init(FusekiServerListener.java:70)
>   at 
> org.apache.jena.fuseki.server.FusekiServerListener.contextInitialized(FusekiServerListener.java:45)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:799)
>   at 
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:446)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
>   at 
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:296)
>   at 
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1347)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:743)
>   at 
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:492)
>   at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
>   at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:117)
>   at org.eclipse.jetty.server.Server.start(Server.java:355)
>   at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:99)
>   at 
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:60)
>   at org.eclipse.jetty.server.Server.doStart(Server.java:324)
>   at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
>   at org.apache.jena.fuseki.jetty.JettyFuseki.start(JettyFuseki.java:137)
>   at 
> org.apache.jena.fuseki.cmd.FusekiCmd$FusekiCmdInner.exec(FusekiCmd.java:331)
>   at arq.cmdline.CmdMain.mainMethod(CmdMain.java:102)
>   at arq.cmdline.CmdMain.mainRun(CmdMain.java:63)
>   at arq.cmdline.CmdMain.mainRun(CmdMain.java:50)
>   at 
> org.apache.jena.fuseki.cmd.FusekiCmd$FusekiCmdInner.innerMain(FusekiCmd.java:97)
>   at org.apache.jena.fuseki.cmd.FusekiCmd.main(FusekiCmd.java:60)
> {code}
> In the HTTP log from before:
> {code}
> [2015-01-28 12:47:02] Admin  INFO  [1] GET http://localhost:3031/$/server
> [2015-01-28 12:47:02] Admin  INFO  [1] 200 OK (11 ms) 
> [2015-01-28 12:47:04] Admin  INFO  [2] GET http://localhost:3031/$/server
> [2015-01-28 12:47:04] Admin  INFO  [2] 200 OK (1 ms) 
> [2015-01-28 12:47:08] Admin  INFO  [3] POST 
> http://localhost:3031/$/datasets
> [2015-01-28 12:47:08] Admin  INFO  [3] Create database : name = /test1
> [2015-01-28 12:47:08] BuilderINFO  Service: TDB test1
> [2015-01-28 12:47:08] Admin  INFO  [3] 200 OK (499 ms) 
> [2015-01-28 12:47:09] Admin  INFO  [4] GET http://localhost:3031/$/server
> [2015-01-28 12:47:09] Admin  INFO  [4] 200 OK (2 ms) 
> [2015-01-28 12:47:12] Admin  INFO  [5] POST 
> http://localhost:3031/$/datasets
> [2015-01-28 12:47:12] Admin  INFO  [5] Create database

[GitHub] jena pull request: JENA-869 Disable Remove button until it works a...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-867) Fuseki2: Dataset "Active" tickbox does not work

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on JENA-867:
-

Github user asfgit closed the pull request at:

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


> Fuseki2: Dataset "Active" tickbox does not work
> ---
>
> Key: JENA-867
> URL: https://issues.apache.org/jira/browse/JENA-867
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Affects Versions: Fuseki 2.0.0
> Environment: Ubuntu 14.10 x64
> Firefox 35.0
> BasicAuth in shiro.ini
>Reporter: Stian Soiland-Reyes
>Priority: Trivial
> Fix For: Fuseki 2.0.0
>
>
> Under Manage Datasets, unticking "Active" for a created dataset does not do 
> anything, neither for memory or persisted datasets.
> Presumably unticking Active would allow me to populate the database with TDB 
> on the command line tool - so I can see this is a useful feature.
> If you navigate to a different page, the dataset is still in the dropdown 
> list for Query (which still works), and navigating back to Dataset it is 
> ticked again. So the datasets remain active.
> Inspection in Developer Tools reveal no AJAX calls are made when 
> ticking/unticking.
> Suggested quick-fix for the release is to hide the tickbox from the UI.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JENA-867) Fuseki2: Dataset "Active" tickbox does not work

[ASF subversion and git services (JIRA)]

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

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

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

JENA-867 : Disable checkbox for 'Active'


> Fuseki2: Dataset "Active" tickbox does not work
> ---
>
> Key: JENA-867
> URL: https://issues.apache.org/jira/browse/JENA-867
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Affects Versions: Fuseki 2.0.0
> Environment: Ubuntu 14.10 x64
> Firefox 35.0
> BasicAuth in shiro.ini
>Reporter: Stian Soiland-Reyes
>Priority: Trivial
> Fix For: Fuseki 2.0.0
>
>
> Under Manage Datasets, unticking "Active" for a created dataset does not do 
> anything, neither for memory or persisted datasets.
> Presumably unticking Active would allow me to populate the database with TDB 
> on the command line tool - so I can see this is a useful feature.
> If you navigate to a different page, the dataset is still in the dropdown 
> list for Query (which still works), and navigating back to Dataset it is 
> ticked again. So the datasets remain active.
> Inspection in Developer Tools reveal no AJAX calls are made when 
> ticking/unticking.
> Suggested quick-fix for the release is to hide the tickbox from the UI.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] jena pull request: JENA-867 - temporarily disable "Active?" tickbo...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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] [Updated] (JENA-887) Dead/wrong links on Fuseki2 front page

[Andy Seaborne (JIRA)]

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

Andy Seaborne updated JENA-887:
---
Summary: Dead/wrong links on Fuseki2 front page  (was: Dead/wrong links on 
Fuseki2 frong page)

> Dead/wrong links on Fuseki2 front page
> --
>
> Key: JENA-887
> URL: https://issues.apache.org/jira/browse/JENA-887
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Reporter: Stian Soiland-Reyes
>Assignee: Andy Seaborne
> Fix For: Fuseki 2.0.0
>
>
> Most of these links 404 or go to the wrong page - on http://localhost:3030/ 
> of Fuseki 2:
> {quote}
> Use the following pages to perform actions or tasks on this server:
> SPARQL query form
> to run a SPARQL query against one of the active datasets hosted by this 
> server
> validate
> to validate SPARQL query syntax, or RDF data syntax
> administer
> to administer the datasets on this server, including adding and removing 
> datasets, enabling data services, uploading data and performing backups. 
> logs
> to view server log files
> help
> for a summary of commands, and links to online documentation 
> {quote}
> Suggestion is to update links.
> AFAIK there is no common query across datasets in the Fuseki2 UI - so 'query' 
> would instead just point to "datasets"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JENA-869) Fuseki2: Can't reuse dataset name after DELETE

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on JENA-869:
-

Github user asfgit closed the pull request at:

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


> Fuseki2: Can't reuse dataset name after DELETE
> --
>
> Key: JENA-869
> URL: https://issues.apache.org/jira/browse/JENA-869
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Affects Versions: Fuseki 2.0.0
>Reporter: Stian Soiland-Reyes
> Fix For: Fuseki 2.0.0
>
>
> In the web interface, I create a persistent dataset "test1". I then remove 
> it. I then create a second one called "test1". Everything works fine.
> However, if I restart Fuseki, now it attemps to register test1 twice:
> {code}
> [2015-01-28 12:47:33] ServletINFO  Initializing Shiro environment
> [2015-01-28 12:47:33] Config INFO  Shiro file: file:///fuseki/shiro.ini
> [2015-01-28 12:47:33] BuilderINFO  Service: TDB test1
> [2015-01-28 12:47:34] BuilderINFO  Service: TDB test1
> [2015-01-28 12:47:34] BuilderINFO  Service: :service1
> [2015-01-28 12:47:34] BuilderINFO  Service: TDB test3
> [2015-01-28 12:47:34] Config INFO  Register: /test1
> [2015-01-28 12:47:34] Config INFO  Register: /test1
> [2015-01-28 12:47:34] Server ERROR Exception in initialization: Already 
> registered: /test1
> [2015-01-28 12:47:34] WebAppContext WARN  Failed startup of context 
> o.e.j.w.WebAppContext@d04ca48{/,file:/jena-fuseki/webapp/,STARTING}
> org.apache.jena.fuseki.FusekiException: Already registered: /test1
>   at 
> org.apache.jena.fuseki.server.DataAccessPointRegistry.register(DataAccessPointRegistry.java:28)
>   at 
> org.apache.jena.fuseki.server.FusekiServer.enable(FusekiServer.java:232)
>   at 
> org.apache.jena.fuseki.server.FusekiServer.initializeDataAccessPoints(FusekiServer.java:226)
>   at 
> org.apache.jena.fuseki.server.FusekiServerListener.init(FusekiServerListener.java:70)
>   at 
> org.apache.jena.fuseki.server.FusekiServerListener.contextInitialized(FusekiServerListener.java:45)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:799)
>   at 
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:446)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
>   at 
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:296)
>   at 
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1347)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:743)
>   at 
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:492)
>   at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
>   at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:117)
>   at org.eclipse.jetty.server.Server.start(Server.java:355)
>   at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:99)
>   at 
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:60)
>   at org.eclipse.jetty.server.Server.doStart(Server.java:324)
>   at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
>   at org.apache.jena.fuseki.jetty.JettyFuseki.start(JettyFuseki.java:137)
>   at 
> org.apache.jena.fuseki.cmd.FusekiCmd$FusekiCmdInner.exec(FusekiCmd.java:331)
>   at arq.cmdline.CmdMain.mainMethod(CmdMain.java:102)
>   at arq.cmdline.CmdMain.mainRun(CmdMain.java:63)
>   at arq.cmdline.CmdMain.mainRun(CmdMain.java:50)
>   at 
> org.apache.jena.fuseki.cmd.FusekiCmd$FusekiCmdInner.innerMain(FusekiCmd.java:97)
>   at org.apache.jena.fuseki.cmd.FusekiCmd.main(FusekiCmd.java:60)
> {code}
> In the HTTP log from before:
> {code}
> [2015-01-28 12:47:02] Admin  INFO  [1] GET http://localhost:3031/$/server
> [2015-01-28 12:47:02] Admin  INFO  [1] 200 OK (11 ms) 
> [2015-01-28 12:47:04] Admin  INFO  [2] GET http://localhost:3031/$/server
> [2015-01-28 12:47:04] Admin  INFO  [2] 200 OK (1 ms) 
> [2015-01-28 12:47:08] Admin  INFO  [3] POST 
> http://localhost:3031/$/datasets
> [2015-01-28 12:47:08] Admin  INFO  [3] Create database : name = /test1
> [2015-01-28 12:47:08] BuilderINFO  Service: TDB test1
> [2015-01-28 12:47:08] Admin  INFO  [3] 200 OK (499 ms) 
> [2015-01-28 12:47:09] Admin  INFO  [4] GET http://localhost:3031/$/server
> [2015-01-28 12:47:09] Admin  INFO  [4] 200 OK (2 ms) 
> [2015-01-28 12:47:12] Admin  INFO  [5] POST 
> http://localhost:3031/$/da

[jira] [Commented] (JENA-869) Fuseki2: Can't reuse dataset name after DELETE

[ASF subversion and git services (JIRA)]

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

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

Commit 9ed1e145b2d534202d94d806e3b311dbcdb1b51b in jena's branch 
refs/heads/master from [~soilandreyes]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=9ed1e14 ]

JENA-869 Disable remove button until it works again


> Fuseki2: Can't reuse dataset name after DELETE
> --
>
> Key: JENA-869
> URL: https://issues.apache.org/jira/browse/JENA-869
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Affects Versions: Fuseki 2.0.0
>Reporter: Stian Soiland-Reyes
> Fix For: Fuseki 2.0.0
>
>
> In the web interface, I create a persistent dataset "test1". I then remove 
> it. I then create a second one called "test1". Everything works fine.
> However, if I restart Fuseki, now it attemps to register test1 twice:
> {code}
> [2015-01-28 12:47:33] ServletINFO  Initializing Shiro environment
> [2015-01-28 12:47:33] Config INFO  Shiro file: file:///fuseki/shiro.ini
> [2015-01-28 12:47:33] BuilderINFO  Service: TDB test1
> [2015-01-28 12:47:34] BuilderINFO  Service: TDB test1
> [2015-01-28 12:47:34] BuilderINFO  Service: :service1
> [2015-01-28 12:47:34] BuilderINFO  Service: TDB test3
> [2015-01-28 12:47:34] Config INFO  Register: /test1
> [2015-01-28 12:47:34] Config INFO  Register: /test1
> [2015-01-28 12:47:34] Server ERROR Exception in initialization: Already 
> registered: /test1
> [2015-01-28 12:47:34] WebAppContext WARN  Failed startup of context 
> o.e.j.w.WebAppContext@d04ca48{/,file:/jena-fuseki/webapp/,STARTING}
> org.apache.jena.fuseki.FusekiException: Already registered: /test1
>   at 
> org.apache.jena.fuseki.server.DataAccessPointRegistry.register(DataAccessPointRegistry.java:28)
>   at 
> org.apache.jena.fuseki.server.FusekiServer.enable(FusekiServer.java:232)
>   at 
> org.apache.jena.fuseki.server.FusekiServer.initializeDataAccessPoints(FusekiServer.java:226)
>   at 
> org.apache.jena.fuseki.server.FusekiServerListener.init(FusekiServerListener.java:70)
>   at 
> org.apache.jena.fuseki.server.FusekiServerListener.contextInitialized(FusekiServerListener.java:45)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:799)
>   at 
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:446)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
>   at 
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:296)
>   at 
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1347)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:743)
>   at 
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:492)
>   at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
>   at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:117)
>   at org.eclipse.jetty.server.Server.start(Server.java:355)
>   at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:99)
>   at 
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:60)
>   at org.eclipse.jetty.server.Server.doStart(Server.java:324)
>   at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
>   at org.apache.jena.fuseki.jetty.JettyFuseki.start(JettyFuseki.java:137)
>   at 
> org.apache.jena.fuseki.cmd.FusekiCmd$FusekiCmdInner.exec(FusekiCmd.java:331)
>   at arq.cmdline.CmdMain.mainMethod(CmdMain.java:102)
>   at arq.cmdline.CmdMain.mainRun(CmdMain.java:63)
>   at arq.cmdline.CmdMain.mainRun(CmdMain.java:50)
>   at 
> org.apache.jena.fuseki.cmd.FusekiCmd$FusekiCmdInner.innerMain(FusekiCmd.java:97)
>   at org.apache.jena.fuseki.cmd.FusekiCmd.main(FusekiCmd.java:60)
> {code}
> In the HTTP log from before:
> {code}
> [2015-01-28 12:47:02] Admin  INFO  [1] GET http://localhost:3031/$/server
> [2015-01-28 12:47:02] Admin  INFO  [1] 200 OK (11 ms) 
> [2015-01-28 12:47:04] Admin  INFO  [2] GET http://localhost:3031/$/server
> [2015-01-28 12:47:04] Admin  INFO  [2] 200 OK (1 ms) 
> [2015-01-28 12:47:08] Admin  INFO  [3] POST 
> http://localhost:3031/$/datasets
> [2015-01-28 12:47:08] Admin  INFO  [3] Create database : name = /test1
> [2015-01-28 12:47:08] BuilderINFO  Service: TDB test1
> [2015-01-28 12:47:08] Admin  INFO  [3] 200 OK (499 ms) 
> [2015-01-28 12:47:09] Admin  INFO  [4] GET http

[jira] [Assigned] (JENA-887) Dead/wrong links on Fuseki2 frong page

[Andy Seaborne (JIRA)]

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

Andy Seaborne reassigned JENA-887:
--

Assignee: Andy Seaborne

> Dead/wrong links on Fuseki2 frong page
> --
>
> Key: JENA-887
> URL: https://issues.apache.org/jira/browse/JENA-887
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Reporter: Stian Soiland-Reyes
>Assignee: Andy Seaborne
> Fix For: Fuseki 2.0.0
>
>
> Most of these links 404 or go to the wrong page - on http://localhost:3030/ 
> of Fuseki 2:
> {quote}
> Use the following pages to perform actions or tasks on this server:
> SPARQL query form
> to run a SPARQL query against one of the active datasets hosted by this 
> server
> validate
> to validate SPARQL query syntax, or RDF data syntax
> administer
> to administer the datasets on this server, including adding and removing 
> datasets, enabling data services, uploading data and performing backups. 
> logs
> to view server log files
> help
> for a summary of commands, and links to online documentation 
> {quote}
> Suggestion is to update links.
> AFAIK there is no common query across datasets in the Fuseki2 UI - so 'query' 
> would instead just point to "datasets"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (JENA-887) Dead/wrong links on Fuseki2 front page

[Andy Seaborne (JIRA)]

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

Andy Seaborne closed JENA-887.
--
Resolution: Done

> Dead/wrong links on Fuseki2 front page
> --
>
> Key: JENA-887
> URL: https://issues.apache.org/jira/browse/JENA-887
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Reporter: Stian Soiland-Reyes
>Assignee: Andy Seaborne
> Fix For: Fuseki 2.0.0
>
>
> Most of these links 404 or go to the wrong page - on http://localhost:3030/ 
> of Fuseki 2:
> {quote}
> Use the following pages to perform actions or tasks on this server:
> SPARQL query form
> to run a SPARQL query against one of the active datasets hosted by this 
> server
> validate
> to validate SPARQL query syntax, or RDF data syntax
> administer
> to administer the datasets on this server, including adding and removing 
> datasets, enabling data services, uploading data and performing backups. 
> logs
> to view server log files
> help
> for a summary of commands, and links to online documentation 
> {quote}
> Suggestion is to update links.
> AFAIK there is no common query across datasets in the Fuseki2 UI - so 'query' 
> would instead just point to "datasets"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Reopened] (JENA-887) Dead/wrong links on Fuseki2 front page

[Andy Seaborne (JIRA)]

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

Andy Seaborne reopened JENA-887:


Fix JIRA

> Dead/wrong links on Fuseki2 front page
> --
>
> Key: JENA-887
> URL: https://issues.apache.org/jira/browse/JENA-887
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Reporter: Stian Soiland-Reyes
>Assignee: Andy Seaborne
> Fix For: Fuseki 2.0.0
>
>
> Most of these links 404 or go to the wrong page - on http://localhost:3030/ 
> of Fuseki 2:
> {quote}
> Use the following pages to perform actions or tasks on this server:
> SPARQL query form
> to run a SPARQL query against one of the active datasets hosted by this 
> server
> validate
> to validate SPARQL query syntax, or RDF data syntax
> administer
> to administer the datasets on this server, including adding and removing 
> datasets, enabling data services, uploading data and performing backups. 
> logs
> to view server log files
> help
> for a summary of commands, and links to online documentation 
> {quote}
> Suggestion is to update links.
> AFAIK there is no common query across datasets in the Fuseki2 UI - so 'query' 
> would instead just point to "datasets"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Issue Comment Deleted] (JENA-887) Dead/wrong links on Fuseki2 front page

[Andy Seaborne (JIRA)]

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

Andy Seaborne updated JENA-887:
---
Comment: was deleted

(was: Fix JIRA)

> Dead/wrong links on Fuseki2 front page
> --
>
> Key: JENA-887
> URL: https://issues.apache.org/jira/browse/JENA-887
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Reporter: Stian Soiland-Reyes
>Assignee: Andy Seaborne
> Fix For: Fuseki 2.0.0
>
>
> Most of these links 404 or go to the wrong page - on http://localhost:3030/ 
> of Fuseki 2:
> {quote}
> Use the following pages to perform actions or tasks on this server:
> SPARQL query form
> to run a SPARQL query against one of the active datasets hosted by this 
> server
> validate
> to validate SPARQL query syntax, or RDF data syntax
> administer
> to administer the datasets on this server, including adding and removing 
> datasets, enabling data services, uploading data and performing backups. 
> logs
> to view server log files
> help
> for a summary of commands, and links to online documentation 
> {quote}
> Suggestion is to update links.
> AFAIK there is no common query across datasets in the Fuseki2 UI - so 'query' 
> would instead just point to "datasets"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JENA-887) Dead/wrong links on Fuseki2 front page

[Andy Seaborne (JIRA)]

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

Andy Seaborne commented on JENA-887:


See [pull request #36|https://github.com/apache/jena/pull/36].

> Dead/wrong links on Fuseki2 front page
> --
>
> Key: JENA-887
> URL: https://issues.apache.org/jira/browse/JENA-887
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Reporter: Stian Soiland-Reyes
>Assignee: Andy Seaborne
> Fix For: Fuseki 2.0.0
>
>
> Most of these links 404 or go to the wrong page - on http://localhost:3030/ 
> of Fuseki 2:
> {quote}
> Use the following pages to perform actions or tasks on this server:
> SPARQL query form
> to run a SPARQL query against one of the active datasets hosted by this 
> server
> validate
> to validate SPARQL query syntax, or RDF data syntax
> administer
> to administer the datasets on this server, including adding and removing 
> datasets, enabling data services, uploading data and performing backups. 
> logs
> to view server log files
> help
> for a summary of commands, and links to online documentation 
> {quote}
> Suggestion is to update links.
> AFAIK there is no common query across datasets in the Fuseki2 UI - so 'query' 
> would instead just point to "datasets"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (JENA-887) Dead/wrong links on Fuseki2 front page

[Andy Seaborne (JIRA)]

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

Andy Seaborne closed JENA-887.
--
Resolution: Fixed

> Dead/wrong links on Fuseki2 front page
> --
>
> Key: JENA-887
> URL: https://issues.apache.org/jira/browse/JENA-887
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Reporter: Stian Soiland-Reyes
>Assignee: Andy Seaborne
> Fix For: Fuseki 2.0.0
>
>
> Most of these links 404 or go to the wrong page - on http://localhost:3030/ 
> of Fuseki 2:
> {quote}
> Use the following pages to perform actions or tasks on this server:
> SPARQL query form
> to run a SPARQL query against one of the active datasets hosted by this 
> server
> validate
> to validate SPARQL query syntax, or RDF data syntax
> administer
> to administer the datasets on this server, including adding and removing 
> datasets, enabling data services, uploading data and performing backups. 
> logs
> to view server log files
> help
> for a summary of commands, and links to online documentation 
> {quote}
> Suggestion is to update links.
> AFAIK there is no common query across datasets in the Fuseki2 UI - so 'query' 
> would instead just point to "datasets"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JENA-887) Dead/wrong links on Fuseki2 front page

[ASF subversion and git services (JIRA)]

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

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

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

JENA-887: comment out non-working links


> Dead/wrong links on Fuseki2 front page
> --
>
> Key: JENA-887
> URL: https://issues.apache.org/jira/browse/JENA-887
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Reporter: Stian Soiland-Reyes
>Assignee: Andy Seaborne
> Fix For: Fuseki 2.0.0
>
>
> Most of these links 404 or go to the wrong page - on http://localhost:3030/ 
> of Fuseki 2:
> {quote}
> Use the following pages to perform actions or tasks on this server:
> SPARQL query form
> to run a SPARQL query against one of the active datasets hosted by this 
> server
> validate
> to validate SPARQL query syntax, or RDF data syntax
> administer
> to administer the datasets on this server, including adding and removing 
> datasets, enabling data services, uploading data and performing backups. 
> logs
> to view server log files
> help
> for a summary of commands, and links to online documentation 
> {quote}
> Suggestion is to update links.
> AFAIK there is no common query across datasets in the Fuseki2 UI - so 'query' 
> would instead just point to "datasets"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Jena-686, was: release planning 2.13.0

[Andy Seaborne]

On 27/02/15 11:55, chris dollin wrote:

(Continuing on-list but asking if it would now be appropriate for
Stephen and I to discuss off-list)


That would be completely *inappropriate*.

Apache culture is that discussion and decisions about the project should 
be on the dev@.


Discussion is for everyone.

Andy

[jira] [Closed] (JENA-865) Fuseki 2: Example query does not declare owl/rdfs PREFIXes

[Andy Seaborne (JIRA)]

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

Andy Seaborne closed JENA-865.
--
Resolution: Fixed
  Assignee: Andy Seaborne

> Fuseki 2: Example query does not declare owl/rdfs PREFIXes
> --
>
> Key: JENA-865
> URL: https://issues.apache.org/jira/browse/JENA-865
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Affects Versions: Fuseki 2.0.0
>Reporter: Stian Soiland-Reyes
>Assignee: Andy Seaborne
>Priority: Trivial
> Fix For: Fuseki 2.0.0
>
>
> If I create a new dataset through the web interface, have not uploaded any 
> data yet, and under Dataset/Query click the Example Query "
> Selection of Classes" I get the error:
> {code}
> Error 400: Parse error: 
> SELECT distinct ?class ?label ?description
> where {
>   ?class a owl:Class.
>   OPTIONAL { ?class rdfs:label ?label}
>   OPTIONAL { ?class rdfs:comment ?description}
> }
> LIMIT 25
> Line 5, column 12: Unresolved prefixed name: owl:Class
> Fuseki - version 2.0.0-SNAPSHOT (Build date: 2015-01-25T09:54:26+)
> {code}
>  
> The fix is to either add to the example query:
> {code}
> PREFIX owl: 
> PREFIX rdfs: 
> {code}
> or - much better (or in addition) - always interpret prefixes for
> owl, rdfs, rdf, xsd
> (any others?)
> Ideally 'distinct' and 'where' should also be upper-case in the example query 
> :)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (JENA-865) Fuseki 2: Example query does not declare owl/rdfs PREFIXes

[Andy Seaborne (JIRA)]

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

Andy Seaborne updated JENA-865:
---
Environment: (was: https://registry.hub.docker.com/u/stain/jena-fuseki/)

> Fuseki 2: Example query does not declare owl/rdfs PREFIXes
> --
>
> Key: JENA-865
> URL: https://issues.apache.org/jira/browse/JENA-865
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Affects Versions: Fuseki 2.0.0
>Reporter: Stian Soiland-Reyes
>Priority: Trivial
> Fix For: Fuseki 2.0.0
>
>
> If I create a new dataset through the web interface, have not uploaded any 
> data yet, and under Dataset/Query click the Example Query "
> Selection of Classes" I get the error:
> {code}
> Error 400: Parse error: 
> SELECT distinct ?class ?label ?description
> where {
>   ?class a owl:Class.
>   OPTIONAL { ?class rdfs:label ?label}
>   OPTIONAL { ?class rdfs:comment ?description}
> }
> LIMIT 25
> Line 5, column 12: Unresolved prefixed name: owl:Class
> Fuseki - version 2.0.0-SNAPSHOT (Build date: 2015-01-25T09:54:26+)
> {code}
>  
> The fix is to either add to the example query:
> {code}
> PREFIX owl: 
> PREFIX rdfs: 
> {code}
> or - much better (or in addition) - always interpret prefixes for
> owl, rdfs, rdf, xsd
> (any others?)
> Ideally 'distinct' and 'where' should also be upper-case in the example query 
> :)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] jena pull request: Jena 887 remove dead links

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-887) Dead/wrong links on Fuseki2 front page

[ASF subversion and git services (JIRA)]

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

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

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

JENA-887 : This closes #36


> Dead/wrong links on Fuseki2 front page
> --
>
> Key: JENA-887
> URL: https://issues.apache.org/jira/browse/JENA-887
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Reporter: Stian Soiland-Reyes
>Assignee: Andy Seaborne
> Fix For: Fuseki 2.0.0
>
>
> Most of these links 404 or go to the wrong page - on http://localhost:3030/ 
> of Fuseki 2:
> {quote}
> Use the following pages to perform actions or tasks on this server:
> SPARQL query form
> to run a SPARQL query against one of the active datasets hosted by this 
> server
> validate
> to validate SPARQL query syntax, or RDF data syntax
> administer
> to administer the datasets on this server, including adding and removing 
> datasets, enabling data services, uploading data and performing backups. 
> logs
> to view server log files
> help
> for a summary of commands, and links to online documentation 
> {quote}
> Suggestion is to update links.
> AFAIK there is no common query across datasets in the Fuseki2 UI - so 'query' 
> would instead just point to "datasets"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JENA-887) Dead/wrong links on Fuseki2 front page

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on JENA-887:
-

Github user asfgit closed the pull request at:

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


> Dead/wrong links on Fuseki2 front page
> --
>
> Key: JENA-887
> URL: https://issues.apache.org/jira/browse/JENA-887
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Reporter: Stian Soiland-Reyes
>Assignee: Andy Seaborne
> Fix For: Fuseki 2.0.0
>
>
> Most of these links 404 or go to the wrong page - on http://localhost:3030/ 
> of Fuseki 2:
> {quote}
> Use the following pages to perform actions or tasks on this server:
> SPARQL query form
> to run a SPARQL query against one of the active datasets hosted by this 
> server
> validate
> to validate SPARQL query syntax, or RDF data syntax
> administer
> to administer the datasets on this server, including adding and removing 
> datasets, enabling data services, uploading data and performing backups. 
> logs
> to view server log files
> help
> for a summary of commands, and links to online documentation 
> {quote}
> Suggestion is to update links.
> AFAIK there is no common query across datasets in the Fuseki2 UI - so 'query' 
> would instead just point to "datasets"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

JENA-686

[chris dollin]

(Trying to get the email thriough the system; it hasn't
appeared on my epimorphics mailbox inbox)

I posted to Stephen:

Dealing with deletions. We do not yet address the general case.
TextDocProducerTriples simply ignores the deletion case and
we don't change that behaviour in jena-text -- instead we use an
alternative docProducer (which you can see in the Epimorphics
github repository in ppd-text-index). This docProducer deals
with deletions in this way:

- incoming quads are accumulated while the subject remains
  the same. When the subject changes (or we reach finish())
  then we deal with the batch.

- we delete the documents corresponding to the subject.

- however we may have deleted documents that should still
  exist. We make a new document entity and then reach back
  into the dataset and add to the entity all the quads
  that are still in the dataset and about this subject.

- if we added any quads, then we put this new entity back
  into the index

This requires that the producer has access to the dataset,
which is why our TextDocProducerBatch takes the dataset
(graph) as one of its constructor arguments. Our branch's
assembler, when attempting to construct the producer
specified by its classname, checks to see if there's a
two-argument form (DatasetGraph, TextIndex) as well as
the one-argument form (TextIndex).


-- 
Chris "allusive" Dollin

Re: Storing values in Lucene index

[Andy Seaborne]

On 27/02/15 06:58, Osma Suominen wrote:

On 26/02/15 18:37, Stephen Allen wrote:

I would propose in the future that we actual store and not
just index the document so that it can be appropriately identified and
deleted.  This would require a change to existing Lucene databases (we
should provide a tool to reindex existing data).  An alternative to
actually storing the value would be to generate a hash of the
subject+predicate+object and store that as an identifier.


The same literal may be in the RDF graph multiple times.  It's a 
reference counting problem; maintaining a reference would be expensive 
and limit scale.



I second storing the original value in the Lucene index at least as an
option - it would obviously increase the index size, though I suspect
the increase would be rather minor if you compare it to the overall (TDB
+ text index) database size. This would be similar to how LARQ used to
work, though LARQ only provides access to the values, not the subject
resources.


Slight caveat - size of index affects the speed of Lucene so it's not 
just disk space compared to the size of the TDB database.



It would allow, with some additional code, having access to the actual
value from the SPARQL query. Something like this:

(?s ?value) text:query 'word' .

Then you could also easily check that the triple actually exists in
current RDF data (and in the current graph), with a pattern such as this:

?s rdfs:label ?value .


For me, it would probably allow some optimization of queries that
currently have to do a bit of detective work to find out which value
actually matched the query. I'm currently doing queries somewhat like this:

?s text:query (skos:altLabel 'word*') .
?s skos:altLabel ?value .
FILTER (STRSTARTS(?value, 'word'))

This is inefficient if there happen to be lots of skos:altLabel values,
as there are in e.g. AGROVOC thesaurus data.


How many skos:altLabel can occur in that dataset?

--
jena-text is a bit misnamed.  It's an entity index : "find subjects such 
that ..."  Entity indexes make the conjunctive use cases work, "find 
entities such that :property1 matches ... and :property2 matches ...".


The example above is closer to a text index (query -> literal) LARQ 
could do both in different configurations (not at the same time) through 
people tended to use it as a text index and then look in the RDF to make 
it an entity index.  It can't in a single call do the conjunctive use 
case nor be particularly easy to manage specific properties in different 
ways.


I have come to realise that we might provide both kinds of index 
separately.  A tightly managed literal-text-index could have deeper 
integration into query processing e.g. FILTER expressions.


Andy





-Osma

Re: Storing values in Lucene index

[Osma Suominen]

27.02.2015, 18:06, Andy Seaborne wrote:


This is inefficient if there happen to be lots of skos:altLabel values,
as there are in e.g. AGROVOC thesaurus data.


How many skos:altLabel can occur in that dataset?


As an extreme example,  (the 
country Chile) has 433 altLabels. The typical case (if there's such a 
thing - it's probably a long tail distribution) is more like a dozen per 
concept. AGROVOC has terms in over 20 languages. Queries involving the 
literals tend to be a bit slow...



jena-text is a bit misnamed.  It's an entity index : "find subjects such
that ..."  Entity indexes make the conjunctive use cases work, "find
entities such that :property1 matches ... and :property2 matches ...".

The example above is closer to a text index (query -> literal) LARQ
could do both in different configurations (not at the same time) through
people tended to use it as a text index and then look in the RDF to make
it an entity index.  It can't in a single call do the conjunctive use
case nor be particularly easy to manage specific properties in different
ways.

I have come to realise that we might provide both kinds of index
separately.  A tightly managed literal-text-index could have deeper
integration into query processing e.g. FILTER expressions.


I don't oppose, but I don't really follow either. Is there something 
fundamentally wrong with the (?s ?value) text:query 'blah' query style 
that I suggested? It's not like its unusual to store the actual values 
in a Lucene index... Lucene supports it (and Solr too), LARQ does it, 
many people do it. I understand that not all people will need it (and 
the associated size/performance costs), but it could be made optional.


-Osma

--
Osma Suominen
D.Sc. (Tech), Information Systems Specialist
National Library of Finland
P.O. Box 26 (Teollisuuskatu 23)
00014 HELSINGIN YLIOPISTO
Tel. +358 50 3199529
osma.suomi...@helsinki.fi
http://www.nationallibrary.fi