On 31/01/14 07:28, Michael Brunnbauer wrote:
Hello Andy,
On Thu, Jan 30, 2014 at 03:20:58PM +, Andy Seaborne wrote:
Sure - I would not expect anyone to run dev builds in production except
to explicitly pick up bug fixes. Do you have test or dev environments?
No. But the TDBs that are
On 29/01/14 19:00, Michael Brunnbauer wrote:
Hello Andy,
On Wed, Jan 29, 2014 at 06:40:05PM +, Andy Seaborne wrote:
[https://issues.apache.org/jira/browse/JENA-627]
The key issue here is resourcing.
It would take me a lot longer than one hour as I don't know your data or
indeed your
Comments inline:
On 28/01/2014 22:36, Michael Brunnbauer bru...@netestate.de wrote:
Hello Rob,
On Tue, Jan 28, 2014 at 02:20:22PM -0800, Rob Vesse wrote:
The 2.11.0 release was only last week so do not expect another official
release for a while.
OK
The somewhat toy query in your bug
Hello Rob,
On Wed, Jan 29, 2014 at 09:12:04AM -0800, Rob Vesse wrote:
It's a complete minimal example. I have an application that broke due to
this
one when I upgraded to 1.0.1.
Really, that is actually a real application query.
No - a complete minimal example. This is one of the real
hi all,
https://issues.apache.org/jira/browse/JENA-627
I guess this comes from ARQ and also affects Jena 2.11.1.
Can somebody confirm/assign it ?
Will there be a new release of Fuseki/Jena soon ?
Regards,
Michael Brunnbauer
On Fri, Jan 24, 2014 at 02:03:12PM +, Andy Seaborne wrote:
On 28/01/14 14:09, Michael Brunnbauer wrote:
hi all,
https://issues.apache.org/jira/browse/JENA-627
Created: Yesterday 14:00
Hmm ... 24 hours ...
I guess this comes from ARQ and also affects Jena 2.11.1.
Can somebody confirm/assign it ?
Will there be a new release of Fuseki/Jena soon ?
Hello Andy,
On Tue, Jan 28, 2014 at 02:30:36PM +, Andy Seaborne wrote:
https://issues.apache.org/jira/browse/JENA-627
Created: Yesterday 14:00
Hmm ... 24 hours ...
Sorry - I am getting used to your superb service :-)
It would be helpful to know when the next release is due so I can
Michael
The 2.11.0 release was only last week so do not expect another official
release for a while.
There is already a related fix for another bug that appears to solve your
problem (at least in some cases) so if you could start testing that and
see if that resolves the issue and that it
Hello Rob,
On Tue, Jan 28, 2014 at 02:20:22PM -0800, Rob Vesse wrote:
The 2.11.0 release was only last week so do not expect another official
release for a while.
OK
The somewhat toy query in your bug seems to imply that you have some set
of SPARQL smoke tests or similar that you use.
