ARQ 2.10.0 Upgrade Notes

[Rob Vesse <rv...@yarcdata.com>]

Here are my notes on upgrading our code base to ARQ 2.10.0, all in all this has been relatively painless.

Mostly I was simply able to use a Find and Replace to change openjena to apache.jena which made life very simple, while we do hook into ARQ and RIOT at a fairly low level other than the package renames I didn't find anything that had really changed fundamentally.

I ran into one oddity which is that SinkQuadsToDataset now takes a boolean argument in it's constructor but this argument appears to never be used in the SinkQuadsToDataset code.  What if anything is this argument supposed to be doing?

Other than this I haven't had any problems, it'll be a little while before we run our next integration cycle so I'll feed back to the list later in the month if anything shows up with that or if it all goes smoothly as I expect.  Certainly making these changes hasn't caused our CI builds of our modules that rely on ARQ to keel over immediately which is always a good sign.

Cheers,

Rob

Re: ARQ 2.10.0 Upgrade Notes

[Rob Vesse <rv...@yarcdata.com>]

Thanks for the heads up, have switched to using StreamRDFLib and
RDFDataMgr instead since that seems a bit nicer than creating Sinks
directly and calling RiotReader

Rob


On 1/15/13 2:33 PM, "Andy Seaborne" <an...@apache.org> wrote:

>On 15/01/13 14:13, Rob Vesse wrote:
>> Here are my notes on upgrading our code base to ARQ 2.10.0, all in
>> all this has been relatively painless.
>>
>> Mostly I was simply able to use a Find and Replace to change openjena
>> to apache.jena which made life very simple, while we do hook into ARQ
>> and RIOT at a fairly low level other than the package renames I
>> didn't find anything that had really changed fundamentally.
>
>Good.
>
>> I ran into one oddity which is that SinkQuadsToDataset now takes a
>> boolean argument in it's constructor but this argument appears to
>> never be used in the SinkQuadsToDataset code.  What if anything is
>> this argument supposed to be doing?
>
>Arrg!  It was there to force a signature change during the transition to
>check for same class but under org.openjena.  Nothing more.
>
>It will be removed ASAP - sorry, that's be a bump for you.
>
>SinkQuadsToDataset isn't used in the codebase any more.
>
>See also
>
>    StreamRDFLib.dataset(...)
>
>which creates a direct parser to dataset connection.
>
>> Other than this I haven't had any problems, it'll be a little while
>> before we run our next integration cycle so I'll feed back to the
>> list later in the month if anything shows up with that or if it all
>> goes smoothly as I expect.  Certainly making these changes hasn't
>> caused our CI builds of our modules that rely on ARQ to keel over
>> immediately which is always a good sign.
>
><relief/>
>
>>
>> Cheers,
>>
>> Rob
>>
>

Re: ARQ 2.10.0 Upgrade Notes

[Andy Seaborne <an...@apache.org>]

On 15/01/13 14:13, Rob Vesse wrote:
> Here are my notes on upgrading our code base to ARQ 2.10.0, all in
> all this has been relatively painless.
>
> Mostly I was simply able to use a Find and Replace to change openjena
> to apache.jena which made life very simple, while we do hook into ARQ
> and RIOT at a fairly low level other than the package renames I
> didn't find anything that had really changed fundamentally.

Good.

> I ran into one oddity which is that SinkQuadsToDataset now takes a
> boolean argument in it's constructor but this argument appears to
> never be used in the SinkQuadsToDataset code.  What if anything is
> this argument supposed to be doing?

Arrg!  It was there to force a signature change during the transition to 
check for same class but under org.openjena.  Nothing more.

It will be removed ASAP - sorry, that's be a bump for you.

SinkQuadsToDataset isn't used in the codebase any more.

See also

    StreamRDFLib.dataset(...)

which creates a direct parser to dataset connection.

> Other than this I haven't had any problems, it'll be a little while
> before we run our next integration cycle so I'll feed back to the
> list later in the month if anything shows up with that or if it all
> goes smoothly as I expect.  Certainly making these changes hasn't
> caused our CI builds of our modules that rely on ARQ to keel over
> immediately which is always a good sign.

<relief/>

>
> Cheers,
>
> Rob
>