Mailing-List: contact gora-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: gora-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of alexis.detreglode@gmail.com
 designates 209.85.210.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <1979681516.14770.1311348117900.JavaMail.tomcat@hel.zones.apache.org>
References: <912921.283031294757686013.JavaMail.jira@thor>
	<1979681516.14770.1311348117900.JavaMail.tomcat@hel.zones.apache.org>
Date: Fri, 22 Jul 2011 16:08:08 -0700
Message-ID: 
 <CAEyseSFDFaYpwLOyutQVGSJsWb6FwFR7hVYCvCza4DDPj1KVSg@mail.gmail.com>
Subject: Re: [jira] [Commented] (GORA-22) Upgrade cassandra backend to
 cassandra 0.7
From: Alexis <alexis.detreglode@gmail.com>
To: gora-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

Sorry I have committed my changes before I had the go ahead of the
other peers. I am still learning the opensource etiquette. I thought
it was fine to replace the code since I believe the Cassandra part was
broken. I personnally never managed to use the code "as is". It was
mentioned to me the entire backend needed to be rewritten:
See Julien's comment in this page:
http://techvineyard.blogspot.com/2011/01/trying-nutch-20-hbase-storage.html=
:

"The Cassandra backend in GORA is in need of serious work and is not
considered fully functional, IIRC it is not thread safe. There has
been a new release of Cassandra in the meantime and I am pretty sure
that it would be quicker to simply write a new backend for GORA based
on the latest release..."

Now we have 2 options:
- revert the modifications and go back to a broken state
- test the new version and iterate from there. I'm sure it's not
perfect but at least we have a seemingly working state to start with.

Sorry for the bad surprise.

On Fri, Jul 22, 2011 at 8:21 AM, Chris A. Mattmann (JIRA)
<jira@apache.org> wrote:
>
> =A0 =A0[ https://issues.apache.org/jira/browse/GORA-22?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13=
069581#comment-13069581 ]
>
> Chris A. Mattmann commented on GORA-22:
> ---------------------------------------
>
> One note though: Alexis, it seems like you've replaced and/or added upon =
somehow to the cassandra backend. It was my impression we had one already o=
r that it was functioning/etc. What does your patch do that improves or add=
s to it? Would be great to explain for the benefit of others watching.
>
>> Upgrade cassandra backend to cassandra 0.7
>> ------------------------------------------
>>
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Key: GORA-22
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 URL: https://issues.apache.org/jira/brow=
se/GORA-22
>> =A0 =A0 =A0 =A0 =A0 =A0 Project: Gora
>> =A0 =A0 =A0 =A0 =A0Issue Type: Improvement
>> =A0 =A0 =A0 =A0 =A0Components: storage
>> =A0 =A0Affects Versions: 0.2-incubating
>> =A0 =A0 =A0 =A0 =A0 =A0Reporter: Julien Nioche
>> =A0 =A0 =A0 =A0 =A0 =A0 Fix For: 0.2-incubating
>>
>> =A0 =A0 =A0 =A0 Attachments: gora-cassandra-mapping.xml, gora-cassandra-=
mapping.xml, gora.patch, goraCassandra.patch
>>
>>
>
>
> --
> This message is automatically generated by JIRA.
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>