Re: [jira] [Commented] (JENA-952) Make the URI string visible in all jena.vocabulary classes.
I need them for annotation usage, annotations can't use functions (even
static ones).
On Mon, Jun 1, 2015 at 6:51 PM, Andy Seaborne (JIRA)
wrote:
>
> [
> https://issues.apache.org/jira/browse/JENA-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567645#comment-14567645
> ]
>
> Andy Seaborne commented on JENA-952:
>
>
> Use {{getURI()}} - they seem to all provide that.
>
> > Make the URI string visible in all jena.vocabulary classes.
> > ---
> >
> > Key: JENA-952
> > URL: https://issues.apache.org/jira/browse/JENA-952
> > Project: Apache Jena
> > Issue Type: Improvement
> >Reporter: Claude Warren
> >Assignee: Claude Warren
> >Priority: Minor
> >
> > Some jena.vocabulary classes make the URI string visible others do not.
> This change is to standardise on making them visible.
> > Classes are:
> > DC_10
> > RDF
> > RDFS
> > RDFSyntax
> > RSS
> > SKOS
> > SKOSXL
> > VCARD
> > and
> > XSD
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>
--
I like: Like Like - The likeliest place on the web
LinkedIn: http://www.linkedin.com/in/claudewarren
[jira] [Commented] (JENA-952) Make the URI string visible in all jena.vocabulary classes.
[
https://issues.apache.org/jira/browse/JENA-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567645#comment-14567645
]
Andy Seaborne commented on JENA-952:
Use {{getURI()}} - they seem to all provide that.
> Make the URI string visible in all jena.vocabulary classes.
> ---
>
> Key: JENA-952
> URL: https://issues.apache.org/jira/browse/JENA-952
> Project: Apache Jena
> Issue Type: Improvement
>Reporter: Claude Warren
>Assignee: Claude Warren
>Priority: Minor
>
> Some jena.vocabulary classes make the URI string visible others do not. This
> change is to standardise on making them visible.
> Classes are:
> DC_10
> RDF
> RDFS
> RDFSyntax
> RSS
> SKOS
> SKOSXL
> VCARD
> and
> XSD
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (JENA-952) Make the URI string visible in all jena.vocabulary classes.
[ https://issues.apache.org/jira/browse/JENA-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567625#comment-14567625 ] ASF subversion and git services commented on JENA-952: -- Commit fc1bbf3e5f104ca0244ca337849544c1f49b9e46 in jena's branch refs/heads/master from [~cla...@xenei.org] [ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=fc1bbf3 ] Made all namespace variables public. This fixes JENA-952 > Make the URI string visible in all jena.vocabulary classes. > --- > > Key: JENA-952 > URL: https://issues.apache.org/jira/browse/JENA-952 > Project: Apache Jena > Issue Type: Improvement >Reporter: Claude Warren >Assignee: Claude Warren >Priority: Minor > > Some jena.vocabulary classes make the URI string visible others do not. This > change is to standardise on making them visible. > Classes are: > DC_10 > RDF > RDFS > RDFSyntax > RSS > SKOS > SKOSXL > VCARD > and > XSD -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (JENA-952) Make the URI string visible in all jena.vocabulary classes.
[ https://issues.apache.org/jira/browse/JENA-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567626#comment-14567626 ] ASF subversion and git services commented on JENA-952: -- Commit 86e0dd85e2391b6d663f793f24348fd4a68f9191 in jena's branch refs/heads/master from [~cla...@xenei.org] [ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=86e0dd8 ] make namespace public in RDFS.java for JENA-952 > Make the URI string visible in all jena.vocabulary classes. > --- > > Key: JENA-952 > URL: https://issues.apache.org/jira/browse/JENA-952 > Project: Apache Jena > Issue Type: Improvement >Reporter: Claude Warren >Assignee: Claude Warren >Priority: Minor > > Some jena.vocabulary classes make the URI string visible others do not. This > change is to standardise on making them visible. > Classes are: > DC_10 > RDF > RDFS > RDFSyntax > RSS > SKOS > SKOSXL > VCARD > and > XSD -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] jena pull request: Jena-text multilingual alternative implementati...
Github user amiara514 commented on the pull request: https://github.com/apache/jena/pull/64#issuecomment-107613817 The update action works, thanks. --- 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] [Created] (JENA-952) Make the URI string visible in all jena.vocabulary classes.
Claude Warren created JENA-952: -- Summary: Make the URI string visible in all jena.vocabulary classes. Key: JENA-952 URL: https://issues.apache.org/jira/browse/JENA-952 Project: Apache Jena Issue Type: Improvement Reporter: Claude Warren Assignee: Claude Warren Priority: Minor Some jena.vocabulary classes make the URI string visible others do not. This change is to standardise on making them visible. Classes are: DC_10 RDF RDFS RDFSyntax RSS SKOS SKOSXL VCARD and XSD -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] jena pull request: Jena-text multilingual alternative implementati...
Github user afs commented on the pull request: https://github.com/apache/jena/pull/64#issuecomment-107605937 "Hmm" indeed. I'll trying making a small change to see if it flushes the correct mdtext file. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: Add (?uri ?score) to jena-text
Github user amiara514 commented on the pull request: https://github.com/apache/jena/pull/72#issuecomment-107581689 >Maybe @amiara514 would have a comment as I understood he is using jena-text via Java code? @osma : Not exactly, I execute Sparql queries via java code which involve jena-text. I don't manipulate it at this level. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: Jena-text multilingual alternative implementati...
Github user amiara514 commented on the pull request:
https://github.com/apache/jena/pull/64#issuecomment-107572459
> The direct reflection of site/trunk is http://jena.staging.apache.org/
and the button should work there as well.
Humm, this link leads to the same wrong place...
Ex: the section "Configuring an Analyzer" should finish with the
explanation about specifiyng a query analyzer ("New in Jena 2.13.0 is the
optional ability to specify...") as the online version, and it's not the case.
---
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-949) DISTINCT spilling to a data bag leads to wrong answers.
[
https://issues.apache.org/jira/browse/JENA-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567408#comment-14567408
]
Andy Seaborne commented on JENA-949:
In the current implementation, the data bag accumulates incrementally in
{{isFreshSighting}}, saying "yes" or "no" to each incoming. That makes it
impossible to iterate over bag because that is over multiple items. To do that,
it needs something in {{closeSubIterator}} but that is usually called after
iteration has ceased. i.e. the design assumption in
{{QueryIterDistinctReduced}} of being able to immediately say "yes" or "no" is
getting in the way.
Here is a proposal for a change to address this.
Run in-memory (see {{QueryIterDistinctMem}}) until spilling is needed,
keeping the in-memory set of items already yielded. This is not the bag size
limit,
but it could be.
Start spilling, making no effort to iterate, sitting inside {{isFreshSighting}}
looping on
the input. Filter al incoming by in-memory set above for the items already
emitted.
Then continue iterating over the bag - the bag contains none of the first stage
items.
Issue: there are two copies: the in-memory set and the working area of the data
bag.
To just use a data net, then the implementation {{QueryIterDistinct}} needs to
be a lot smarter, switching to processing the stored distinct results. It's a
new implementation, not using the approach of {{QueryIterDistinctReduced}},
providing {{hasNextBinding}}/{{moveToNextBinding}} directly.
> DISTINCT spilling to a data bag leads to wrong answers.
> ---
>
> Key: JENA-949
> URL: https://issues.apache.org/jira/browse/JENA-949
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
>Affects Versions: Jena 3.0.0
>Reporter: Andy Seaborne
> Attachments: Jena949_1.java
>
>
> In the attached example, the same query is made twice. The second time
> {{ARQ.spillToDiskThreshold}} is set to 2L. The first results are correct.
> [email
> 2015-05-20|http://mail-archives.apache.org/mod_mbox/jena-users/201505.mbox/%3C34B3B313-EAE4-4498-875F-A9674A8B3B2D%40interition.net%3E]
> reports a possibly similar situation at scale.
> The presence of {{DISTINCT}} is the key factor.
> Output:
> {noformat}
> ---
> | g |
> ===
> | |
> | |
> | |
> | |
> | |
> | |
> | |
> | |
> | |
> | |
> ---
> ---
> | g |
> ===
> | |
> | |
> ---
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: A couple pull requests in the pending tray.
On 31/05/15 21:54, Claude Warren wrote: Andy, I did a review and the changes make sense (the structure is a holdover from a very early incarnation). I would do the merge but I don't know. ".. how to do that?" a) what id to use on github to do the merge? or do I do the merge elsewhere? b) I am not certain what actions I would take to do the merge. You are doing with to bring things into the Apache Jena repo with your Apache id. Not as a guthub person nor with their tools. There are several ways depending. 1/ If you want to include all the commits, and maybe tweak things after, then git pull https://github.com/apache/jena/pull/NN/head (caution see (3) I don't do that - I use a short form). # Schedule a close. git commit -m "This closes #NN." --allow-empty # Push to Apache. git push The "This closes..." can be in any commit message; I've shown how to do it if you just pull, make no changes, and want to have the close happen. Advantage of this route : the commits have the contributors name. 2/ If I'm picking and choosing, i.e. more than a few tweaks, I've found it easier to grab some changes and work locally. Get the diff by downloading as a file: https://github.com/apache/jena/pull/NN.diff (I have found that diff is better than patch when the PR has been modified a few times ".patch" don't see to always apply the revisions, ".diff" is OK) Apply it git apply NN.diff Work locally, commit changes. Make sure one has "This closes #NN" 3/ I have this in /.git/config -- [remote "github"] url = g...@github.com:apache/jena.git fetch = +refs/heads/*:refs/remotes/github/* -- so it's git pull github pull/NN/head Andy Claude On Fri, May 29, 2015 at 5:27 PM, Andy Seaborne wrote: Claude, Rob, I took a look at our outstanding pull requests on github. I was wondering if you have a moment to assess them. It's clearing up suggestions from ajs6f, not bug fixes nor new features. They were part of large sets of changes over several modules but ajs6f very kindly broken them up in units that reflect the module structure of Jena. Claude: "Nonfunctional cleanup in jena-querybuilder" https://github.com/apache/jena/pull/68 the bulk of this is subQuery is known to be instanceof the various cases do the if/instanceof isn't necessary. Your choice on style. Rob: "Nonfunctional cleanup in jena-jdbc" https://github.com/apache/jena/pull/62 Much of this is adjusting the throws clauses on @Override methods. I personally prefer normally to keep the throws even if not actually thrown because they are in the contract of the interface. I didn't apply similar changes elsewhere. Andy
[GitHub] jena pull request: Jena-text multilingual alternative implementati...
Github user afs commented on the pull request: https://github.com/apache/jena/pull/64#issuecomment-107519936 Thank for pointing that out. The direct reflection of `site/trunk` is http://jena.staging.apache.org/ and the button should work there as well. The website gets published explicitly and we have probably not published it as Jena3 mentions get into the content. Sorry for any confusion. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: Add (?uri ?score) to jena-text
Github user ajs6f commented on the pull request: https://github.com/apache/jena/pull/72#issuecomment-107519784 `Iter` is also a good choice because it provides access to transform-behavior as well as many other forms of iterator-processing. `Map1Iterator` is more of an "implementation" class. As the code evolves, I would expect `Iter` to last longer and be better supported. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: Add (?uri ?score) to jena-text
Github user afs commented on the pull request: https://github.com/apache/jena/pull/72#issuecomment-107516262 Re: Map1Iterator -- yes is it similar (and older). `Iter` works on any iterators, not just `ExtendedIterator`. Re: naming of search - your choice. It is alwayss difficult to choose between compatibility and creating legacy. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] jena pull request: JENA-869 Fuseki2: Can't reuse dataset name afte...
Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/66 --- 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] [Resolved] (JENA-869) Fuseki2: Can't reuse dataset name after DELETE
[
https://issues.apache.org/jira/browse/JENA-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-869.
Resolution: Fixed
Fix Version/s: (was: Fuseki 2.0.0)
Fuseki 2.3.0
> 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 (old)
>Assignee: Andy Seaborne
> Fix For: Fuseki 2.3.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
[jira] [Commented] (JENA-869) Fuseki2: Can't reuse dataset name after DELETE
[
https://issues.apache.org/jira/browse/JENA-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567332#comment-14567332
]
ASF subversion and git services commented on JENA-869:
--
Commit 52ac62d8484c255018f2309bb654bcdbf16b3644 in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=52ac62d ]
JENA-869 : Find the graph in the database based on dataset name.
This fix is based on based on PR#66.
This closes #66.
> 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 (old)
>Assignee: Andy Seaborne
> 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
> [
[jira] [Commented] (JENA-869) Fuseki2: Can't reuse dataset name after DELETE
[
https://issues.apache.org/jira/browse/JENA-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567333#comment-14567333
]
ASF GitHub Bot commented on JENA-869:
-
Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/66
> 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 (old)
>Assignee: Andy Seaborne
> 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 I
[jira] [Commented] (JENA-938) Clean up dead code
[ https://issues.apache.org/jira/browse/JENA-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567283#comment-14567283 ] ASF subversion and git services commented on JENA-938: -- Commit b2d1cf7cbe7502314760b97017ad062c17f3944f in jena's branch refs/heads/master from [~ajs6f] [ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=b2d1cf7 ] JENA-938: Nonfunctional cleanup in jena-jdbc > Clean up dead code > -- > > Key: JENA-938 > URL: https://issues.apache.org/jira/browse/JENA-938 > Project: Apache Jena > Issue Type: Task > Components: Jena >Affects Versions: Jena 3.0.0 >Reporter: A. Soroka >Priority: Minor > Labels: cleanup, jena > > This is an umbrella task to which several PRs will be attached, each > containing "clean up" for some modules in Jena. Each PR will contain only > non-controversial emendations, such as the removal of unused imports or > unthrown exceptions. Specifically disallowed are the removal of actual logic > or methods. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (JENA-938) Clean up dead code
[ https://issues.apache.org/jira/browse/JENA-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567284#comment-14567284 ] ASF GitHub Bot commented on JENA-938: - Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/62 > Clean up dead code > -- > > Key: JENA-938 > URL: https://issues.apache.org/jira/browse/JENA-938 > Project: Apache Jena > Issue Type: Task > Components: Jena >Affects Versions: Jena 3.0.0 >Reporter: A. Soroka >Priority: Minor > Labels: cleanup, jena > > This is an umbrella task to which several PRs will be attached, each > containing "clean up" for some modules in Jena. Each PR will contain only > non-controversial emendations, such as the removal of unused imports or > unthrown exceptions. Specifically disallowed are the removal of actual logic > or methods. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] jena pull request: JENA-938: Nonfunctional cleanup in jena-jdbc
Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/62 --- 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. ---
Re: Help with "apache: Big data" and "apacheCon: Core"
Yes that would be my thought as well
Rob
On 01/06/2015 13:19, "Andy Seaborne" wrote:
>Good question: I was more approaching from the LD angle. I guess "big
>data" is more specifc to the big data memes in Apache and LD isn't there
>(Elephas aside!). "core" seems more natural - does that make sense?
>
> Andy
>
>On 01/06/15 09:52, Rob Vesse wrote:
>> Would this be for Core or Big Data track?
>>
>> Rob
>>
>> On 31/05/2015 18:01, "Andy Seaborne" wrote:
>>
>>> One idea that occurs to me is a linked data (half)track with
>>> introductions to all the apache projects in the space. A specialist
>>> linked data track might not get that many people whereas the audience
>>> who might be interesting in technical-not-no-assumed-background
>>>("what's
>>> all the fuss about?") is larger.
>>>
>>> Andy
>>>
>>> (Hmm - maybe dig out+update my RDF / Tinkerpop comparison)
>>>
>>> On 28/05/15 22:26, Claude Warren wrote:
Is anyone here interested in pushing this forward. I have previously
proposed a talk covering the design and implementation of the
permissions
module.
Claude
-- Forwarded message --
From: jan i
Date: Thu, May 28, 2015 at 7:58 PM
Subject: Help with "apache: Big data" and "apacheCon: Core"
To: apachecon-disc...@apache.org
Dear PMC.
We have just announced the call for Papers for "apache Big data" and
"apacheCon: Core".
If your project would like a track (1 day == 6 presentations) or a
half
track
(3 presentations), please contact me. Building a track (or half track)
is a
good
way of securing (without guarantee) that your project is represented
in
the
events. PMCs that suggest tracks (half tracks) for "apacheCon: Core"
will
decide the content, with only an outside oversight.
We hope you will take the oppertunity and build an awesome track
representing
your projects. We are of course also open if a group of projects
builds
a
track
together.
We hope to be able to make some cross project presentations/panels. An
example is "the future of web and web applications", many people ask
if
e.g. httpd and tomcat will play a major role in the future of
internet.
We
hope
some (especially the more mature projects) will grab the idea, and
come
with suggestions.
Especially "apacheCon: Core" is open for innovation.
Looking forward to help build super events with YOUR assistance.
on behalf of the apacheCon team and LF
jan I.
>>>
>>
>>
>>
>>
>
Re: Help with "apache: Big data" and "apacheCon: Core"
Good question: I was more approaching from the LD angle. I guess "big
data" is more specifc to the big data memes in Apache and LD isn't there
(Elephas aside!). "core" seems more natural - does that make sense?
Andy
On 01/06/15 09:52, Rob Vesse wrote:
Would this be for Core or Big Data track?
Rob
On 31/05/2015 18:01, "Andy Seaborne" wrote:
One idea that occurs to me is a linked data (half)track with
introductions to all the apache projects in the space. A specialist
linked data track might not get that many people whereas the audience
who might be interesting in technical-not-no-assumed-background ("what's
all the fuss about?") is larger.
Andy
(Hmm - maybe dig out+update my RDF / Tinkerpop comparison)
On 28/05/15 22:26, Claude Warren wrote:
Is anyone here interested in pushing this forward. I have previously
proposed a talk covering the design and implementation of the
permissions
module.
Claude
-- Forwarded message --
From: jan i
Date: Thu, May 28, 2015 at 7:58 PM
Subject: Help with "apache: Big data" and "apacheCon: Core"
To: apachecon-disc...@apache.org
Dear PMC.
We have just announced the call for Papers for "apache Big data" and
"apacheCon: Core".
If your project would like a track (1 day == 6 presentations) or a half
track
(3 presentations), please contact me. Building a track (or half track)
is a
good
way of securing (without guarantee) that your project is represented in
the
events. PMCs that suggest tracks (half tracks) for "apacheCon: Core"
will
decide the content, with only an outside oversight.
We hope you will take the oppertunity and build an awesome track
representing
your projects. We are of course also open if a group of projects builds
a
track
together.
We hope to be able to make some cross project presentations/panels. An
example is "the future of web and web applications", many people ask if
e.g. httpd and tomcat will play a major role in the future of internet.
We
hope
some (especially the more mature projects) will grab the idea, and come
with suggestions.
Especially "apacheCon: Core" is open for innovation.
Looking forward to help build super events with YOUR assistance.
on behalf of the apacheCon team and LF
jan I.
Re: Help with "apache: Big data" and "apacheCon: Core"
Would this be for Core or Big Data track?
Rob
On 31/05/2015 18:01, "Andy Seaborne" wrote:
>One idea that occurs to me is a linked data (half)track with
>introductions to all the apache projects in the space. A specialist
>linked data track might not get that many people whereas the audience
>who might be interesting in technical-not-no-assumed-background ("what's
>all the fuss about?") is larger.
>
> Andy
>
>(Hmm - maybe dig out+update my RDF / Tinkerpop comparison)
>
>On 28/05/15 22:26, Claude Warren wrote:
>> Is anyone here interested in pushing this forward. I have previously
>> proposed a talk covering the design and implementation of the
>>permissions
>> module.
>>
>> Claude
>>
>>
>> -- Forwarded message --
>> From: jan i
>> Date: Thu, May 28, 2015 at 7:58 PM
>> Subject: Help with "apache: Big data" and "apacheCon: Core"
>> To: apachecon-disc...@apache.org
>>
>>
>> Dear PMC.
>>
>> We have just announced the call for Papers for "apache Big data" and
>> "apacheCon: Core".
>>
>> If your project would like a track (1 day == 6 presentations) or a half
>> track
>> (3 presentations), please contact me. Building a track (or half track)
>>is a
>> good
>> way of securing (without guarantee) that your project is represented in
>>the
>> events. PMCs that suggest tracks (half tracks) for "apacheCon: Core"
>>will
>> decide the content, with only an outside oversight.
>>
>> We hope you will take the oppertunity and build an awesome track
>> representing
>> your projects. We are of course also open if a group of projects builds
>>a
>> track
>> together.
>>
>> We hope to be able to make some cross project presentations/panels. An
>> example is "the future of web and web applications", many people ask if
>> e.g. httpd and tomcat will play a major role in the future of internet.
>>We
>> hope
>> some (especially the more mature projects) will grab the idea, and come
>> with suggestions.
>>
>> Especially "apacheCon: Core" is open for innovation.
>>
>> Looking forward to help build super events with YOUR assistance.
>>
>> on behalf of the apacheCon team and LF
>> jan I.
>>
>>
>>
>
[GitHub] jena pull request: Add (?uri ?score) to jena-text
Github user osma commented on the pull request: https://github.com/apache/jena/pull/72#issuecomment-107341239 Thanks a lot Andy for your review! I will address your points soon and push a new version. Thank you also for pointing out Iter.map(), I actually wanted something like that when coding but then I found Map1Iterator (which had been recently upgraded to support Java 8 Functions) and settled on using that. >I'm unsure whether it is better to add searchWithScore (or better name?), which returns the List form, and retain search returning List (just a Iter.map added each time): I wouldn't call it searchWithScore - potentially, TextHit could also contain other information than the node and score. searchWithHits? searchForHits? searchTextHits? I only use jena-text via SPARQL so I can't really tell whether the API breakage would be bad. Maybe @amiara514 would have a comment as I understood he is using jena-text via Java code? My opinion is slightly on the "clean up the API with Jena3, don't worry about breakage" side. --- 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. ---
