[ 
https://issues.apache.org/jira/browse/GORA-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13864081#comment-13864081
 ] 

Lewis John McGibbney commented on GORA-246:
-------------------------------------------

Hey [~alfonso.nishikawa], it is clear that the changes are non-trivial in 
nature. This is exactly why it has taken so long to get the code in to the 
codebase. I do have some points to make here as well though

 * In essence object creation has changed. We now create objects with an 
additional field __g__ at position 0. This field determines whether an object 
or it's fields are dirty however this field should NOT be flushed or persisted 
to the datastore... the downside of this is that we CANNOT do direct 
comparisons between put and get operations for objects as before... this is why 
I have had to change many tests. 
 * Secondly the interfaces you mention are predominantly within the persistency 
package so I cannot agree that it is all interfaces.

There are of course other issues which you've mentioned but these are some 
things which I thought were important to mention.
On another note, I have a couple of slides regarding my understanding of this 
upgrade an it's effects on our website now from the Dublin meetup. You can 
check them out and we can discuss. The more we can discuss the better IMHO. 
Thank you [~alfonso.nishikawa] :)

> Upgrade to Avro 1.7.X in gora-hbase
> -----------------------------------
>
>                 Key: GORA-246
>                 URL: https://issues.apache.org/jira/browse/GORA-246
>             Project: Apache Gora
>          Issue Type: Sub-task
>          Components: gora-core, gora-hbase
>    Affects Versions: 0.4
>            Reporter: Lewis John McGibbney
>             Fix For: 0.4
>
>         Attachments: GORA-246.patch, GORA-246v2.patch, GORA-246v3.patch, 
> GORA-246v3.patch, GORA-246v4.patch, GORA_246.HBaseDriverTest.patch, 
> GORA_246.HBaseDriverTest.v2.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to