Re: [jira] [Commented] (JENA-1499) The TIM dataset retains a memory of named graphs after deleting all quads.

This looks like a prime candidate for a contract test (as soon as we agree on what the action should be) Claude On Wed, Mar 7, 2018 at 4:26 PM, A. Soroka (JIRA) wrote: > > [ https://issues.apache.org/jira/browse/JENA-1499?page= >

Re: XMLChar.isNameStart error?

ause most of the ecosystem has not > adopted XML 1.1 yet > > Rob > > On 14/02/2018, 09:04, "Claude Warren" <cla...@xenei.com> wrote: > > The issue is that predicate namespaces are parsed with XMLChar. So if > I > have one that is correctly fo

Re: XMLChar.isNameStart error?

, 2018 at 6:50 PM, Andy Seaborne <a...@apache.org> wrote: > Maybe SplitIRI will help? > > It does Turtle splitting as well as XML. > > Andy > > > On 13/02/18 17:39, Claude Warren wrote: > >> It is used in org.apache.jena.rdf.model.impl.Util namespace splitt

Re: XMLChar.isNameStart error?

It is used in org.apache.jena.rdf.model.impl.Util namespace splitting code. On Tue, Feb 13, 2018 at 4:44 PM, Andy Seaborne <a...@apache.org> wrote: > Where is XMLChar.isNameStart being used? > > > On 13/02/18 13:10, Claude Warren wrote: > >> Is there a reason that Jen

XMLChar.isNameStart error?

Is there a reason that Jena does not support the full range of XML name start characters? see https://www.w3.org/TR/xml/#NT-NameStartChar I wrote a quick test and found that there were a number of characters that Jena does not support. Miscategorization appears to start at 0x132. There are

[jira] [Resolved] (JENA-1457) Graph contract tests do not properly support transactions

[ https://issues.apache.org/jira/browse/JENA-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Warren resolved JENA-1457. - Resolution: Fixed Fix Version/s: Jena 3.7.0 > Graph contract tests do not properly supp

merging pull requests

Greetings, I was looking at the git hub repository online and did not see a way to merge the pull request from the web. Is this normal (i.e. we always merge on local machine and push) or do I just not have permissions, or am I looking at the wrong place? thx, Claude -- I like: Like Like - The

Re: Welcome Chris!

Welcome Chris. Always nice to have another member of the team. Claude On Wed, Jan 31, 2018 at 11:40 PM, Bruno P. Kinoshita < brunodepau...@yahoo.com.br.invalid> wrote: > Welcome aboard! > > Bruno > > > > > > > From: Andy Seaborne > To:

[jira] [Assigned] (JENA-1457) Graph contract tests do not properly support transactions

[ https://issues.apache.org/jira/browse/JENA-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Warren reassigned JENA-1457: --- Assignee: Claude Warren > Graph contract tests do not properly support transacti

RDFConnection fetch() issue?

I am working with an RDFConnection to a Fuseki server. The server is set up as DatasetGraph serverdsg = DatasetGraphFactory.createTxnMem(); FusekiServer server = FusekiServer.make( 3030, "/ds", serverdsg ); server.start(); I have called ARQ.enableBlankNodeResultLabels(true); It seems

[jira] [Created] (JENA-1469) GraphTxnTDB does not handle abort() properly

Claude Warren created JENA-1469: --- Summary: GraphTxnTDB does not handle abort() properly Key: JENA-1469 URL: https://issues.apache.org/jira/browse/JENA-1469 Project: Apache Jena Issue Type: Bug

Re: TDB Graph usage question

gt; On 30/12/17 00:09, Claude Warren wrote: > >> When I tried to add a transaction on dest there was an error with a >> transaction already being active. >> > > This is what I mean by details - you are now saying that graphs are from > the same dataset. Tha

Re: TDB Graph usage question

laim. > > Too many details missing to say much else but I don't see any txn on dest. > > Andy > > > On 29/12/17 13:10, Claude Warren wrote: > >> fair enough. >> >> I created a ContractTest for GraphTxnTDB and discovered a lot of issues >> with tra

[jira] [Commented] (JENA-1457) Graph contract tests do not properly support transactions

[ https://issues.apache.org/jira/browse/JENA-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16306603#comment-16306603 ] Claude Warren commented on JENA-1457: - the txnBegin and other methods determine if the graph supports

Re: [jira] [Commented] (JENA-1457) Graph contract tests do not properly support transactions

ct: Apache Jena > > Issue Type: Bug > > Components: Core > >Reporter: Claude Warren > >Priority: Minor > > > > The Contract test for Graphs do not properly support transactions. > Specifically, if the graph supports tr

Re: TDB Graph usage question

emoteTestRunner.java:192) Is this a bug, or a known limitation of GraphTxnTDB? Claude On Fri, Dec 29, 2017 at 11:14 AM, Andy Seaborne <a...@apache.org> wrote: > Try it :-) > > Then try running it twice in a JVM. > > And then try TDB2 vs TDB1 vs TIM. > >Andy > >

[jira] [Created] (JENA-1457) Graph contract tests do not properly support transactions

Claude Warren created JENA-1457: --- Summary: Graph contract tests do not properly support transactions Key: JENA-1457 URL: https://issues.apache.org/jira/browse/JENA-1457 Project: Apache Jena

TDB Graph usage question

Would the following code snippit work Graph g = // a TDB graph instance if (g.getTransactionHandler().transactionsSupported()) { Graph initial = graphWith( GraphFactory.createGraphMem(), "initial hasValue 42; also hasURI hello"); Graph

Re: RDF Diff/patch

to see especially the handling of blank nodes > cycles and other structures. > > > > Please don't call it "RDF Patch" or a names similar to that - that term > is already used. > > > >Andy > > > > On 26/12/17 18:17, Claude Warren wrote: > >> Ho

[jira] [Resolved] (JENA-1456) QueryBuilder needs a stand alone WhereClause instance

[ https://issues.apache.org/jira/browse/JENA-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Warren resolved JENA-1456. - Resolution: Fixed Fix Version/s: Jena 3.7.0 WhereBuilder created. Has all the functions

[jira] [Resolved] (JENA-1455) QueryBuilder allows Node_Variable instances into QueryTripleIterator

[ https://issues.apache.org/jira/browse/JENA-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Warren resolved JENA-1455. - Resolution: Fixed Fix Version/s: Jena 3.7.0 Added additional checks and processing of quads

[jira] [Created] (JENA-1456) QueryBuilder needs a stand alone WhereClause instance

Claude Warren created JENA-1456: --- Summary: QueryBuilder needs a stand alone WhereClause instance Key: JENA-1456 URL: https://issues.apache.org/jira/browse/JENA-1456 Project: Apache Jena Issue

RDF Diff/patch

Howdy, I am working on a tool that can create UpdateRequests that will convert one Dataset into another. The basic idea is to extract the quads sorted by (g,s,p,o) and then perform a diff on the lists (like a text diff but each quad is a "line"). The result is that I can create statements to

Re: QueryTripleIterator not accept Node_Variables

; > On 26/12/17 14:24, Claude Warren wrote: > >> if this method does not have to account for null node values then >> >> node.isVariable() would suffice. >> >> On Tue, Dec 26, 2017 at 1:46 PM, Claude Warren <cla...@xenei.com> wrote: >> >>

Re: QueryTripleIterator not accept Node_Variables

if this method does not have to account for null node values then node.isVariable() would suffice. On Tue, Dec 26, 2017 at 1:46 PM, Claude Warren <cla...@xenei.com> wrote: > QueryTripleIterator at line 87 calls Var.isVar(node) which throws an > exception if the node is a N

QueryTripleIterator not accept Node_Variables

QueryTripleIterator at line 87 calls Var.isVar(node) which throws an exception if the node is a Node_Variable. But based code following line 87 I think that Node_Variable should be accepted. {noformat} private static Node substitute(Node node, Binding binding) { if (

Round Trip blank values and alternatives.

Howdy, I recently asked a question about consistent blank id values in SPARQL queries and Andy provided a patch that solves the problem for query (provided the server consistently calls the blank node by the same ID across queries). This is a follow on to that with a slightly different twist.

Re: consistent blank id values from RDFConnection

serializer do blank node scoping by default. >>> >>> That's why the blank node labels are short like b0, b1, >>> >>> It would be >>> >>> { "type": "bnode" , "value": "c46a7fb56a6126a3d31a1250510b838f" } &

Re: consistent blank id values from RDFConnection

quot;c46a7fb56a6126a3d31a1250510b838f" } >> >> if emitting blank node labels (that's a real example). >> >> Parser-generated blank node ids are UUID-related. >> >> The JSON writer has support via the system-wide context setting ... which >> is useless be

Re: consistent blank id values from RDFConnection

t; by system id. There is a request for examples on > https://afs.github.io/rdf-delta. Caching is one of several uses case for > the system and one that works. > > On 17/12/17 17:47, Claude Warren wrote: > >> My requirement centres around a caching graph. >> >> For my requirements I

Re: Jena-1427 - nextOptional()

ight we evolve the current API > without method bloat? > > Andy > > > On 14/12/17 17:46, Claude Warren wrote: > >> I was expecting that with the discovery that optional throws a null >> pointer >> exception when the retrieved value is null would be enough

Re: consistent blank id values from RDFConnection

t; We could thread such a mapping choice all the way through the call stack, > but that seems a bit difficult to me. Maybe we could introduce a Context > setting for this purpose? > > ajs6f > > > On Dec 17, 2017, at 9:28 AM, Claude Warren <cla...@

Re: consistent blank id values from RDFConnection

g for this purpose? >> > > They already exist! > > ajs6f >> >> On Dec 17, 2017, at 9:28 AM, Claude Warren <cla...@xenei.com> wrote: >>> >>> Greetings, >>> >>> I am looking at org.apache.jena.sparql.resultset.JSONInput and th

consistent blank id values from RDFConnection

Greetings, I am looking at org.apache.jena.sparql.resultset.JSONInput and the way in which it parses blank nodes. I have a requirement for an application such that the same blank node returned on multiple queries returns the same blank node id. I have verified that Fuseki does this (given that

Re: Jena-1427 - nextOptional()

gt; nextOptional added for release 3.6.0. > > Proposal: close this JIRA for now, see how nextOptional works out and > revisit orElse* based on experience. > > ajs6f A. Soroka added a comment - 1 week ago > > +1 > ]] > > Adding nextOptional, and no others, is in

Jena-1427 - nextOptional()

Perhaps i wasn't paying close enough attention but i didn't think adding optional and other streaming methods had been agreed. In fact i thought quite the oposite. If i am wrong please forgive the noise. If i am correct shouldn't 1427 be removed from the release candidate? Claude

Re: Build failed in Jenkins: Jena_Development_Deploy #1465

Can we create a "starter" that uses a countdown latch to wait until the back end starts? Not sure if this is possible but thought I would ask. Claude On Tue, Dec 12, 2017 at 11:37 AM, Andy Seaborne wrote: > It's a bit of a nuisance. It's been happening every so often. > > We

Re: [GitHub] jena pull request #314: JENA-1430

Q: What about when the tests are used by subclasses in a different package. The test files would then need to be loaded from the class path. I ran into this issue trying to run tests on graph implementations before. However, it my not apply in this specific case with assemblers. So I am asking,

Re: [jira] [Resolved] (JENA-1427) Add nextOrElse() method in ExtendedIterator

Is optional.get() == null an expected or acceptable solution? I supose it might be in this case. However i am beginning to believe that streaming operations should not be applied to iterators and rather that methods to convert the iterator to a stream should be sufficient. And i believe that

Re: [jira] [Commented] (JENA-1427) Add nextOrElse() method in ExtendedIterator

my reading of this is that nextOptional will return null at the end of the iteration and that this is indistinguishable from a null in the iteration unless hasNext() is called. but calling hasNext() after a null only tells you if the next item is present not if the last item was present, thus a

IteratorIterator deprecated

I know that the IteratorIterator class was deprecated some time ago in favor of WrappedIterator.createIteratorIterator(). However they have different performance characteristics. the original IteratorIterator, did not call iter.next() on the base iterator until it was needed.

[jira] [Resolved] (JENA-1442) QueryBuilder ValuesClause.clearValues does not return the builder

[ https://issues.apache.org/jira/browse/JENA-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Warren resolved JENA-1442. - Resolution: Fixed Fix Version/s: Jena 3.6.0 Changed return value from void to builder type

[jira] [Created] (JENA-1442) QueryBuilder ValuesClause.clearValues does not return the builder

Claude Warren created JENA-1442: --- Summary: QueryBuilder ValuesClause.clearValues does not return the builder Key: JENA-1442 URL: https://issues.apache.org/jira/browse/JENA-1442 Project: Apache Jena

[jira] [Resolved] (JENA-1433) Query Builder does not have a short hand method to add group clause with single triple

[ https://issues.apache.org/jira/browse/JENA-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Warren resolved JENA-1433. - Resolution: Resolved Fix Version/s: Jena 3.6.0 > Query Builder does not have a short h

[jira] [Closed] (JENA-1432) Query Builder does not have a mechanism to put value var block in the where clause

[ https://issues.apache.org/jira/browse/JENA-1432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Warren closed JENA-1432. --- Resolution: Resolved Fix Version/s: Jena 3.6.0 > Query Builder does not have a mechanism to

Re: [jira] [Commented] (JENA-1432) Query Builder does not have a mechanism to put value var block in the where clause

- >>> -- >>> >>> Key: JENA-1432 >>> URL: https://issues.apache.org/jira/browse/JENA-1432 >>> Project: Apache Jena >>> Issue Type: Improvement >>> Components: QueryBuilder >>> Reporter: Claude Warren >>> Assignee: Claude Warren >>> Priority: Minor >>> >>> >> >> >> >> -- >> This message was sent by Atlassian JIRA >> (v6.4.14#64029) >> >>

[jira] [Created] (JENA-1436) RDFConnection does not implement Closable interface

Claude Warren created JENA-1436: --- Summary: RDFConnection does not implement Closable interface Key: JENA-1436 URL: https://issues.apache.org/jira/browse/JENA-1436 Project: Apache Jena Issue

Re: ElementData.equalTo problem?

with blank node isomorphism considered. > > A reparsed query string has new blank nodes. > > So for two query strings to be equal, tested by parsing (same AST), it > needs to have blank node isomorphism. > > Andy > > > On 23/11/17 17:55, Claude Warren wrote: > &

Re: ElementData.equalTo problem?

equalTo is used in the isIsomorphicWith(Model g) method. So I guess the question becomes are the two element data objects equivalent for purposes of isomorphic comparison? Claude On Thu, Nov 23, 2017 at 5:27 PM, Claude Warren <cla...@xenei.com> wrote: > Andy, > > Not "

Re: ElementData.equalTo problem?

Andy, Not "equals" but "equalTo". Does your point still hold for equalTo? Claude On Thu, Nov 23, 2017 at 10:18 AM, Andy Seaborne <a...@apache.org> wrote: > > > On 22/11/17 21:27, Claude Warren wrote: > >> I think equalTo for ElementData is no

[jira] [Created] (JENA-1433) Query Builder does not have a short hand method to add group clause with single triple

Claude Warren created JENA-1433: --- Summary: Query Builder does not have a short hand method to add group clause with single triple Key: JENA-1433 URL: https://issues.apache.org/jira/browse/JENA-1433

[jira] [Updated] (JENA-1432) Query Builder does not have a mechanism to put value var block in the where clause

[ https://issues.apache.org/jira/browse/JENA-1432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Warren updated JENA-1432: Issue Type: Improvement (was: Bug) > Query Builder does not have a mechanism to put value var bl

[jira] [Updated] (JENA-1432) Query Builder does not have a mechanism to put value var block in the where clause

[ https://issues.apache.org/jira/browse/JENA-1432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Warren updated JENA-1432: Summary: Query Builder does not have a mechanism to put value var block in the where clause

[jira] [Assigned] (JENA-1432) Query Builder does not have a mechanism to put values in

[ https://issues.apache.org/jira/browse/JENA-1432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Warren reassigned JENA-1432: --- Assignee: Claude Warren Priority: Minor (was: Major) Component/s: QueryBuilder

[jira] [Created] (JENA-1432) Query Builder does not have a mechanism to put values in

Claude Warren created JENA-1432: --- Summary: Query Builder does not have a mechanism to put values in Key: JENA-1432 URL: https://issues.apache.org/jira/browse/JENA-1432 Project: Apache Jena

ElementData.equalTo problem?

I think equalTo for ElementData is not correct. Given 2 ElementData instances ElementData 1: {noformat} VALUES ( ?x ?v ) { ( "three" ) ( "four" ) } {noformat} ElementData 2: {noformat} VALUES ( ?v ?x ) { ( "three" ) ( "four" ) } {noformat} shouldn't the equalTo() method return

Re: mapping URIs

Another use case is where an endpoint is known to have moved. So that if the user attempts to resolve the data they are correctly redirected to the new location. On Wed, Nov 22, 2017 at 5:26 PM, Claude Warren <cla...@xenei.com> wrote: > actually, I want the urn:foo:bar: prefixed URL

Re: mapping URIs

ns on the way from the backend to Fuseki? > > ajs6f > > > On Nov 22, 2017, at 12:13 PM, Claude Warren <cla...@xenei.com> wrote: > > > > I have a case where data are generated in a backend system that is not > > publicly accessible and has no idea where the data are g

mapping URIs

I have a case where data are generated in a backend system that is not publicly accessible and has no idea where the data are going to be served from. The backend system generates URNs like "" What I think I want to do is on the fuseki server be able to configure "urn:foo:bar" as a place holder

[jira] [Resolved] (JENA-1428) NPE in Query Builder

[ https://issues.apache.org/jira/browse/JENA-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Warren resolved JENA-1428. - Resolution: Fixed Fix Version/s: Jena 3.6.0 Fixed AbstractRewriter to accept null parameter

[jira] [Commented] (JENA-1428) NPE in Query Builder

[ https://issues.apache.org/jira/browse/JENA-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16258138#comment-16258138 ] Claude Warren commented on JENA-1428: - workaround change: Expr x = new NodeValueInteger(1

[jira] [Commented] (JENA-1428) NPE in Query Builder

[ https://issues.apache.org/jira/browse/JENA-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16258119#comment-16258119 ] Claude Warren commented on JENA-1428: - Issue is that NodeValueRewriter calls getNode() when it should

[jira] [Created] (JENA-1428) NPE in Query Builder

Claude Warren created JENA-1428: --- Summary: NPE in Query Builder Key: JENA-1428 URL: https://issues.apache.org/jira/browse/JENA-1428 Project: Apache Jena Issue Type: Bug Components

Re: Immutability

One more note: I have an project where we are using in memory Models as the storage for object data (i.e. all/most instance variables are stored in the model). In some cases we want to lock the model so that no further changes can occur (specifically when we pass the model through a listener

Re: Immutability

In most cases I prefer immutable interfaces. However, immutable interfaces pose an interesting problem for contract testing and for the permissions implementation. In contract testing you get have a producer to create instances of an interface and tests you run against it. However, since you

Re: Java 9 branch? (Was: Release Jena 3.5.0?)

rom the ASF parent seems > to me like extra work for little benefit. > > Unless there is an immediate need? > > Andy > > > On 19/10/17 08:19, Claude Warren wrote: > >> Did we get a Java 9 branch started? Seems like most of the issues are >> around tooling no

Java 9 branch? (Was: Release Jena 3.5.0?)

Did we get a Java 9 branch started? Seems like most of the issues are around tooling not functionality of the product. If this is the case I would expect the differences between the java9 branch and the master to be contained in the pom.xml files. On Wed, Oct 18, 2017 at 2:20 AM, Andy Seaborne

Re: Release Jena 3.5.0?

The contract test changes cover edge cases that Jena doesn't trip over. Updating should not impact the build. I'd say go ahead. On Tue, Oct 17, 2017 at 2:56 PM, wrote: > Claude-- > > I see some updates available for the contract test machinery: > >

Re: Jena over Cassandra?

obviously >>>>> nontrivial in our situation, where we don't know the potential queries. >>>>> Have you looked at an indexing solution such as was used by CumulusRDF >>>>> [4]? >>>>> >>>> >> (single graph example) >> >

Re: Jena over Cassandra?

actually, looking at the code it is a datsset graph that the cassandra code is built on. On Mon, Sep 4, 2017 at 5:17 PM, Claude Warren <cla...@xenei.com> wrote: > The jena-on-cassandra solution is quite simple. it is an implementation > of the graph layer so it doesn't do the jo

Re: Jena over Cassandra?

are you looking to use jena-on-cassandra or do you have ideas? what leads you to ask about it? On Sat, Sep 2, 2017 at 1:21 PM, wrote: > Hey, Claude-- > > Just curious as to where https://github.com/Claudenw/jena-on-cassandra > has ended up. Is that still work-in-progress? >

Re: Jena over Cassandra?

Well, it is a minimal implementation of the graph store on Casandra. Nothing in the way of query optimization or the like, but it should be functional. Since Cassandra does not do "joins" I am not certain that there is much more that could be done. It might make more sense to implement a store

transactions

Is there a quick method to determine if transactions are supported by a model implementation? -- I like: Like Like - The likeliest place on the web LinkedIn: http://www.linkedin.com/in/claudewarren

Re: Java 9

; maven-source-plugin 3.0.0 > maven-surefire-plugin . 2.19.1 > > > > > On 20/08/17 19:29, Claude Warren wrote: > >> Andy, >> >> Is there a branch for the java 9 work? it looks like th

Re: Java 9

iately into plugin problems. > > What upgrades did you disable and which upgrade to get anything to > minimally compile? > > Andy > > On 04/06/17 13:43, Claude Warren wrote: > >> I was trying to get a PR for the java9 changes but am having significant >> probl

Re: Release 3.4.0?

+1 thx Andy On Sat, Jul 8, 2017 at 6:16 AM, Bruno P. Kinoshita < brunodepau...@yahoo.com.br.invalid> wrote: > I think it's a good idea to have a release now. The number of changes > looks OK, and might be easy to work on any eventual issue raised due to the > changes on this release. > > As for

path statements in queries

I know that the SPARQL recommendation states that path elements must be URIs (https://www.w3.org/TR/sparql11-property-paths/#id41857) but sine the path may be expanded as noted in the recommendation so that {noformat} { ?x foaf:mbox . ?x

Re: Unexpected difference in query results

After further investigation the issue is in the query builder and how it handles "_:b0" while createing nodes. I'll dig further to but there is no issue with fuseki or RDFConnection. On Mon, Jun 26, 2017 at 5:33 PM, Claude Warren <cla...@xenei.com> wrote: > Fuseki 2.5.0 >

Unexpected difference in query results

Fuseki 2.5.0 Jena 3.3.0 I have a graph and a query. I expect the query to return 1 value from the graph. I get 2 different results. If I run the query locally either directly on the model using QueryExecutionFactory.create(query, model) or via RDFConnection (local version) connection.query(

[jira] [Resolved] (JENA-1365) QueryBuilder can build an invalid union-of-one query.

[ https://issues.apache.org/jira/browse/JENA-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Warren resolved JENA-1365. - Resolution: Fixed Fix Version/s: Jena 3.4.0 Updates completed and tested > QueryBuil

[jira] [Commented] (JENA-1365) QueryBuilder can build an invalid union-of-one query.

[ https://issues.apache.org/jira/browse/JENA-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16062050#comment-16062050 ] Claude Warren commented on JENA-1365: - The tests work with the change to FormatterElement and I

[jira] [Commented] (JENA-1365) QueryBuilder can build an invalid union-of-one query.

[ https://issues.apache.org/jira/browse/JENA-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061878#comment-16061878 ] Claude Warren commented on JENA-1365: - Andy mentions that the FormatterElement method for ElementUnion

Re: org.apache.jena.sparql.util.Iso Question

Seaborne <a...@apache.org> wrote: > > > On 23/06/17 22:16, Andy Seaborne wrote: > >> >> >> On 23/06/17 22:11, Claude Warren wrote: >> >>> {noformat} >>> public static boolean nodeIso(Node n1, Node n2, NodeIsomorphis

org.apache.jena.sparql.util.Iso Question

{noformat} public static boolean nodeIso(Node n1, Node n2, NodeIsomorphismMap isoMap) { if ( isoMap != null ) { if ( n1.isBlank() && n2.isBlank() ) return isoMap.makeIsomorphic(n1, n2) ; if ( Var.isBlankNodeVar(n1) && Var.isBlankNodeVar(n2) )

[jira] [Created] (JENA-1365) QueryBuilder can build an invalid union-of-one query.

Claude Warren created JENA-1365: --- Summary: QueryBuilder can build an invalid union-of-one query. Key: JENA-1365 URL: https://issues.apache.org/jira/browse/JENA-1365 Project: Apache Jena Issue

Re: querybuilder - txt based tests

Andy, The contract is "equivalent to", so I don't expect it to be exactly like a parser and not exactly like a string either. I'll have to think about this again. I reviewed it in my mind recently when I was looking at the update builder stuff. The problem with doing parse( builder.toString()

snapshot build failed

The last snapshot build failed and I can not log in to the jenkins from work. Would someone kick off the build please. I think the jenkins setup is correct it just hasn't run since it was last modified. Claude -- I like: Like Like - The likeliest place on the web

Re: Build failed in Jenkins: Jena_Development_Test #2674

t; and I fixed it for the development build by setting it to maven 3.3.3, >> not "maven 3 latest". >> >> Andy >> >> On 04/06/17 14:43, aj...@apache.org wrote: >> >>> I'll take it up with INFRA tomorrow unless someone beats me to it

Re: Java 9

he modules vote was lost: 10 for, 13 against. > > https://www.jcp.org/en/jsr/results?id=5959_mc_uid=2651742 > 7955014876736746_mc_sid_5020=1494449092 > > What that means for Java9 timescale is anyone's guess. > > Andy > > On 15/02/17 19:07, Claude Warr

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

[ https://issues.apache.org/jira/browse/JENA-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Warren resolved JENA-1352. - Resolution: Implemented Fix Version/s: Jena 3.4.0 > QueryBuilder should prov

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

[ https://issues.apache.org/jira/browse/JENA-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Warren closed JENA-1358. --- Resolution: Not A Problem Issue was with data in initial table. > UpdateRequest does not prope

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

[ https://issues.apache.org/jira/browse/JENA-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Warren updated JENA-1358: Attachment: Example10.java Test code that executes the example 10 from the w3c SPARQL 1.1

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

Claude Warren created JENA-1358: --- Summary: UpdateRequest does not properly execute w3c update Example 10 Key: JENA-1358 URL: https://issues.apache.org/jira/browse/JENA-1358 Project: Apache Jena

Re: Sparql Insert Data bug?

I didn't think so but the examples would imply that it is. Thx. On Sat, Jun 3, 2017 at 4:37 PM, Andy Seaborne <a...@apache.org> wrote: > Prefixes are not part of SPARQL Update. > > > On 03/06/17 14:36, Claude Warren wrote: > >> I am starting with the second example i

Sparql Insert Data bug?

I am starting with the second example in the SPARQL recommendation: https://www.w3.org/TR/sparql11-update/#example_2 I construct a model with the "data before" data. I construct an UpdateRequest as per the snippet I execute UpdateAction.execute( updateRequest, model); should the model

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

Claude Warren created JENA-1352: --- Summary: QueryBuilder should provide UpdateBuilder Key: JENA-1352 URL: https://issues.apache.org/jira/browse/JENA-1352 Project: Apache Jena Issue Type

[jira] [Resolved] (JENA-1351) QueryBuilder does not support DescribeQuery

[ https://issues.apache.org/jira/browse/JENA-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Warren resolved JENA-1351. - Resolution: Fixed Fix Version/s: Jena 3.4.0 added DescribeBuilder class and test code

[jira] [Created] (JENA-1351) QueryBuilder does not support DescribeQuery

Claude Warren created JENA-1351: --- Summary: QueryBuilder does not support DescribeQuery Key: JENA-1351 URL: https://issues.apache.org/jira/browse/JENA-1351 Project: Apache Jena Issue Type: Bug

[jira] [Resolved] (JENA-1343) QueryBuilder.addFilter() does not accept anything but string

[ https://issues.apache.org/jira/browse/JENA-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Warren resolved JENA-1343. - Resolution: Fixed Fix Version/s: Jena 3.4.0 use getExprFactory() to get an expression

[jira] [Resolved] (JENA-1348) E_DyncmicFunction 2-arg constructor fails

[ https://issues.apache.org/jira/browse/JENA-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Warren resolved JENA-1348. - Resolution: Fixed Assignee: Claude Warren Fix Version/s: Jena 3.4.0 Fixed as per

<    1   2   3   4   5   6   7   8   9   10   >