Ahem...

No I was wrong and also apologise as there seems to be a problem with
with gora-cassandra v0.2.1 indeed. For the time being please roll back
to 0.2 until we can release another gora-cassandra artifact.

Time to get digging.

Ta

Lewis

On Thu, Sep 20, 2012 at 10:54 PM, Lewis John Mcgibbney
<[email protected]> wrote:
> Hi Troops,
>
> This was a rather concerned email from myself however I can confirm
> that as far as my local testing has gone it was a false alarm.
>
> Please see my final response to the thread on the nutch user@ list for
> my reply to the issue.
>
> Looks like I can now press on with the Nutch 2.1 update ;)
>
> All the best for now
> Lewis
>
> On Wed, Sep 19, 2012 at 4:32 PM, Lewis John Mcgibbney
> <[email protected]> wrote:
>> Hi,
>>
>> Basically we are currently in the process of releasing Nutch 2.1 and
>> have unfortunately (but luckily) encountered a rather serious issue
>> regarding the gora-cassandra module v0.2.1 and backwards compatibility
>> with the Nutch 2.1 client application.
>>
>> Some questions I have
>>
>> 1. I would like to gauge some kind of usage statistics regarding of
>> gora-cassandra v0.2.1 in (2.x) Nutch branch. It is currently fitted
>> with gora-cassandra v0.2.1... which has been reported [0] to not work
>> properly. So far the best info I have is that 0.2 seems to work fine
>> but 0.2.1 does not! Although this is rather vague it still sets off
>> alarm bells.
>>
>> 2. If you have been using Nutch 2.x branch with gora-cassandra v0.2.1,
>> have you discovered any issues?
>>
>> As we know there were a number of improvements in gora-cassandra
>> between 0.2 and 0.2.1 and it would therefore be nice to retain
>> backwards compatibility.
>>
>> In all honesty I have not encountered any problems in my use cases so
>> far but that is not to say that there are none lingering.
>>
>> Thanks in advance for any info or insight you have.
>>
>> All the best for now
>>
>> [0] http://www.mail-archive.com/user%40nutch.apache.org/msg07618.html
>>
>> --
>> Lewis
>
>
>
> --
> Lewis



-- 
Lewis

Reply via email to