Hi all, I vote for gora-0.3 with GORA-182 + GORA-170 + GORA-174 (this includes GORA-188) as Henry propose.
GORA-189 should not take much time, but by now we have enough work, so better to leave it out. About GORA-174, Renato is facing Cassandra backend (thanks!! I don't know about Cassandra an was taking me some time to analyze). Accumulo's tests fails, but i guess it is not completely important since still is not working. Am I wrong? If I am, would be good someone to face it... or I will do it, but will take me a bit more time than someone who knows Accumulo. I use the ocasion to ask some things related with HBase (I was looking at Cassandra and didn't mind to wait to ask until later). One much important thing about HBase. I have fixed it locally, and seems to work perfectly, BUT breaks compatibility with former data in one case: If you take your old schema and update a field to be optional ([null, ...]), then you will not be able to read that field properly. Unions add a byte to tell with index in the schema they represent, and expect it, so your data becomes incompatible with the new schema. How do we face it? I thought about this just before Christmas :\ And, of course, thanks Lewis for the bumb =) (and thanks everyone too) Regards, Alfonso Nishikawa 2013/1/3 Renato Marroquín Mogrovejo <[email protected]> > Hi all, > > IMO Gora-174 is the real blocker here. Alfonso and me are trying to > get this fixed (: but any help is more than welcome guys. > We could definitely put the ones you mentioned Lewis as blockers and > the rest can go into 0.4. > Henry you beat me in pressing the send button ;) > > > Renato M. > > 2013/1/3 Lewis John Mcgibbney <[email protected]>: > > Hi Henry > > Is it a serious proposal to bump all of the issues quoted thus far to > > blocker for 0.3 release (the remaining issues can be bumped to 0.4) so we > > have a clear vision for the 0.3 development drive? > > Thanks > > Lewis > > > > On Thu, Jan 3, 2013 at 7:34 PM, Henry Saputra <[email protected] > >wrote: > > > >> Hi Lewis, > >> > >> Thanks for starting this discussions. > >> > >> At least couple of the Jira issues you mentioned before are blocked > >> with GORA-174. > >> > >> I think these are good list of blockers that are "must fix" and should > be > >> resolved before start preparing for 0.3 release. > >> > >> > >> - Henry > >> > >> > >> On Thu, Jan 3, 2013 at 5:42 AM, Lewis John Mcgibbney < > >> [email protected]> wrote: > >> > >> > Hi All, > >> > > >> > Firstly, Happy New Year everyone. I really hope that 2013 is a good > year > >> > for everyone. > >> > > >> > It would be excellent to get a Gora 0.3 release done, however there > are a > >> > couple of blocking issues. As I see it we have the following > >> > > >> > GORA-182 <https://issues.apache.org/jira/browse/GORA-182> Nutch 2.1 > does > >> > not work with gora-cassandra 0.2.1 > >> > > >> > GORA-170 <https://issues.apache.org/jira/browse/GORA-170> Getting a > >> > BufferUnderflowException in class CassandraColumn, method > >> fromByteBuffer() > >> > > >> > GORA-188 <https://issues.apache.org/jira/browse/GORA-188> > >> testSerdeWebPage > >> > failure - PersistentBase#equals() fails with map fields > >> > > >> > GORA-189 <https://issues.apache.org/jira/browse/GORA-189> String > >> > parameters > >> > in generated Persistent subclasses by Compiler -not only Utf8- > >> > > >> > > >> > The thing is that some of these are linked, and I also anticipate > that we > >> > may run into other problems once some/all have been resolved so to > speak. > >> > The purpose of this thread is to attempt to draw up some roadmap for > >> > releasing, and of course to understand what is required in the > >> development > >> > drive for us to reach this target. > >> > > >> > Any input would be excellent. > >> > > >> > Best > >> > > >> > Lewis > >> > > >> > -- > >> > *Lewis* > >> > > >> > > > > > > > > -- > > *Lewis* > -- "Drinking bloody marys all night will make you feel like a corpse in the morning."
