I merged the 'hbase-module' branch into master. With Tomasz' contribution on the GET semantics of HBase, I think that module is looking good enough for a spin in a release candidate or so. I'll bump the old thread on HBase to show an updated status.
2014-03-18 11:36 GMT+01:00 Kasper Sørensen <[email protected]>: > Agreed. So we need mostly just to focus on getting the HBase module a > little bit better so it's "good enough for a first release". I think adding > support for "Get" queries is the most important thing. And also the other > day I showed it to a guy who's doing HBase stuff, and we had a lot of > trouble making it work with his specific version of HBase/Hadoop ... > Wondering if there is a general recipe to set up the dependencies etc. so > that it can be used with multiple backend versions. > > > 2014-03-18 6:44 GMT+01:00 Henry Saputra <[email protected]>: > > I think we should do 4.1.0 then if anyone ask for 4.0.x we could >> generate release as needed. >> >> Thoughts? >> >> - Henry >> >> On Mon, Mar 17, 2014 at 11:08 AM, Kasper Sørensen >> <[email protected]> wrote: >> > Yes we do also have the 4.0.x branch for that. Actually this issue: >> > >> > [METAMODEL-32] - Fixed thread-safety issue in Excel module when tables >> > (sheets) metadata is updated. >> > >> > Could/should be applied on the 4.0.x branch I guess ... It's a >> > non-intrusive but (in concurrent situations) quite critical fix for the >> > excel module. >> > >> > >> > 2014-03-17 18:58 GMT+01:00 Henry Saputra <[email protected]>: >> > >> >> We could go with 4.1.0. >> >> >> >> My 2-cents is that we could reserve something like 4.0.x for emergency >> >> patches like security. >> >> >> >> >> >> - Henry >> >> >> >> On Sat, Mar 15, 2014 at 1:57 AM, Kasper Sørensen >> >> <[email protected]> wrote: >> >> > Hi all, >> >> > >> >> > I feel like we should start planning MetaModel 4.1. In the current >> master >> >> > branch we have a number of nice improvements that I'm really excited >> >> about >> >> > and would like to see released. The main points from changes.txt: >> >> > >> >> > [METAMODEL-11] - New module "MetaModel-spring" which adds a >> convenient >> >> > FactoryBean to produce various types of DataContext objects based on >> >> > externalizable parameters, for Spring framework users. >> >> > [METAMODEL-41] - Added a parser for SimpleTableDef objects >> >> > (SimpleTableDefParser). It parses statements similar to CREATE TABLE >> >> > statements, although without the "CREATE TABLE" prefix. For example: >> foo >> >> > (bar INTEGER, baz VARCHAR) >> >> > [METAMODEL-32] - Fixed thread-safety issue in Excel module when >> tables >> >> > (sheets) metadata is updated. >> >> > [METAMODEL-35] - Improved query rewriting for DB2 when paged queries >> >> > contain ORDER BY clause. >> >> > [METAMODEL-39] - Added pooling of active/used Connections and >> >> > PreparedStatements in JDBC compiled queries. >> >> > >> >> > I think also the HBase module (in a branch) is looking rather OK for >> a >> >> > first release. Maybe we can aim to finish up this module and include >> it. >> >> In >> >> > that case I am all for releasing MetaModel again with a version >> number >> >> like >> >> > 4.1. >> >> > >> >> > Of course we could also go for just a minor release bump like 4.0.1, >> but >> >> I >> >> > think actually the addition of Spring module and potentially also >> HBase >> >> > module is great news. >> >> > >> >> > What do you guys think? >> >> > >> >> > - Kasper >> >> >> > >
