The remote branch approach should work well as we might not be making a lot of changes in the other Metamodel modules or MM-core, I have followed this approach earlier and never faced trouble while merging the branch back on the Master.
regards Sameer On Tue, Jul 30, 2013 at 12:28 PM, Kasper Sørensen < [email protected]> wrote: > Hi everyone, > > Spoke with Sameer who originally started the HBase branch of MetaModel > on the old infrastructure and we thought it would be good to also make > a remote branch in the Git repo for this effort. The HBase module does > pose a few challenges [1], so having it on a branch would allow > developers to work on it without having to deliver a fully fledged > solution from the first patch. > > Is that a good use of a Git remote branch, or do we need some Git > education on this? :-) > > Regards, > Kasper > > [1] One of the distinct challenges of HBase so far has been that the > data types are not directly visible - everything is more or less just > a byte array. Another issue is how we should represent the nested > column structure of HBase (every column has a 'column family'). And > there are probably more... >
