You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by Andy Seaborne <an...@apache.org> on 2016/04/18 12:44:06 UTC

Towards release 3.1.0

Version 3.1.0 has quite a few good things in it1

I think it is about time we released it.

So this is a first ping for anything you want to get done for it.

As for timing - I can RM it sometime in the next few weeks though it 
will have to fit around other things.

     Andy

-------------------------------------------

* New custom functions and aggregate functions
   Added:
   + afn:sprintf (contribution from Alessandro Seganti)
   + The XQuery/XPath Functions and Operators "math:" functions
   + Custom aggregates for stdev etc. (also STDEV etc as keywords).

* RC features in 3.0.1:
   + In-memory transactional dataset (Adam Soroka )
   + SPARQL extension for CONSTRUCT Quads (Qihong Lin)

* OSGi fixes (Jaroslav Pullmann)

* Upgrades:
   jsonld-java : 2.8.2
     jackson 2.6.3
   slf4j 1.7.20
   dexx collections 0.2 -> 0.6 (OSGi)

* DatasetGraphs & transactions

* New module jena-cmds

* Logging - log4j marked <optional>

* Fuseki: Multiple service per file, shared datasets

* JSON result fix type: "literal" not "type": "typed-literal"

* Space saving when parsing (FactoryRDF)
   Parsing RDF now saves space by partial interning RDFTerms
   created during a each parser run.

Re: JENA-626 Re: Towards release 3.1.0

Posted by Saikat Maitra <sa...@gmail.com>.
Hi Andy,

No problem at all.

Regards
Saikat

On Wed, Apr 20, 2016 at 2:04 AM, Andy Seaborne <an...@apache.org> wrote:

> Saikat,
>
> Sorry this has taken so long to get looked at.
>
>         Andy
>
>

Re: JENA-626 Re: Towards release 3.1.0

Posted by Andy Seaborne <an...@apache.org>.
Saikat,

Sorry this has taken so long to get looked at.

	Andy


Re: JENA-626 Re: Towards release 3.1.0

Posted by Saikat Maitra <sa...@gmail.com>.
Hello Osma,

Thank you for your reply. Please find my replies inline.

Regards
Saikat

On Mon, Apr 18, 2016 at 10:53 PM, Osma Suominen <os...@helsinki.fi>
wrote:

> Hi Saikat!
>
> I'd love to see this merged. I can do a bit of testing if necessary.
>
> Sorry for my ignorance but I couldn't find answers to these questions
> easily in the PR or on Jira:
>
> How is this configured? Is it always on when compiled in? Can the
> parameters (e.g. cache size, maximum TTL) be configured? Is the cache
> stored in RAM, on disk, or is that selectable?
>

[Saikat] Yes, it is always on and running in Fuseki2 jvm. As of now the
cache size and TTL is not configurable and it is configured with maximum
size of 10000. The cache is store in RAM.

>
> From my perspective, I'd like to have a cache with a tunable size (say 1GB
> of RAM, preferably in some memory-efficient/compressed form), a LRU
> invalidation policy, and a very long TTL (say 1 week or more) unless the
> underlying data changes and thus the cache has to be invalidated, which
> should happen immediately.
>

[Saikat] The cache try to evict entries which are not used recently. In
case of update the cache entry is invalidated immediately.

>
> We currently use Varnish for this sort of caching but this feature could
> eliminate that dependency, at least for simple setups.
>
> [Saikat] Yes, I agree.

> -Osma
>
> 18.04.2016, 18:54, Saikat Maitra kirjoitti:
>
>> Hello Andy
>>
>> Please let me know if this PR can be accommodated in the release and if
>> any
>> further changes required.
>>
>> https://github.com/apache/jena/pull/95
>>
>> Regards
>> Saikat
>>
>>
>>
>> On Mon, Apr 18, 2016 at 5:05 PM, Osma Suominen <osma.suominen@helsinki.fi
>> >
>> wrote:
>>
>> Hi Andy!
>>>
>>> I'm happy with the current state of Jena and would support a release.
>>> This
>>> time I've been more diligent in using recent snapshots so there should be
>>> less chance of problems that surface only around release time.
>>>
>>> I have no outstanding work that I want to do for jena-text currently.
>>> JENA-1134/AnalyzingQueryParser (which you can consider including in the
>>> release notes) was the major item for me since the previous release, plus
>>> some bugfixes that were done earlier.
>>>
>>> -Osma
>>>
>>>
>>> On 18/04/16 13:44, Andy Seaborne wrote:
>>>
>>> Version 3.1.0 has quite a few good things in it1
>>>>
>>>> I think it is about time we released it.
>>>>
>>>> So this is a first ping for anything you want to get done for it.
>>>>
>>>> As for timing - I can RM it sometime in the next few weeks though it
>>>> will have to fit around other things.
>>>>
>>>>       Andy
>>>>
>>>> -------------------------------------------
>>>>
>>>> * New custom functions and aggregate functions
>>>>     Added:
>>>>     + afn:sprintf (contribution from Alessandro Seganti)
>>>>     + The XQuery/XPath Functions and Operators "math:" functions
>>>>     + Custom aggregates for stdev etc. (also STDEV etc as keywords).
>>>>
>>>> * RC features in 3.0.1:
>>>>     + In-memory transactional dataset (Adam Soroka )
>>>>     + SPARQL extension for CONSTRUCT Quads (Qihong Lin)
>>>>
>>>> * OSGi fixes (Jaroslav Pullmann)
>>>>
>>>> * Upgrades:
>>>>     jsonld-java : 2.8.2
>>>>       jackson 2.6.3
>>>>     slf4j 1.7.20
>>>>     dexx collections 0.2 -> 0.6 (OSGi)
>>>>
>>>> * DatasetGraphs & transactions
>>>>
>>>> * New module jena-cmds
>>>>
>>>> * Logging - log4j marked <optional>
>>>>
>>>> * Fuseki: Multiple service per file, shared datasets
>>>>
>>>> * JSON result fix type: "literal" not "type": "typed-literal"
>>>>
>>>> * Space saving when parsing (FactoryRDF)
>>>>     Parsing RDF now saves space by partial interning RDFTerms
>>>>     created during a each parser run.
>>>>
>>>>
>>>
>>> --
>>> Osma Suominen
>>> D.Sc. (Tech), Information Systems Specialist
>>> National Library of Finland
>>> P.O. Box 26 (Kaikukatu 4)
>>> 00014 HELSINGIN YLIOPISTO
>>> Tel. +358 50 3199529
>>> osma.suominen@helsinki.fi
>>> http://www.nationallibrary.fi
>>>
>>>
>>
>
> --
> Osma Suominen
> D.Sc. (Tech), Information Systems Specialist
> National Library of Finland
> P.O. Box 26 (Kaikukatu 4)
> 00014 HELSINGIN YLIOPISTO
> Tel. +358 50 3199529
> osma.suominen@helsinki.fi
> http://www.nationallibrary.fi
>

JENA-626 Re: Towards release 3.1.0

Posted by Osma Suominen <os...@helsinki.fi>.
Hi Saikat!

I'd love to see this merged. I can do a bit of testing if necessary.

Sorry for my ignorance but I couldn't find answers to these questions 
easily in the PR or on Jira:

How is this configured? Is it always on when compiled in? Can the 
parameters (e.g. cache size, maximum TTL) be configured? Is the cache 
stored in RAM, on disk, or is that selectable?

 From my perspective, I'd like to have a cache with a tunable size (say 
1GB of RAM, preferably in some memory-efficient/compressed form), a LRU 
invalidation policy, and a very long TTL (say 1 week or more) unless the 
underlying data changes and thus the cache has to be invalidated, which 
should happen immediately.

We currently use Varnish for this sort of caching but this feature could 
eliminate that dependency, at least for simple setups.

-Osma

18.04.2016, 18:54, Saikat Maitra kirjoitti:
> Hello Andy
>
> Please let me know if this PR can be accommodated in the release and if any
> further changes required.
>
> https://github.com/apache/jena/pull/95
>
> Regards
> Saikat
>
>
>
> On Mon, Apr 18, 2016 at 5:05 PM, Osma Suominen <os...@helsinki.fi>
> wrote:
>
>> Hi Andy!
>>
>> I'm happy with the current state of Jena and would support a release. This
>> time I've been more diligent in using recent snapshots so there should be
>> less chance of problems that surface only around release time.
>>
>> I have no outstanding work that I want to do for jena-text currently.
>> JENA-1134/AnalyzingQueryParser (which you can consider including in the
>> release notes) was the major item for me since the previous release, plus
>> some bugfixes that were done earlier.
>>
>> -Osma
>>
>>
>> On 18/04/16 13:44, Andy Seaborne wrote:
>>
>>> Version 3.1.0 has quite a few good things in it1
>>>
>>> I think it is about time we released it.
>>>
>>> So this is a first ping for anything you want to get done for it.
>>>
>>> As for timing - I can RM it sometime in the next few weeks though it
>>> will have to fit around other things.
>>>
>>>       Andy
>>>
>>> -------------------------------------------
>>>
>>> * New custom functions and aggregate functions
>>>     Added:
>>>     + afn:sprintf (contribution from Alessandro Seganti)
>>>     + The XQuery/XPath Functions and Operators "math:" functions
>>>     + Custom aggregates for stdev etc. (also STDEV etc as keywords).
>>>
>>> * RC features in 3.0.1:
>>>     + In-memory transactional dataset (Adam Soroka )
>>>     + SPARQL extension for CONSTRUCT Quads (Qihong Lin)
>>>
>>> * OSGi fixes (Jaroslav Pullmann)
>>>
>>> * Upgrades:
>>>     jsonld-java : 2.8.2
>>>       jackson 2.6.3
>>>     slf4j 1.7.20
>>>     dexx collections 0.2 -> 0.6 (OSGi)
>>>
>>> * DatasetGraphs & transactions
>>>
>>> * New module jena-cmds
>>>
>>> * Logging - log4j marked <optional>
>>>
>>> * Fuseki: Multiple service per file, shared datasets
>>>
>>> * JSON result fix type: "literal" not "type": "typed-literal"
>>>
>>> * Space saving when parsing (FactoryRDF)
>>>     Parsing RDF now saves space by partial interning RDFTerms
>>>     created during a each parser run.
>>>
>>
>>
>> --
>> Osma Suominen
>> D.Sc. (Tech), Information Systems Specialist
>> National Library of Finland
>> P.O. Box 26 (Kaikukatu 4)
>> 00014 HELSINGIN YLIOPISTO
>> Tel. +358 50 3199529
>> osma.suominen@helsinki.fi
>> http://www.nationallibrary.fi
>>
>


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

Re: Towards release 3.1.0

Posted by Saikat Maitra <sa...@gmail.com>.
Hello Andy

Please let me know if this PR can be accommodated in the release and if any
further changes required.

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

Regards
Saikat



On Mon, Apr 18, 2016 at 5:05 PM, Osma Suominen <os...@helsinki.fi>
wrote:

> Hi Andy!
>
> I'm happy with the current state of Jena and would support a release. This
> time I've been more diligent in using recent snapshots so there should be
> less chance of problems that surface only around release time.
>
> I have no outstanding work that I want to do for jena-text currently.
> JENA-1134/AnalyzingQueryParser (which you can consider including in the
> release notes) was the major item for me since the previous release, plus
> some bugfixes that were done earlier.
>
> -Osma
>
>
> On 18/04/16 13:44, Andy Seaborne wrote:
>
>> Version 3.1.0 has quite a few good things in it1
>>
>> I think it is about time we released it.
>>
>> So this is a first ping for anything you want to get done for it.
>>
>> As for timing - I can RM it sometime in the next few weeks though it
>> will have to fit around other things.
>>
>>      Andy
>>
>> -------------------------------------------
>>
>> * New custom functions and aggregate functions
>>    Added:
>>    + afn:sprintf (contribution from Alessandro Seganti)
>>    + The XQuery/XPath Functions and Operators "math:" functions
>>    + Custom aggregates for stdev etc. (also STDEV etc as keywords).
>>
>> * RC features in 3.0.1:
>>    + In-memory transactional dataset (Adam Soroka )
>>    + SPARQL extension for CONSTRUCT Quads (Qihong Lin)
>>
>> * OSGi fixes (Jaroslav Pullmann)
>>
>> * Upgrades:
>>    jsonld-java : 2.8.2
>>      jackson 2.6.3
>>    slf4j 1.7.20
>>    dexx collections 0.2 -> 0.6 (OSGi)
>>
>> * DatasetGraphs & transactions
>>
>> * New module jena-cmds
>>
>> * Logging - log4j marked <optional>
>>
>> * Fuseki: Multiple service per file, shared datasets
>>
>> * JSON result fix type: "literal" not "type": "typed-literal"
>>
>> * Space saving when parsing (FactoryRDF)
>>    Parsing RDF now saves space by partial interning RDFTerms
>>    created during a each parser run.
>>
>
>
> --
> Osma Suominen
> D.Sc. (Tech), Information Systems Specialist
> National Library of Finland
> P.O. Box 26 (Kaikukatu 4)
> 00014 HELSINGIN YLIOPISTO
> Tel. +358 50 3199529
> osma.suominen@helsinki.fi
> http://www.nationallibrary.fi
>

Re: Towards release 3.1.0

Posted by Andy Seaborne <an...@apache.org>.
OK - I'll go ahead as time permits.

[[
The process might be a bit intermittent depending on the network 
connectivity while travelling.  I'm going into the office this coming 
week ... which in my case involves UK->US.
]]

     Andy

On 29/04/16 21:08, Dave Reynolds wrote:
> +1
>
> Dave
>
> On 29/04/16 17:45, A. Soroka wrote:
>> +1 from this non-committer to holding the cache work for now. A simple
>> on-off switch seems absolutely requisite, and preferably we would have
>> fine-grained controls. The sudden appearance of an always-on cache
>> like this would represent really surprising new behavior for
>> integrators. Also, from the discussion on the PR in question [1] it
>> seems to me that there are still some questions of design.
>>
>> [1] https://github.com/apache/jena/pull/95
>>
>> ---
>> A. Soroka
>> The University of Virginia Library
>>
>>> On Apr 29, 2016, at 12:38 PM, Andy Seaborne <an...@apache.org> wrote:
>>>
>>> I'd like to go ahead with 3.1.0.
>>>
>>> The work on a query cache for Fuseki [*] was tested by Osma and found
>>> to be useful. There was also feedback on configuration and bounding
>>> the resources consumed by the caches.  Without the ability to
>>> configure it (including turn it off) I don't think that putting it in
>>> right before a release is a good idea.  There are is still some
>>> discussion to be had about the detailed design goals.
>>>
>>> So what I suggest is release Jena 3.1.0 now as-is, and start a
>>> testing/evaluation phase for a configurable cache.
>>>
>>> As a cache is most important under load, and Fuseki is used in
>>> deployed and public facing systems, I'm concerned that we block
>>> people picking up all the other things in 3.1.0.  I think it would be
>>> good to get wider testing via users@.  That will take time. (And then
>>> if people don't test it until after its in a release ... well, we can
>>> only do our best.)
>>>
>>>     Andy
>>>
>>> [*]
>>> https://issues.apache.org/jira/browse/JENA-626
>>> https://github.com/apache/jena/pull/95
>>>
>>> On 18/04/16 12:35, Osma Suominen wrote:
>>>> Hi Andy!
>>>>
>>>> I'm happy with the current state of Jena and would support a release.
>>>> This time I've been more diligent in using recent snapshots so there
>>>> should be less chance of problems that surface only around release
>>>> time.
>>>>
>>>> I have no outstanding work that I want to do for jena-text currently.
>>>> JENA-1134/AnalyzingQueryParser (which you can consider including in the
>>>> release notes) was the major item for me since the previous release,
>>>> plus some bugfixes that were done earlier.
>>>>
>>>> -Osma
>>>>
>>>> On 18/04/16 13:44, Andy Seaborne wrote:
>>>>> Version 3.1.0 has quite a few good things in it1
>>>>>
>>>>> I think it is about time we released it.
>>>>>
>>>>> So this is a first ping for anything you want to get done for it.
>>>>>
>>>>> As for timing - I can RM it sometime in the next few weeks though it
>>>>> will have to fit around other things.
>>>>>
>>>>>      Andy
>>>>>
>>>>> -------------------------------------------
>>>>>
>>>>> * New custom functions and aggregate functions
>>>>>    Added:
>>>>>    + afn:sprintf (contribution from Alessandro Seganti)
>>>>>    + The XQuery/XPath Functions and Operators "math:" functions
>>>>>    + Custom aggregates for stdev etc. (also STDEV etc as keywords).
>>>>>
>>>>> * RC features in 3.0.1:
>>>>>    + In-memory transactional dataset (Adam Soroka )
>>>>>    + SPARQL extension for CONSTRUCT Quads (Qihong Lin)
>>>>>
>>>>> * OSGi fixes (Jaroslav Pullmann)
>>>>>
>>>>> * Upgrades:
>>>>>    jsonld-java : 2.8.2
>>>>>      jackson 2.6.3
>>>>>    slf4j 1.7.20
>>>>>    dexx collections 0.2 -> 0.6 (OSGi)
>>>>>
>>>>> * DatasetGraphs & transactions
>>>>>
>>>>> * New module jena-cmds
>>>>>
>>>>> * Logging - log4j marked <optional>
>>>>>
>>>>> * Fuseki: Multiple service per file, shared datasets
>>>>>
>>>>> * JSON result fix type: "literal" not "type": "typed-literal"
>>>>>
>>>>> * Space saving when parsing (FactoryRDF)
>>>>>    Parsing RDF now saves space by partial interning RDFTerms
>>>>>    created during a each parser run.
>>>>
>>>>
>>>
>>
>


Re: Towards release 3.1.0

Posted by Dave Reynolds <da...@gmail.com>.
+1

Dave

On 29/04/16 17:45, A. Soroka wrote:
> +1 from this non-committer to holding the cache work for now. A simple on-off switch seems absolutely requisite, and preferably we would have fine-grained controls. The sudden appearance of an always-on cache like this would represent really surprising new behavior for integrators. Also, from the discussion on the PR in question [1] it seems to me that there are still some questions of design.
>
> [1] https://github.com/apache/jena/pull/95
>
> ---
> A. Soroka
> The University of Virginia Library
>
>> On Apr 29, 2016, at 12:38 PM, Andy Seaborne <an...@apache.org> wrote:
>>
>> I'd like to go ahead with 3.1.0.
>>
>> The work on a query cache for Fuseki [*] was tested by Osma and found to be useful. There was also feedback on configuration and bounding the resources consumed by the caches.  Without the ability to configure it (including turn it off) I don't think that putting it in right before a release is a good idea.  There are is still some discussion to be had about the detailed design goals.
>>
>> So what I suggest is release Jena 3.1.0 now as-is, and start a testing/evaluation phase for a configurable cache.
>>
>> As a cache is most important under load, and Fuseki is used in deployed and public facing systems, I'm concerned that we block people picking up all the other things in 3.1.0.  I think it would be good to get wider testing via users@.  That will take time. (And then if people don't test it until after its in a release ... well, we can only do our best.)
>>
>> 	Andy
>>
>> [*]
>> https://issues.apache.org/jira/browse/JENA-626
>> https://github.com/apache/jena/pull/95
>>
>> On 18/04/16 12:35, Osma Suominen wrote:
>>> Hi Andy!
>>>
>>> I'm happy with the current state of Jena and would support a release.
>>> This time I've been more diligent in using recent snapshots so there
>>> should be less chance of problems that surface only around release time.
>>>
>>> I have no outstanding work that I want to do for jena-text currently.
>>> JENA-1134/AnalyzingQueryParser (which you can consider including in the
>>> release notes) was the major item for me since the previous release,
>>> plus some bugfixes that were done earlier.
>>>
>>> -Osma
>>>
>>> On 18/04/16 13:44, Andy Seaborne wrote:
>>>> Version 3.1.0 has quite a few good things in it1
>>>>
>>>> I think it is about time we released it.
>>>>
>>>> So this is a first ping for anything you want to get done for it.
>>>>
>>>> As for timing - I can RM it sometime in the next few weeks though it
>>>> will have to fit around other things.
>>>>
>>>>      Andy
>>>>
>>>> -------------------------------------------
>>>>
>>>> * New custom functions and aggregate functions
>>>>    Added:
>>>>    + afn:sprintf (contribution from Alessandro Seganti)
>>>>    + The XQuery/XPath Functions and Operators "math:" functions
>>>>    + Custom aggregates for stdev etc. (also STDEV etc as keywords).
>>>>
>>>> * RC features in 3.0.1:
>>>>    + In-memory transactional dataset (Adam Soroka )
>>>>    + SPARQL extension for CONSTRUCT Quads (Qihong Lin)
>>>>
>>>> * OSGi fixes (Jaroslav Pullmann)
>>>>
>>>> * Upgrades:
>>>>    jsonld-java : 2.8.2
>>>>      jackson 2.6.3
>>>>    slf4j 1.7.20
>>>>    dexx collections 0.2 -> 0.6 (OSGi)
>>>>
>>>> * DatasetGraphs & transactions
>>>>
>>>> * New module jena-cmds
>>>>
>>>> * Logging - log4j marked <optional>
>>>>
>>>> * Fuseki: Multiple service per file, shared datasets
>>>>
>>>> * JSON result fix type: "literal" not "type": "typed-literal"
>>>>
>>>> * Space saving when parsing (FactoryRDF)
>>>>    Parsing RDF now saves space by partial interning RDFTerms
>>>>    created during a each parser run.
>>>
>>>
>>
>


Re: Towards release 3.1.0

Posted by "A. Soroka" <aj...@virginia.edu>.
+1 from this non-committer to holding the cache work for now. A simple on-off switch seems absolutely requisite, and preferably we would have fine-grained controls. The sudden appearance of an always-on cache like this would represent really surprising new behavior for integrators. Also, from the discussion on the PR in question [1] it seems to me that there are still some questions of design.

[1] https://github.com/apache/jena/pull/95

---
A. Soroka
The University of Virginia Library

> On Apr 29, 2016, at 12:38 PM, Andy Seaborne <an...@apache.org> wrote:
> 
> I'd like to go ahead with 3.1.0.
> 
> The work on a query cache for Fuseki [*] was tested by Osma and found to be useful. There was also feedback on configuration and bounding the resources consumed by the caches.  Without the ability to configure it (including turn it off) I don't think that putting it in right before a release is a good idea.  There are is still some discussion to be had about the detailed design goals.
> 
> So what I suggest is release Jena 3.1.0 now as-is, and start a testing/evaluation phase for a configurable cache.
> 
> As a cache is most important under load, and Fuseki is used in deployed and public facing systems, I'm concerned that we block people picking up all the other things in 3.1.0.  I think it would be good to get wider testing via users@.  That will take time. (And then if people don't test it until after its in a release ... well, we can only do our best.)
> 
> 	Andy
> 
> [*]
> https://issues.apache.org/jira/browse/JENA-626
> https://github.com/apache/jena/pull/95
> 
> On 18/04/16 12:35, Osma Suominen wrote:
>> Hi Andy!
>> 
>> I'm happy with the current state of Jena and would support a release.
>> This time I've been more diligent in using recent snapshots so there
>> should be less chance of problems that surface only around release time.
>> 
>> I have no outstanding work that I want to do for jena-text currently.
>> JENA-1134/AnalyzingQueryParser (which you can consider including in the
>> release notes) was the major item for me since the previous release,
>> plus some bugfixes that were done earlier.
>> 
>> -Osma
>> 
>> On 18/04/16 13:44, Andy Seaborne wrote:
>>> Version 3.1.0 has quite a few good things in it1
>>> 
>>> I think it is about time we released it.
>>> 
>>> So this is a first ping for anything you want to get done for it.
>>> 
>>> As for timing - I can RM it sometime in the next few weeks though it
>>> will have to fit around other things.
>>> 
>>>     Andy
>>> 
>>> -------------------------------------------
>>> 
>>> * New custom functions and aggregate functions
>>>   Added:
>>>   + afn:sprintf (contribution from Alessandro Seganti)
>>>   + The XQuery/XPath Functions and Operators "math:" functions
>>>   + Custom aggregates for stdev etc. (also STDEV etc as keywords).
>>> 
>>> * RC features in 3.0.1:
>>>   + In-memory transactional dataset (Adam Soroka )
>>>   + SPARQL extension for CONSTRUCT Quads (Qihong Lin)
>>> 
>>> * OSGi fixes (Jaroslav Pullmann)
>>> 
>>> * Upgrades:
>>>   jsonld-java : 2.8.2
>>>     jackson 2.6.3
>>>   slf4j 1.7.20
>>>   dexx collections 0.2 -> 0.6 (OSGi)
>>> 
>>> * DatasetGraphs & transactions
>>> 
>>> * New module jena-cmds
>>> 
>>> * Logging - log4j marked <optional>
>>> 
>>> * Fuseki: Multiple service per file, shared datasets
>>> 
>>> * JSON result fix type: "literal" not "type": "typed-literal"
>>> 
>>> * Space saving when parsing (FactoryRDF)
>>>   Parsing RDF now saves space by partial interning RDFTerms
>>>   created during a each parser run.
>> 
>> 
> 


Re: Towards release 3.1.0

Posted by Andy Seaborne <an...@apache.org>.
Don't worry about any Jenkins failures

There is a java JVM dump in the Jenkins workspace and, unsurprisingly, 
it does not pass the RAT checking for licenses.

     Andy

On 03/05/16 11:27, Osma Suominen wrote:
> Thanks for reviewing! I merged the fix to master and resolved the JIRA
> issue.
>
> -Osma
>
> 'On 03/05/16 13:11, Andy Seaborne wrote:
>> Great - apply the fix to master and I'll pick it up.
>>
>> I haven't had time to look at the release problem but I have narrowed it
>> down to lib/ being created after the binaries so the ones picked up are
>> from a previous maven run.
>>
>> So something in the assembly.
>>
>> That might mean this is a very old situation that just happened not to
>> occur or a change of version or a change of assembly.
>>
>>      Andy
>>
>>
>>
>> On 02/05/16 08:45, Osma Suominen wrote:
>>> +1 for releasing without the cache, though I'll try getting in at least
>>> the trivial fix (prevent blank nodes being indexed by jena-text) for
>>> JENA-1172 that I just reported.
>>>
>>> -Osma
>>>
>>> On 29/04/16 19:38, Andy Seaborne wrote:
>>>> I'd like to go ahead with 3.1.0.
>>>>
>>>> The work on a query cache for Fuseki [*] was tested by Osma and
>>>> found to
>>>> be useful. There was also feedback on configuration and bounding the
>>>> resources consumed by the caches.  Without the ability to configure it
>>>> (including turn it off) I don't think that putting it in right before a
>>>> release is a good idea.  There are is still some discussion to be had
>>>> about the detailed design goals.
>>>>
>>>> So what I suggest is release Jena 3.1.0 now as-is, and start a
>>>> testing/evaluation phase for a configurable cache.
>>>>
>>>> As a cache is most important under load, and Fuseki is used in deployed
>>>> and public facing systems, I'm concerned that we block people
>>>> picking up
>>>> all the other things in 3.1.0.  I think it would be good to get wider
>>>> testing via users@.  That will take time. (And then if people don't
>>>> test
>>>> it until after its in a release ... well, we can only do our best.)
>>>>
>>>>      Andy
>>>>
>>>> [*]
>>>> https://issues.apache.org/jira/browse/JENA-626
>>>> https://github.com/apache/jena/pull/95
>>>>
>>>> On 18/04/16 12:35, Osma Suominen wrote:
>>>>> Hi Andy!
>>>>>
>>>>> I'm happy with the current state of Jena and would support a release.
>>>>> This time I've been more diligent in using recent snapshots so there
>>>>> should be less chance of problems that surface only around release
>>>>> time.
>>>>>
>>>>> I have no outstanding work that I want to do for jena-text currently.
>>>>> JENA-1134/AnalyzingQueryParser (which you can consider including in
>>>>> the
>>>>> release notes) was the major item for me since the previous release,
>>>>> plus some bugfixes that were done earlier.
>>>>>
>>>>> -Osma
>>>>>
>>>>> On 18/04/16 13:44, Andy Seaborne wrote:
>>>>>> Version 3.1.0 has quite a few good things in it1
>>>>>>
>>>>>> I think it is about time we released it.
>>>>>>
>>>>>> So this is a first ping for anything you want to get done for it.
>>>>>> to be stored
>>>>>> As for timing - I can RM it sometime in the next few weeks though it
>>>>>> will have to fit around other things.
>>>>>>
>>>>>>      Andy
>>>>>>
>>>>>> -------------------------------------------
>>>>>>
>>>>>> * New custom functions and aggregate functions
>>>>>>    Added:
>>>>>>    + afn:sprintf (contribution from Alessandro Seganti)
>>>>>>    + The XQuery/XPath Functions and Operators "math:" functions
>>>>>>    + Custom aggregates for stdev etc. (also STDEV etc as keywords).
>>>>>>
>>>>>> * RC features in 3.0.1:
>>>>>>    + In-memory transactional dataset (Adam Soroka )
>>>>>>    + SPARQL extension for CONSTRUCT Quads (Qihong Lin)
>>>>>>
>>>>>> * OSGi fixes (Jaroslav Pullmann)
>>>>>>
>>>>>> * Upgrades:
>>>>>>    jsonld-java : 2.8.2
>>>>>>      jackson 2.6.3
>>>>>>    slf4j 1.7.20
>>>>>>    dexx collections 0.2 -> 0.6 (OSGi)
>>>>>>
>>>>>> * DatasetGraphs & transactions
>>>>>>
>>>>>> * New module jena-cmds
>>>>>>
>>>>>> * Logging - log4j marked <optional>
>>>>>>
>>>>>> * Fuseki: Multiple service per file, shared datasets
>>>>>>
>>>>>> * JSON result fix type: "literal" not "type": "typed-literal"
>>>>>>
>>>>>> * Space saving when parsing (FactoryRDF)
>>>>>>    Parsing RDF now saves space by partial interning RDFTerms
>>>>>>    created during a each parser run.
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>
>


Re: Towards release 3.1.0

Posted by Osma Suominen <os...@helsinki.fi>.
Thanks for reviewing! I merged the fix to master and resolved the JIRA 
issue.

-Osma

'On 03/05/16 13:11, Andy Seaborne wrote:
> Great - apply the fix to master and I'll pick it up.
>
> I haven't had time to look at the release problem but I have narrowed it
> down to lib/ being created after the binaries so the ones picked up are
> from a previous maven run.
>
> So something in the assembly.
>
> That might mean this is a very old situation that just happened not to
> occur or a change of version or a change of assembly.
>
>      Andy
>
>
>
> On 02/05/16 08:45, Osma Suominen wrote:
>> +1 for releasing without the cache, though I'll try getting in at least
>> the trivial fix (prevent blank nodes being indexed by jena-text) for
>> JENA-1172 that I just reported.
>>
>> -Osma
>>
>> On 29/04/16 19:38, Andy Seaborne wrote:
>>> I'd like to go ahead with 3.1.0.
>>>
>>> The work on a query cache for Fuseki [*] was tested by Osma and found to
>>> be useful. There was also feedback on configuration and bounding the
>>> resources consumed by the caches.  Without the ability to configure it
>>> (including turn it off) I don't think that putting it in right before a
>>> release is a good idea.  There are is still some discussion to be had
>>> about the detailed design goals.
>>>
>>> So what I suggest is release Jena 3.1.0 now as-is, and start a
>>> testing/evaluation phase for a configurable cache.
>>>
>>> As a cache is most important under load, and Fuseki is used in deployed
>>> and public facing systems, I'm concerned that we block people picking up
>>> all the other things in 3.1.0.  I think it would be good to get wider
>>> testing via users@.  That will take time. (And then if people don't test
>>> it until after its in a release ... well, we can only do our best.)
>>>
>>>      Andy
>>>
>>> [*]
>>> https://issues.apache.org/jira/browse/JENA-626
>>> https://github.com/apache/jena/pull/95
>>>
>>> On 18/04/16 12:35, Osma Suominen wrote:
>>>> Hi Andy!
>>>>
>>>> I'm happy with the current state of Jena and would support a release.
>>>> This time I've been more diligent in using recent snapshots so there
>>>> should be less chance of problems that surface only around release
>>>> time.
>>>>
>>>> I have no outstanding work that I want to do for jena-text currently.
>>>> JENA-1134/AnalyzingQueryParser (which you can consider including in the
>>>> release notes) was the major item for me since the previous release,
>>>> plus some bugfixes that were done earlier.
>>>>
>>>> -Osma
>>>>
>>>> On 18/04/16 13:44, Andy Seaborne wrote:
>>>>> Version 3.1.0 has quite a few good things in it1
>>>>>
>>>>> I think it is about time we released it.
>>>>>
>>>>> So this is a first ping for anything you want to get done for it.
>>>>> to be stored
>>>>> As for timing - I can RM it sometime in the next few weeks though it
>>>>> will have to fit around other things.
>>>>>
>>>>>      Andy
>>>>>
>>>>> -------------------------------------------
>>>>>
>>>>> * New custom functions and aggregate functions
>>>>>    Added:
>>>>>    + afn:sprintf (contribution from Alessandro Seganti)
>>>>>    + The XQuery/XPath Functions and Operators "math:" functions
>>>>>    + Custom aggregates for stdev etc. (also STDEV etc as keywords).
>>>>>
>>>>> * RC features in 3.0.1:
>>>>>    + In-memory transactional dataset (Adam Soroka )
>>>>>    + SPARQL extension for CONSTRUCT Quads (Qihong Lin)
>>>>>
>>>>> * OSGi fixes (Jaroslav Pullmann)
>>>>>
>>>>> * Upgrades:
>>>>>    jsonld-java : 2.8.2
>>>>>      jackson 2.6.3
>>>>>    slf4j 1.7.20
>>>>>    dexx collections 0.2 -> 0.6 (OSGi)
>>>>>
>>>>> * DatasetGraphs & transactions
>>>>>
>>>>> * New module jena-cmds
>>>>>
>>>>> * Logging - log4j marked <optional>
>>>>>
>>>>> * Fuseki: Multiple service per file, shared datasets
>>>>>
>>>>> * JSON result fix type: "literal" not "type": "typed-literal"
>>>>>
>>>>> * Space saving when parsing (FactoryRDF)
>>>>>    Parsing RDF now saves space by partial interning RDFTerms
>>>>>    created during a each parser run.
>>>>
>>>>
>>>
>>
>>
>


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

Re: Towards release 3.1.0

Posted by Andy Seaborne <an...@apache.org>.
Great - apply the fix to master and I'll pick it up.

I haven't had time to look at the release problem but I have narrowed it 
down to lib/ being created after the binaries so the ones picked up are 
from a previous maven run.

So something in the assembly.

That might mean this is a very old situation that just happened not to 
occur or a change of version or a change of assembly.

     Andy



On 02/05/16 08:45, Osma Suominen wrote:
> +1 for releasing without the cache, though I'll try getting in at least
> the trivial fix (prevent blank nodes being indexed by jena-text) for
> JENA-1172 that I just reported.
>
> -Osma
>
> On 29/04/16 19:38, Andy Seaborne wrote:
>> I'd like to go ahead with 3.1.0.
>>
>> The work on a query cache for Fuseki [*] was tested by Osma and found to
>> be useful. There was also feedback on configuration and bounding the
>> resources consumed by the caches.  Without the ability to configure it
>> (including turn it off) I don't think that putting it in right before a
>> release is a good idea.  There are is still some discussion to be had
>> about the detailed design goals.
>>
>> So what I suggest is release Jena 3.1.0 now as-is, and start a
>> testing/evaluation phase for a configurable cache.
>>
>> As a cache is most important under load, and Fuseki is used in deployed
>> and public facing systems, I'm concerned that we block people picking up
>> all the other things in 3.1.0.  I think it would be good to get wider
>> testing via users@.  That will take time. (And then if people don't test
>> it until after its in a release ... well, we can only do our best.)
>>
>>      Andy
>>
>> [*]
>> https://issues.apache.org/jira/browse/JENA-626
>> https://github.com/apache/jena/pull/95
>>
>> On 18/04/16 12:35, Osma Suominen wrote:
>>> Hi Andy!
>>>
>>> I'm happy with the current state of Jena and would support a release.
>>> This time I've been more diligent in using recent snapshots so there
>>> should be less chance of problems that surface only around release time.
>>>
>>> I have no outstanding work that I want to do for jena-text currently.
>>> JENA-1134/AnalyzingQueryParser (which you can consider including in the
>>> release notes) was the major item for me since the previous release,
>>> plus some bugfixes that were done earlier.
>>>
>>> -Osma
>>>
>>> On 18/04/16 13:44, Andy Seaborne wrote:
>>>> Version 3.1.0 has quite a few good things in it1
>>>>
>>>> I think it is about time we released it.
>>>>
>>>> So this is a first ping for anything you want to get done for it.
>>>> to be stored
>>>> As for timing - I can RM it sometime in the next few weeks though it
>>>> will have to fit around other things.
>>>>
>>>>      Andy
>>>>
>>>> -------------------------------------------
>>>>
>>>> * New custom functions and aggregate functions
>>>>    Added:
>>>>    + afn:sprintf (contribution from Alessandro Seganti)
>>>>    + The XQuery/XPath Functions and Operators "math:" functions
>>>>    + Custom aggregates for stdev etc. (also STDEV etc as keywords).
>>>>
>>>> * RC features in 3.0.1:
>>>>    + In-memory transactional dataset (Adam Soroka )
>>>>    + SPARQL extension for CONSTRUCT Quads (Qihong Lin)
>>>>
>>>> * OSGi fixes (Jaroslav Pullmann)
>>>>
>>>> * Upgrades:
>>>>    jsonld-java : 2.8.2
>>>>      jackson 2.6.3
>>>>    slf4j 1.7.20
>>>>    dexx collections 0.2 -> 0.6 (OSGi)
>>>>
>>>> * DatasetGraphs & transactions
>>>>
>>>> * New module jena-cmds
>>>>
>>>> * Logging - log4j marked <optional>
>>>>
>>>> * Fuseki: Multiple service per file, shared datasets
>>>>
>>>> * JSON result fix type: "literal" not "type": "typed-literal"
>>>>
>>>> * Space saving when parsing (FactoryRDF)
>>>>    Parsing RDF now saves space by partial interning RDFTerms
>>>>    created during a each parser run.
>>>
>>>
>>
>
>


Re: Towards release 3.1.0

Posted by Osma Suominen <os...@helsinki.fi>.
+1 for releasing without the cache, though I'll try getting in at least 
the trivial fix (prevent blank nodes being indexed by jena-text) for 
JENA-1172 that I just reported.

-Osma

On 29/04/16 19:38, Andy Seaborne wrote:
> I'd like to go ahead with 3.1.0.
>
> The work on a query cache for Fuseki [*] was tested by Osma and found to
> be useful. There was also feedback on configuration and bounding the
> resources consumed by the caches.  Without the ability to configure it
> (including turn it off) I don't think that putting it in right before a
> release is a good idea.  There are is still some discussion to be had
> about the detailed design goals.
>
> So what I suggest is release Jena 3.1.0 now as-is, and start a
> testing/evaluation phase for a configurable cache.
>
> As a cache is most important under load, and Fuseki is used in deployed
> and public facing systems, I'm concerned that we block people picking up
> all the other things in 3.1.0.  I think it would be good to get wider
> testing via users@.  That will take time. (And then if people don't test
> it until after its in a release ... well, we can only do our best.)
>
>      Andy
>
> [*]
> https://issues.apache.org/jira/browse/JENA-626
> https://github.com/apache/jena/pull/95
>
> On 18/04/16 12:35, Osma Suominen wrote:
>> Hi Andy!
>>
>> I'm happy with the current state of Jena and would support a release.
>> This time I've been more diligent in using recent snapshots so there
>> should be less chance of problems that surface only around release time.
>>
>> I have no outstanding work that I want to do for jena-text currently.
>> JENA-1134/AnalyzingQueryParser (which you can consider including in the
>> release notes) was the major item for me since the previous release,
>> plus some bugfixes that were done earlier.
>>
>> -Osma
>>
>> On 18/04/16 13:44, Andy Seaborne wrote:
>>> Version 3.1.0 has quite a few good things in it1
>>>
>>> I think it is about time we released it.
>>>
>>> So this is a first ping for anything you want to get done for it.
>>>
>>> As for timing - I can RM it sometime in the next few weeks though it
>>> will have to fit around other things.
>>>
>>>      Andy
>>>
>>> -------------------------------------------
>>>
>>> * New custom functions and aggregate functions
>>>    Added:
>>>    + afn:sprintf (contribution from Alessandro Seganti)
>>>    + The XQuery/XPath Functions and Operators "math:" functions
>>>    + Custom aggregates for stdev etc. (also STDEV etc as keywords).
>>>
>>> * RC features in 3.0.1:
>>>    + In-memory transactional dataset (Adam Soroka )
>>>    + SPARQL extension for CONSTRUCT Quads (Qihong Lin)
>>>
>>> * OSGi fixes (Jaroslav Pullmann)
>>>
>>> * Upgrades:
>>>    jsonld-java : 2.8.2
>>>      jackson 2.6.3
>>>    slf4j 1.7.20
>>>    dexx collections 0.2 -> 0.6 (OSGi)
>>>
>>> * DatasetGraphs & transactions
>>>
>>> * New module jena-cmds
>>>
>>> * Logging - log4j marked <optional>
>>>
>>> * Fuseki: Multiple service per file, shared datasets
>>>
>>> * JSON result fix type: "literal" not "type": "typed-literal"
>>>
>>> * Space saving when parsing (FactoryRDF)
>>>    Parsing RDF now saves space by partial interning RDFTerms
>>>    created during a each parser run.
>>
>>
>


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

Re: Towards release 3.1.0

Posted by Andy Seaborne <an...@apache.org>.
I'd like to go ahead with 3.1.0.

The work on a query cache for Fuseki [*] was tested by Osma and found to 
be useful. There was also feedback on configuration and bounding the 
resources consumed by the caches.  Without the ability to configure it 
(including turn it off) I don't think that putting it in right before a 
release is a good idea.  There are is still some discussion to be had 
about the detailed design goals.

So what I suggest is release Jena 3.1.0 now as-is, and start a 
testing/evaluation phase for a configurable cache.

As a cache is most important under load, and Fuseki is used in deployed 
and public facing systems, I'm concerned that we block people picking up 
all the other things in 3.1.0.  I think it would be good to get wider 
testing via users@.  That will take time. (And then if people don't test 
it until after its in a release ... well, we can only do our best.)

	Andy

[*]
https://issues.apache.org/jira/browse/JENA-626
https://github.com/apache/jena/pull/95

On 18/04/16 12:35, Osma Suominen wrote:
> Hi Andy!
>
> I'm happy with the current state of Jena and would support a release.
> This time I've been more diligent in using recent snapshots so there
> should be less chance of problems that surface only around release time.
>
> I have no outstanding work that I want to do for jena-text currently.
> JENA-1134/AnalyzingQueryParser (which you can consider including in the
> release notes) was the major item for me since the previous release,
> plus some bugfixes that were done earlier.
>
> -Osma
>
> On 18/04/16 13:44, Andy Seaborne wrote:
>> Version 3.1.0 has quite a few good things in it1
>>
>> I think it is about time we released it.
>>
>> So this is a first ping for anything you want to get done for it.
>>
>> As for timing - I can RM it sometime in the next few weeks though it
>> will have to fit around other things.
>>
>>      Andy
>>
>> -------------------------------------------
>>
>> * New custom functions and aggregate functions
>>    Added:
>>    + afn:sprintf (contribution from Alessandro Seganti)
>>    + The XQuery/XPath Functions and Operators "math:" functions
>>    + Custom aggregates for stdev etc. (also STDEV etc as keywords).
>>
>> * RC features in 3.0.1:
>>    + In-memory transactional dataset (Adam Soroka )
>>    + SPARQL extension for CONSTRUCT Quads (Qihong Lin)
>>
>> * OSGi fixes (Jaroslav Pullmann)
>>
>> * Upgrades:
>>    jsonld-java : 2.8.2
>>      jackson 2.6.3
>>    slf4j 1.7.20
>>    dexx collections 0.2 -> 0.6 (OSGi)
>>
>> * DatasetGraphs & transactions
>>
>> * New module jena-cmds
>>
>> * Logging - log4j marked <optional>
>>
>> * Fuseki: Multiple service per file, shared datasets
>>
>> * JSON result fix type: "literal" not "type": "typed-literal"
>>
>> * Space saving when parsing (FactoryRDF)
>>    Parsing RDF now saves space by partial interning RDFTerms
>>    created during a each parser run.
>
>


Re: Towards release 3.1.0

Posted by Osma Suominen <os...@helsinki.fi>.
Hi Andy!

I'm happy with the current state of Jena and would support a release. 
This time I've been more diligent in using recent snapshots so there 
should be less chance of problems that surface only around release time.

I have no outstanding work that I want to do for jena-text currently. 
JENA-1134/AnalyzingQueryParser (which you can consider including in the 
release notes) was the major item for me since the previous release, 
plus some bugfixes that were done earlier.

-Osma

On 18/04/16 13:44, Andy Seaborne wrote:
> Version 3.1.0 has quite a few good things in it1
>
> I think it is about time we released it.
>
> So this is a first ping for anything you want to get done for it.
>
> As for timing - I can RM it sometime in the next few weeks though it
> will have to fit around other things.
>
>      Andy
>
> -------------------------------------------
>
> * New custom functions and aggregate functions
>    Added:
>    + afn:sprintf (contribution from Alessandro Seganti)
>    + The XQuery/XPath Functions and Operators "math:" functions
>    + Custom aggregates for stdev etc. (also STDEV etc as keywords).
>
> * RC features in 3.0.1:
>    + In-memory transactional dataset (Adam Soroka )
>    + SPARQL extension for CONSTRUCT Quads (Qihong Lin)
>
> * OSGi fixes (Jaroslav Pullmann)
>
> * Upgrades:
>    jsonld-java : 2.8.2
>      jackson 2.6.3
>    slf4j 1.7.20
>    dexx collections 0.2 -> 0.6 (OSGi)
>
> * DatasetGraphs & transactions
>
> * New module jena-cmds
>
> * Logging - log4j marked <optional>
>
> * Fuseki: Multiple service per file, shared datasets
>
> * JSON result fix type: "literal" not "type": "typed-literal"
>
> * Space saving when parsing (FactoryRDF)
>    Parsing RDF now saves space by partial interning RDFTerms
>    created during a each parser run.


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