Re: TDB2 - technical background

The node table is same design but uses binary encoding of the nodes (RDF Thrift). Andy On 17/01/17 16:48, A. Soroka wrote: This is cool, Andy. Hey, if you got the bits, use 'em! :grin: Is the node table itself basically similar to TDB (obviously modulo the change to node IDs)? ---

[jira] [Created] (JENA-1281) JsonLDReader: possibility to override the @context

Andy Seaborne created JENA-1281: --- Summary: JsonLDReader: possibility to override the @context Key: JENA-1281 URL: https://issues.apache.org/jira/browse/JENA-1281 Project: Apache Jena Issue

[jira] [Updated] (JENA-1280) JoinClassifer is too cautious with EXISTS variables.

[ https://issues.apache.org/jira/browse/JENA-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne updated JENA-1280: Summary: JoinClassifer is too cautious with EXISTS variables. (was: JoinClassifer is too cautious

[GitHub] jena pull request #203: JsonLDReader: possibility to override the @context

Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/203 --- 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

[jira] [Resolved] (JENA-1281) JsonLDReader: possibility to override the @context

[ https://issues.apache.org/jira/browse/JENA-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne resolved JENA-1281. - Resolution: Done > JsonLDReader: possibility to override the @context >

[jira] [Updated] (JENA-1281) JsonLDReader: possibility to override the @context

[ https://issues.apache.org/jira/browse/JENA-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne updated JENA-1281: Description: Records PR#203. > JsonLDReader: possibility to override the @context >

Re: CMS diff: ARQ - SPARQL Algebra

Committed, thanks! --- A. Soroka The University of Virginia Library > On Jan 17, 2017, at 10:00 AM, Kim Ahlstrøm wrote: > > Clone URL (Committers only): >

[GitHub] jena issue #204: One writable graph per thread/transaction dataset

Github user ajs6f commented on the issue: https://github.com/apache/jena/pull/204 Yeah, judging by the general silence in response to my question about "Does anyone have other use cases for this kind of thing?" I'm not going to push on that I'm happy for it to be helpful to the LDP

[jira] [Commented] (JENA-1281) JsonLDReader: possibility to override the @context

[ https://issues.apache.org/jira/browse/JENA-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826324#comment-15826324 ] ASF subversion and git services commented on JENA-1281: --- Commit

Re: CMS diff: ARQ - Extending Query Execution

Corrected, thanks! --- A. Soroka The University of Virginia Library > On Jan 17, 2017, at 10:38 AM, Kim Ahlstrøm wrote: > > Clone URL (Committers only): >

Re: TDB2 - technical background

Hang on, I think I mis-wrote-- I meant the dictionary in which IDs are looked up, not the tables that hold rows of IDs. In TDB it's NodeTable vs NodeTupleTable, I mean NodeTable. It looks like NodeTable in TDB2 is pretty much the same? But NodeTupleTable is what is now using Thrift underneath?

Re: TDB2 - technical background

NodeTable holds the RDF terms. It is indexed by position. it is the dictionary interface. The one used is: https://github.com/afs/mantis/blob/master/tdb2/src/main/java/org/seaborne/tdb2/store/nodetable/NodeTableTRDF.java and there is a stack of them above this to cache and inline.

[GitHub] jena issue #204: One writable graph per thread/transaction dataset

Github user afs commented on the issue: https://github.com/apache/jena/pull/204 Possible naming approaches: 1. "Small things" being curated go into a general `jena-extras`/`jena-wip`/`jena-labs`/`jena-optional` module with the idea that that is just while they mature,

Re: TDB2 - technical background

Additional feature: TDB2 now supports xsd:doubles as inline values. Like over inline values, it does this if and only if the value fits, otherwise it uses the node table. In the case of xsd:doubles, there 62 bits to store them. xsd:doubles (as of XSD 1.1) are very similar to IEEE-754-2008

Re: TDB2 - technical background

This is cool, Andy. Hey, if you got the bits, use 'em! :grin: Is the node table itself basically similar to TDB (obviously modulo the change to node IDs)? --- A. Soroka The University of Virginia Library > On Jan 17, 2017, at 11:44 AM, Andy Seaborne wrote: > > Additional

Re: TDB2 - technical background

As someone that has been lurking on this list for a long time, I just want to come out of the woodwork and say I really appreciate this work. I look forward to using it. ~Andy On Jan 17, 2017 11:44, "Andy Seaborne" wrote: > Additional feature: > > TDB2 now supports xsd:doubles

Re: TDB2 - technical background

Ah, okay, cool, so both the dictionary and the table are using Thrift, that's nice to see because it should make it a little easier to "tinker" with the innards. Thanks for the pointer, Andy! Yeah, I'm not complaining about not having to deal with any of the complexities of representation in

[GitHub] jena issue #205: JENA-1277: don't use sorting in spatial queries, for much b...

Github user osma commented on the issue: https://github.com/apache/jena/pull/205 @ajs6f I'm not sure whether you can use ORDER BY in a case like this. It would need a SPARQL function for calculating distances between coordinates, so you could say, in effect, "order by distance from

[jira] [Commented] (JENA-1277) Spatial Queries Very Slow For Large Databases

[ https://issues.apache.org/jira/browse/JENA-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15825969#comment-15825969 ] ASF GitHub Bot commented on JENA-1277: -- Github user osma commented on the issue:

CMS diff: ARQ - SPARQL Algebra

Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://jena.apache.org/documentation%2Fquery%2Falgebra.mdtext Kim Ahlstrøm Index: trunk/content/documentation/query/algebra.mdtext === ---

CMS diff: ARQ - Extending Query Execution

Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://jena.apache.org/documentation%2Fquery%2Farq-query-eval.mdtext Kim Ahlstrøm Index: trunk/content/documentation/query/arq-query-eval.mdtext

[GitHub] jena issue #205: JENA-1277: don't use sorting in spatial queries, for much b...

Github user ajs6f commented on the issue: https://github.com/apache/jena/pull/205 @osma Yeah, that's what I meant tho'-- use a calculation (via `BIND`, I guess?) of the distance (and we have [√ available to use](https://jena.apache.org/documentation/query/library-function.html))

[GitHub] jena issue #205: JENA-1277: don't use sorting in spatial queries, for much b...

Github user osma commented on the issue: https://github.com/apache/jena/pull/205 @ajs6f It takes [a bit more](http://www.movable-type.co.uk/scripts/latlong.html) than just sqrt() to calculate great-circle distances between coordinates even within the same coordinate system, e.g.

[jira] [Commented] (JENA-1277) Spatial Queries Very Slow For Large Databases

[ https://issues.apache.org/jira/browse/JENA-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826124#comment-15826124 ] ASF GitHub Bot commented on JENA-1277: -- Github user osma commented on the issue:

[GitHub] jena issue #205: JENA-1277: don't use sorting in spatial queries, for much b...

Github user ajs6f commented on the issue: https://github.com/apache/jena/pull/205 Sure, so my claims are 1) this is a good PR :) and 2) if we want to offer the kind of functionality that you are removing, that's cool, but we should do it in some appropriate, public, maintainable way

[jira] [Commented] (JENA-1277) Spatial Queries Very Slow For Large Databases

[ https://issues.apache.org/jira/browse/JENA-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826126#comment-15826126 ] ASF GitHub Bot commented on JENA-1277: -- Github user ajs6f commented on the issue: