[GitHub] [jena] afs opened a new pull request #670: JENA-1813: GRAPH and sub-query

[GitBox]

afs opened a new pull request #670: JENA-1813: GRAPH and sub-query
URL: https://github.com/apache/jena/pull/670
 
 
   See ticket [JENA-1813](https://issues.apache.org/jira/browse/JENA-1813).


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: Towards Jena 3.14.0

[ajs6f]

+1. A smaller bug is better than a bigger bug.

ajs6f


On Sun, Jan 12, 2020, 12:51 PM Andy Seaborne  wrote:

> One of those releases ...
>
> JENA-1813 came in and it's a bug.
>
> The proper, comprehensive fix is quite extensive, although it will
> enable optimization in cases currently not handled. That is not
> something I want to rush just before a release.
>
> There is a pragmatic fix suggested in Shawn's report. It fixes the
> reported case. It (probably) isn't complete but more importantly it
> shows there is a better design that does not avoid certain cases that
> happen at the moment
>
> So my proposal is immediate fix for JENA-1813, release 3.14.0
> and fork off JENA-1815 for redesign/rework for a later release.
>
> No query that already works properly in 3.13.1 is affected. Some queries
> that don't work will now work.
>
>  Andy
>
> On 07/01/2020 13:57, Aaron Coburn wrote:
> > I will have time to review any release candidates between now and Jan 20.
> >
> > Cheers,
> > Aaron
> >
> > On Tue, 7 Jan 2020 at 08:37, Andy Seaborne  wrote:
> >
> >> It's coming up to time to look at Jena 3.14.0. v3.13.1 was 2019-10-11.
> >>
> >> I have time between now and January 19th to do a release or to work with
> >> anyone who is interested in performing a release. January 20th and after
> >> is likely to be busy due to new employment.
> >>
> >>   Andy
> >>
> >> == Contributions and notable JIRA
> >>
> >> Pavel Mikhailovskii:
> >> JENA-1787: SHACL improvement
> >> JENA-1786: DatasetGraphMonitor exposes unwrapped graphs
> >> JENA-1785: TDB2 bug fix
> >> JENA-1784: CacheSimple doesn't check keys for equality
> >>
> >> Ken Treimann:
> >> JENA-1781: Thrift upgrade to 0.13.0 for a CVE.
> >>
> >> Georg Schmidt-Dumont:
> >> JENA-1796: Add missing DV for XSD DateTimeStamp data type
> >>
> >> Adrian Wilke:
> >> JENA-1792: DCat vocabulary update to DCat2
> >>
> >>
> >> JENA-1779: Update to Jackson 2.10.1
> >>
> >> 2.10 has a design change to remove the 2.9.x attack point.
> >> Hopefully, moving to 2.10 will mean the end of recurring CVE's for
> Jackson.
> >>
> >> == JIRA
> >>
> >> https://s.apache.org/jena-3.14.0-jira
> >>
> >> 36 currently.
> >>
> >>
> >
>

Re: Towards Jena 3.14.0

[Andy Seaborne]

One of those releases ...

JENA-1813 came in and it's a bug.

The proper, comprehensive fix is quite extensive, although it will 
enable optimization in cases currently not handled. That is not 
something I want to rush just before a release.


There is a pragmatic fix suggested in Shawn's report. It fixes the 
reported case. It (probably) isn't complete but more importantly it 
shows there is a better design that does not avoid certain cases that 
happen at the moment


So my proposal is immediate fix for JENA-1813, release 3.14.0
and fork off JENA-1815 for redesign/rework for a later release.

No query that already works properly in 3.13.1 is affected. Some queries 
that don't work will now work.


Andy

On 07/01/2020 13:57, Aaron Coburn wrote:

I will have time to review any release candidates between now and Jan 20.

Cheers,
Aaron

On Tue, 7 Jan 2020 at 08:37, Andy Seaborne  wrote:


It's coming up to time to look at Jena 3.14.0. v3.13.1 was 2019-10-11.

I have time between now and January 19th to do a release or to work with
anyone who is interested in performing a release. January 20th and after
is likely to be busy due to new employment.

  Andy

== Contributions and notable JIRA

Pavel Mikhailovskii:
JENA-1787: SHACL improvement
JENA-1786: DatasetGraphMonitor exposes unwrapped graphs
JENA-1785: TDB2 bug fix
JENA-1784: CacheSimple doesn't check keys for equality

Ken Treimann:
JENA-1781: Thrift upgrade to 0.13.0 for a CVE.

Georg Schmidt-Dumont:
JENA-1796: Add missing DV for XSD DateTimeStamp data type

Adrian Wilke:
JENA-1792: DCat vocabulary update to DCat2


JENA-1779: Update to Jackson 2.10.1

2.10 has a design change to remove the 2.9.x attack point.
Hopefully, moving to 2.10 will mean the end of recurring CVE's for Jackson.

== JIRA

https://s.apache.org/jena-3.14.0-jira

36 currently.

[jira] [Created] (JENA-1815) Join strategy/VarFinder: deal with assigned variables (AS) differently to pattern defined variables.

[Andy Seaborne (Jira)]

Andy Seaborne created JENA-1815:
---

 Summary: Join strategy/VarFinder: deal with assigned variables 
(AS) differently to pattern defined variables.
 Key: JENA-1815
 URL: https://issues.apache.org/jira/browse/JENA-1815
 Project: Apache Jena
  Issue Type: Improvement
Affects Versions: Jena 3.13.1, Jena 3.14.0
Reporter: Andy Seaborne
Assignee: Andy Seaborne


The {{VarFinder}} treats assigned variables ({{AS ?var}}) in the same way as 
variables set by pattern. In the sense that these two forms both set variables, 
this is correct but "AS variables" can not be substituted for. At the moment 
join classification says that a join is not "linear" (i.e. {{sequence}} can be 
used) when assignment is encountered.

By classifying variables into substituable and non-substitutable, it should be 
possible to do a better job of optimization choices of the join strategy.

This is motivated by JENA-1813.




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: documentation update

[Claude Warren]

I checked with Infra last night and they found an issue with the server.
It should be up and running now.

On Sat, Jan 11, 2020 at 11:52 PM Claude Warren  wrote:

> I tried to follow
> https://cwiki.apache.org/confluence/display/JENA/ProcessWebSite but I
> could not get to https://cms.apache.org/jena/publish [500 error].  I get
> the same error on any access to cms.apache.org.
>
> Is this still correct or do we use the command line tools?
>
> Claude
>
> On Fri, Jan 10, 2020 at 11:39 PM Claude Warren  wrote:
>
>> Will take a look at docs this weekend
>>
>> On 18:24, Fri 10 Jan 2020 Andy Seaborne >
>>> Ping?
>>>
>>> On 07/01/2020 16:58, Andy Seaborne wrote:
>>> >
>>> >
>>> > On 07/01/2020 15:51, Claude Warren wrote:
>>> >> I did some documentation updates (SVN) and think I checked it in.
>>> But I
>>> >> must have missed a step.
>>> >
>>> > I'm not clear what you are asking.
>>> >
>>> > svn? svn log shows some updated by you on 2019-12-20
>>> > The staging site?
>>> > The published site?
>>> >
>>> >  > Is there documentation somewhere?
>>> >
>>> > https://cwiki.apache.org/confluence/display/JENA/
>>> >
>>> >>
>>> >> Claude
>>> >>
>>>
>>
>
> --
> I like: Like Like - The likeliest place on the web
> 
> LinkedIn: http://www.linkedin.com/in/claudewarren
>


-- 
I like: Like Like - The likeliest place on the web

LinkedIn: http://www.linkedin.com/in/claudewarren