Re: [VOTE] Apache Metamodel release 5.0-RC1

[Tomasz Guziałek]

+1

2017-05-18 8:13 GMT+02:00 Dennis Du Krøger <
dennis.dukro...@humaninference.com>:

> +1
>
> -Original Message-
> From: Kasper Sørensen [mailto:i.am.kasper.soren...@gmail.com]
> Sent: 18. maj 2017 06:50
> To: dev@metamodel.apache.org
> Subject: Re: [VOTE] Apache Metamodel release 5.0-RC1
>
> +1 from me btw :-)
>
> Kasper Sørensen
>
> > On May 17, 2017, at 21:36, Kasper Sørensen  com> wrote:
> >
> > Hi All,
> >
> > Please vote on releasing the following candidate as Apache Metamodel
> version 5.0-RC1.
> >
> > The Git tag to be voted on is MetaModel-5.0-RC1:
> > https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=db4
> > 52eaeebadd13d7a6482f2ff76f3270ed2677a
> >
> > The source artifact to be voted on is:
> > http://repository.apache.org/content/repositories/orgapachemetamodel-1
> > 022/org/apache/metamodel/MetaModel/5.0-RC1/MetaModel-5.0-RC1-source-re
> > lease.zip
> >
> > Parent directory (including MD5, SHA1 hashes etc.) of the source is:
> > http://repository.apache.org/content/repositories/orgapachemetamodel-1
> > 022/org/apache/metamodel/MetaModel/5.0-RC1/
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/kaspersor.asc
> >
> > Release engineer public key id: 1FE1C2F5
> >
> > The staging Maven repository for this release can be found at:
> > http://repository.apache.org/content/repositories/orgapachemetamodel-1
> > 022
> >
> > Please vote on releasing this package as Apache MetaModel 5.0-RC1.
> >
> > The vote is open for 72 hours.
> >
> > [ ] +1 Release this package as Apache MetaModel 5.0-RC1 [ ] -1 Do not
> > release this package because ...
> >
> > Thank you in advance for participating.
> >
> > Regards,
> > Kasper Sørensen
>

Re: Suggestion to release MetaModel 5.0-RC1

[Tomasz Guziałek]

Hi Kasper,

Sounds like a good idea, +1 from me.

Pozdrawiam / Regards / Med venlig hilsen
Tomasz Guziałek

2017-05-17 5:38 GMT+02:00 Kasper Sørensen :

> Bump. Any thoughts?
>
> 2017-05-10 19:21 GMT-07:00 Kasper Sørensen  >:
>
> > Hi all,
> >
> > I think that considerable work has been put into the MetaModel 5.0 branch
> > ("5.x") and while discussions still exist on what the full scope of the
> > release should be, I think what we have is very good and I would
> personally
> > love to start using it. So how about we release a version called 5.0-RC1.
> > This would indicate that many of the breaking changes (update summary
> > returns, java 7 support dropped, use of function types) are available,
> but
> > the scope is still being worked on in terms of feature additions.
> >
> > We should do the release from the 5.x branch and keep the master branch
> > available for the 4.x releases that would still be considered the
> > official/stable branch.
> >
> > Best regards,
> > Kasper
> >
>

Re: [VOTE] Apache Metamodel release 4.6.0

[Tomasz Guziałek]

+1

Pozdrawiam / Regards / Med venlig hilsen
Tomasz Guziałek

2017-02-01 9:44 GMT+01:00 Dennis Du Krøger <
dennis.dukro...@humaninference.com>:

> +1
>
> 
> From: Kasper Sørensen 
> Sent: 31 January 2017 22:25:37
> To: dev@metamodel.apache.org
> Subject: [VOTE] Apache Metamodel release 4.6.0
>
> Hi All,
> Please vote on releasing the following candidate as Apache MetaModel
> version 4.6.0.
>
> The Git tag to be voted on is MetaModel-4.6.0:
> https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=
> 5a5f7505c9ea3e1d38607aeafbc9e8f264cb5538
>
> The source artifact to be voted on is:
> http://repository.apache.org/content/repositories/
> orgapachemetamodel-1021/org/apache/metamodel/MetaModel/4.
> 6.0/MetaModel-4.6.0-source-release.zip
>
> Parent directory (including MD5, SHA1 hashes etc.) of the source is:
> http://repository.apache.org/content/repositories/
> orgapachemetamodel-1021/org/apache/metamodel/MetaModel/4.6.0/
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/kaspersor.asc
>
> Release engineer public key id: 1FE1C2F5
>
> The staging Maven repository for this release can be found at:
> http://repository.apache.org/content/repositories/orgapachemetamodel-1021/
>
> Please vote on releasing this package as Apache MetaModel 4.6.0.
>
> The vote is open for 72 hours.
>
> [ ] +1 Release this package as Apache MetaModel 4.6.0
> [ ] -1 Do not release this package because ...
>
> Thank you in advance for participating.
>
> Regards,
> Kasper
>

Re: [VOTE] Apache Metamodel release 4.5.5

[Tomasz Guziałek]

+1

Pozdrawiam / Regards / Med venlig hilsen
Tomasz Guziałek

2016-11-13 20:46 GMT+01:00 Alberto Rodriguez :

> +1
>
> 2016-11-13 20:32 GMT+01:00 Kasper Sørensen  >:
>
> > +1
> >
> > 2016-11-13 11:32 GMT-08:00 Kasper Sørensen  com
> > >:
> >
> > > Dear everybody,
> > >
> > > Please vote on releasing the following candidate as Apache Metamodel
> > > version 4.5.5.
> > >
> > > The Git tag to be voted on is MetaModel-4.5.5:
> > > https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=
> > > 7587b6aca46c1e5351c79cc60a83503548efd14b
> > >
> > > The source artifact to be voted on is:
> > > http://repository.apache.org/content/repositories/
> > > orgapachemetamodel-1020/org/apache/metamodel/MetaModel/4.
> > > 5.5/MetaModel-4.5.5-source-release.zip
> > >
> > > Parent directory (including MD5, SHA1 hashes etc.) of the source is:
> > > http://repository.apache.org/content/repositories/
> > > orgapachemetamodel-1020/org/apache/metamodel/MetaModel/4.5.5/
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/kaspersor.asc
> > >
> > > Release engineer public key id: 1FE1C2F5
> > >
> > > The staging Maven repository for this release can be found at:
> > > http://repository.apache.org/content/repositories/
> > orgapachemetamodel-1020
> > >
> > > Please vote on releasing this package as Apache MetaModel 4.5.5.
> > >
> > > The vote is open for 72 hours.
> > >
> > > [ ] +1 Release this package as Apache MetaModel 4.5.5
> > > [ ] -1 Do not release this package because ...
> > >
> > > Thank you in advance for participating.
> > >
> > > Regards,
> > > Kasper
> > >
> >
>

Re: Time to release?

[Tomasz Guziałek]

+1

Pozdrawiam / Regards / Med venlig hilsen
Tomasz Guziałek

2016-11-11 22:41 GMT+01:00 Kasper Sørensen :

> Hi guys,
>
> I just noticed that our CHANGES file has a pretty extensive list of
> improvements since our last release [1]. I think we should get this shipped
> pretty soon. What do you all think?
>
> Kasper
>
> [1] Everything under '4.5.5' on
> https://github.com/apache/metamodel/blob/master/CHANGES.md
>

Re: New confluence wiki for MetaModel

[Tomasz Guziałek]

Hello Kasper,

I have just registered as "tomaszguzialek". Thanks in advance!

Pozdrawiam / Regards / Med venlig hilsen
Tomasz Guziałek

2016-08-09 17:21 GMT+02:00 Kasper Sørensen :

> You've been added as an admin Alberto. Other PMCs: Just let me know your
> username then you of course also get admin rights :)
>
> 2016-08-08 23:44 GMT-07:00 Alberto Rodriguez :
>
>> I'm in! My username is ardlema
>>
>> Thank you!
>>
>> 2016-08-09 8:12 GMT+02:00 Kasper Sørensen > >:
>>
>> > Yes, but I think you need to have an account first, I couldn't find you.
>> >
>> > Confluence is not connected automagically to your Apache accounts. You
>> have
>> > to register manually first.
>> >
>> > 2016-08-08 22:59 GMT-07:00 Alberto Rodriguez :
>> >
>> > > Hi Kasper,
>> > >
>> > > Could you please grant me access? I'll help in any way I can.
>> > >
>> > > Kind regards,
>> > >
>> > > Alberto
>> > >
>> > > 2016-08-09 7:46 GMT+02:00 Kasper Sørensen > > com>
>> > > :
>> > >
>> > >> Hi all,
>> > >>
>> > >> We have a brand new wiki for Apache MetaModel, which I hope will be a
>> > >> worthy new home for our living documentation. As you may know, we
>> (and
>> > >> Apache Infra) where facing quite a lot of maintenance/performance
>> issues
>> > >> with the MoinMoin based wiki, so it's now time for us to embrace
>> > >> Confluence
>> > >> which also happens to be superior functionality-wise.
>> > >>
>> > >> I am looking for volunteers who would like to help migrating our
>> content
>> > >> from the existing wiki [1] to the new [2] confluence. And of course
>> also
>> > >> if
>> > >> anyone is interested in making new content (for instance fulfill
>> > >> documentation issue METAMODEL-1110 [3]) then it would be just as
>> > awesome.
>> > >>
>> > >> I am currently admin of the confluence space. Let me know who to
>> make my
>> > >> peers!
>> > >>
>> > >> Best regards,
>> > >> Kasper
>> > >>
>> > >> [1] http://wiki.apache.org/metamodel
>> > >> [2] https://cwiki.apache.org/confluence/display/METAMODEL
>> > >> [3] https://issues.apache.org/jira/browse/METAMODEL-1110
>> > >>
>> > >
>> > >
>> >
>>
>
>

Re: [VOTE] Apache Metamodel release 4.5.4

[Tomasz Guziałek]

+1

2016-08-04 12:03 GMT+02:00 Du Krøger, Dennis <
dennis.dukro...@humaninference.com>:

> +1
>
> -Original Message-
> From: Alberto Rodriguez [mailto:ardl...@gmail.com]
> Sent: 2. august 2016 06:58
> To: dev@metamodel.apache.org
> Subject: Re: [VOTE] Apache Metamodel release 4.5.4
>
> +1
>
> El 2 ago. 2016 6:50, "Kasper Sørensen" 
> escribió:
>
> > Hi All,
> >
> > Please vote on releasing the following candidate as Apache Metamodel
> > version 4.5.4.
> >
> > The Git tag to be voted on is MetaModel-4.5.4:
> >
> > https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=fd6
> > 5c4e9bd408af60fe45b28f7416ac643583248
> >
> > The source artifact to be voted on is:
> >
> > https://repository.apache.org/content/repositories/orgapachemetamodel-
> > 1019/org/apache/metamodel/MetaModel/4.5.4/MetaModel-4.5.4-source-relea
> > se.zip
> >
> > Parent directory (including MD5, SHA1 hashes etc.) of the source is:
> >
> > https://repository.apache.org/content/repositories/orgapachemetamodel-
> > 1019/org/apache/metamodel/MetaModel/4.5.4/
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/kaspersor.asc
> >
> > Release engineer public key id: 1FE1C2F5
> >
> > The staging Maven repository for this release can be found at:
> > https://repository.apache.org/content/repositories/orgapachemetamodel-
> > 1019/
> >
> > Please vote on releasing this package as Apache MetaModel 4.5.4.
> >
> > The vote is open for 72 hours.
> >
> > [ ] +1 Release this package as Apache MetaModel 4.5.4 [ ] -1 Do not
> > release this package because ...
> >
> > Thank you in advance for participating.
> >
> > Regards,
> > Kasper Sørensen
> >
>

Re: [VOTE] Release MetaModel 4.5.3

[Tomasz Guziałek]

+1

Pozdrawiam / Regards / Med venlig hilsen
Tomasz Guziałek

2016-05-16 20:43 GMT+02:00 Kasper Sørensen :

> And here's me kickiing off the jam:
>
> +1
>
> 2016-05-16 11:43 GMT-07:00 Kasper Sørensen  >:
> > Hi All,
> >
> > Please vote on releasing the following candidate as Apache Metamodel
> > version 4.5.3.
> >
> > The Git tag to be voted on is MetaModel-4.5.3:
> >
> https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=1a1dc0d8570b6d02579e43041601293868358817
> >
> > The source artifact to be voted on is:
> >
> http://repository.apache.org/content/repositories/orgapachemetamodel-1018/org/apache/metamodel/MetaModel/4.5.3/MetaModel-4.5.3-source-release.zip
> >
> > Parent directory (including MD5, SHA1 hashes etc.) of the source is:
> >
> http://repository.apache.org/content/repositories/orgapachemetamodel-1018/org/apache/metamodel/MetaModel/4.5.3/
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/kaspersor.asc
> >
> > Release engineer public key id: 1FE1C2F5
> >
> > The staging Maven repository for this release can be found at:
> >
> http://repository.apache.org/content/repositories/orgapachemetamodel-1018
> >
> > Please vote on releasing this package as Apache MetaModel 4.5.3.
> >
> > The vote is open for 72 hours.
> >
> > [ ] +1 Release this package as Apache MetaModel 4.5.3
> > [ ] -1 Do not release this package because ...
> >
> > Thank you in advance for participating.
> >
> > Regards,
> > Kasper Sørensen
>

Re: Review Request 46902: METAMODEL-159 : DataContextFactory misses methods to create HBase and POJO data contexts

[Tomasz Guziałek]

Hi Sagar,

Now a committer needs to take the patch and apply it on master. I will take
it from here. Thanks for your contribution!

Pozdrawiam / Regards / Med venlig hilsen
Tomasz Guziałek

2016-05-02 22:16 GMT+02:00 Sagar Gandhi :

> Hi  Tomasz,
>
> can you please guide me how to proceed for check-in ? . I am not a
> committer, what are the steps I need to perform to help committer check-in
> this patch ?
>
>
> Thanks ,
> Mr.Sagar Gandhi,
> Pune.
> (+91)9028440503
>
>
> > Subject: Re: Review Request 46902: METAMODEL-159 : DataContextFactory
> misses methods to create HBase and POJO data contexts
> > From: gandhi.sa...@live.com
> > To: gandhi.sa...@live.com; tom...@guzialek.info;
> dev@metamodel.apache.org
> > Date: Mon, 2 May 2016 20:13:37 +
>
> >
> >
> > ---
> > This is an automatically generated e-mail. To reply, visit:
> > https://reviews.apache.org/r/46902/
> > ---
> >
> > (Updated May 2, 2016, 8:13 p.m.)
> >
> >
> > Review request for MetaModel.
> >
> >
> > Changes
> > ---
> >
> > Technical error viewing diff 3
> >
> >
> > Repository: metamodel
> >
> >
> > Description
> > ---
> >
> > Bug Description :
> > Every DataContext implementation is represented in the
> DataContextFactory with a method for creating such DataContext. However,
> there are no methods for creating HBaseDataContext and PojoDataContext.
> >
> > Solution :
> > Created methods for HBase and Pojo. Added different overloaded methods
> for overloaded constructors.
> >
> >
> > Diffs (updated)
> > -
> >
> > full/src/main/java/org/apache/metamodel/DataContextFactory.java 2b3dae2
> >
> > Diff: https://reviews.apache.org/r/46902/diff/
> >
> >
> > Testing
> > ---
> >
> >
> > Thanks,
> >
> > Sagar Gandhi
> >
>

Re: [VOTE] Apache Metamodel release 4.5.1

[Tomasz Guziałek]

+1

Pozdrawiam / Regards / Med venlig hilsen
Tomasz Guziałek

2016-02-09 14:11 GMT+01:00 Du Krøger, Dennis <
dennis.dukro...@humaninference.com>:

> +1
>
> -Original Message-
> From: Kasper Sørensen [mailto:i.am.kasper.soren...@gmail.com]
> Sent: 9. februar 2016 14:11
> To: dev@metamodel.apache.org
> Subject: [VOTE] Apache Metamodel release 4.5.1
>
> Hi All,
>
> Please vote on releasing the following candidate as Apache Metamodel
> version 4.5.1
>
> The Git tag to be voted on is MetaModel-4.5.1:
>
> https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=f4d6de53803a47e6b6ad67f8043c073da3b5fbff
>
> The source artifact to be voted on is:
>
> https://repository.apache.org/content/repositories/orgapachemetamodel-1016/org/apache/metamodel/MetaModel/4.5.1/MetaModel-4.5.1-source-release.zip
>
> Parent directory (including MD5, SHA1 hashes etc.) of the source is:
>
> https://repository.apache.org/content/repositories/orgapachemetamodel-1016/org/apache/metamodel/MetaModel/4.5.1/
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/kaspersor.asc
>
> Release engineer public key id: 1FE1C2F5
>
> The staging Maven repository for this release can be found at:
> https://repository.apache.org/content/repositories/orgapachemetamodel-1016/
>
> Please vote on releasing this package as Apache MetaModel 4.5.1.
>
> The vote is open for 72 hours.
>
> [ ] +1 Release this package as Apache MetaModel 4.5.1 [ ] -1 Do not
> release this package because ...
>
> Thank you in advance for participating.
>
> Regards,
> Kasper Sørensen
>

Re: [VOTE] Apache Metamodel release 4.5.0

[Tomasz Guziałek]

+1

Pozdrawiam / Regards / Med venlig hilsen
Tomasz Guziałek

2015-12-14 16:51 GMT+01:00 Ankit Kumar :

> +1
>
> ~Ankit
>
> > On 14 Dec 2015, at 12:48, Du Krøger, Dennis
>  wrote:
> >
> > +1
> >
> > -Original Message-
> > From: Alberto Rodriguez [mailto:arodrig...@stratio.com]
> > Sent: 14. december 2015 12:47
> > To: dev@metamodel.apache.org
> > Subject: Re: [VOTE] Apache Metamodel release 4.5.0
> >
> > +1
> >
> > Alberto Rodriguez
> >
> > Vía de las dos Castillas, 33, Ática 4, 3ª Planta
> > 28224 Pozuelo de Alarcón, Madrid
> > Tel: +34 91 828 6473 // www.stratio.com // *@stratiobd
> > <https://twitter.com/StratioBD>*
> >
> > 2015-12-14 12:44 GMT+01:00 Kasper Sørensen <
> i.am.kasper.soren...@gmail.com>:
> >
> >> Hi All,
> >>
> >> Please vote on releasing the following candidate as Apache Metamodel
> >> version 4.5.0.
> >>
> >> The Git tag to be voted on is MetaModel-4.5.0:
> >>
> >> https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=8a5
> >> 24992fe8501ac4c189fc403030e3cb769f171
> >>
> >> The source artifact to be voted on is:
> >>
> >> http://repository.apache.org/content/repositories/orgapachemetamodel-1
> >> 015/org/apache/metamodel/MetaModel/4.5.0/MetaModel-4.5.0-source-releas
> >> e.zip
> >>
> >> Parent directory (including MD5, SHA1 hashes etc.) of the source is:
> >>
> >> http://repository.apache.org/content/repositories/orgapachemetamodel-1
> >> 015/org/apache/metamodel/MetaModel/4.5.0
> >>
> >> Release artifacts are signed with the following key:
> >> https://people.apache.org/keys/committer/kaspersor.asc
> >>
> >> Release engineer public key id: 1FE1C2F5
> >>
> >> The staging Maven repository for this release can be found at:
> >> http://repository.apache.org/content/repositories/orgapachemetamodel-1
> >> 015
> >>
> >> Please vote on releasing this package as Apache MetaModel 4.5.0.
> >>
> >> The vote is open for 72 hours.
> >>
> >> [ ] +1 Release this package as Apache MetaModel 4.5.0 [ ] -1 Do not
> >> release this package because ...
> >>
> >> Thank you in advance for participating.
> >>
> >> Regards,
> >> Kasper Sørensen
> >>
>

Re: How to use joins using apache meta modes

[Tomasz Guziałek]

True. I have always used the version with WHERE clause, so completely
missed innerJoin, leftJoin and rightJoin:

dataContext.query().from("tableA").innerJoin("tableB").on("columnFromA",
"columnFromB").selectAll().execute();

Pozdrawiam / Regards / Med venlig hilsen
Tomasz Guziałek

2015-12-06 12:39 GMT+01:00 Kasper Sørensen :

> Well, a first-class join is also possible. Just use the query API... I'm
> not even sure what the question is here Arunkumar??
>
> 2015-12-05 23:41 GMT+01:00 Tomasz Guziałek :
>
> > Hello Arunkumar,
> >
> > MetaModel does not have specialialized constructs for JOIN operations.
> Try
> > writing your query in such a manner:
> >
> >
> >
> dataContext.query().from("tableA").and("tableB").selectAll().where("joinColumnFromA").eq("joinColumnFromB").executeQuery();
> >
> > Pozdrawiam / Regards / Med venlig hilsen
> > Tomasz Guziałek
> >
> > 2015-12-04 11:19 GMT+01:00 Arunkumar Pillai :
> >
> > > Please help in executing the following queries
> > >
> > > SELECT a.id as ID,
> > >  a.a_name as a_NAME ,b.user_name
> > >  FROM TB_a a inner join TB_b b on b.id = a.id
> > >  WHERE a.active = 1
> > >
> > >
> > > I'm not finding any examples for joins
> > > or directly converting the sql queries to meta model query
> > >
> > > --
> > > Thanks and Regards
> > > Arun
> > >
> >
>

Re: How to use joins using apache meta modes

[Tomasz Guziałek]

Hello Arunkumar,

MetaModel does not have specialialized constructs for JOIN operations. Try
writing your query in such a manner:

dataContext.query().from("tableA").and("tableB").selectAll().where("joinColumnFromA").eq("joinColumnFromB").executeQuery();

Pozdrawiam / Regards / Med venlig hilsen
Tomasz Guziałek

2015-12-04 11:19 GMT+01:00 Arunkumar Pillai :

> Please help in executing the following queries
>
> SELECT a.id as ID,
>  a.a_name as a_NAME ,b.user_name
>  FROM TB_a a inner join TB_b b on b.id = a.id
>  WHERE a.active = 1
>
>
> I'm not finding any examples for joins
> or directly converting the sql queries to meta model query
>
> --
> Thanks and Regards
> Arun
>

Re: [DISCUSS] Checking-in "red" unit tests reproducing bugs.

[Tomasz Guziałek]

I personally don't like working with diffs. But will try to make friends
with them, sounds like a reasonable idea to use them for bug reproducing
purposes.

Pozdrawiam / Regards / Med venlig hilsen
Tomasz Guziałek

2015-11-29 9:30 GMT+01:00 Kasper Sørensen :

> I think that also sounds like a good idea. Agree that rarely the branch is
> needed.
>
> 2015-11-28 13:09 GMT+01:00 Du Krøger, Dennis <
> dennis.dukro...@humaninference.com>:
>
> > Hmmm... How about just attaching it as a diff to the related issue
> > description?
> >
> > Since there is no actual functionality, "only" a demonstration of a
> > problem, I'm not sure a branch is the best place to keep these.
> >
> > /Dennis
> > 
> > From: Kasper Sørensen 
> > Sent: Saturday, November 28, 2015 10:42
> > To: dev@metamodel.apache.org
> > Subject: Re: [DISCUSS] Checking-in "red" unit tests reproducing bugs.
> >
> > Good discussion point Tomasz. From my point of view, it is very nice to
> > reproduce a bug with a unittest. If it is trivial I usually simply inline
> > the unittest in the JIRA issue in a {code} block. But for committers it's
> > certainly also possible that we create branches on the central/shared
> repo.
> > I agree that creating such a branch on a fork is a bit messy in the long
> > run. Regardless how it's done - I think demonstrating a bug with a
> failing
> > unittest is a great practice and we should encourage that a lot. I would
> be
> > happy to agree on making it standard practice to make remote branches on
> > the MM central git repo to represent such bug tests. Maybe we should just
> > always prefix such branch names with "bug/..." or something like that.
> >
> > 2015-11-28 10:31 GMT+01:00 Tomasz Guziałek :
> >
> > > Hello everyone,
> > >
> > > I would like to discuss with you what would be the preferred way to
> > > checking-in code that is a unit test reproducing an issue, but not
> fixing
> > > it.
> > >
> > > I created branches in my own fork of MetaModel with failing unit tests
> > for
> > > several tickets. Currently only one of them is still open and no fix is
> > on
> > > the way:
> > > https://issues.apache.org/jira/browse/METAMODEL-167
> > >
> > > Such branches should not be merged into master as the build will fail,
> > but
> > > they are a valuable documentation of the issues. As mentioned, the
> > branches
> > > live only in a fork, but maybe we should consider checking-in them into
> > the
> > > main repo?
> > >
> > > I am starting the discussion right now, because I would like to nuke my
> > own
> > > fork soon. I made some commits on my fork's master branch by mistake
> and
> > it
> > > keeps polluting subsequent branches I create. I know that is probably
> > > killing the fly with a bazooka, but it will save me much time carefully
> > > fixing the mess.
> > >
> > > I would love to hear your suggestions regarding the process how we deal
> > > with "red" branches in MetaModel - no doubt that the situatio of
> > > reproducing bugs with unit tests will come up again in the nearest
> > future.
> > >
> >
>

[DISCUSS] Checking-in "red" unit tests reproducing bugs.

[Tomasz Guziałek]

Hello everyone,

I would like to discuss with you what would be the preferred way to
checking-in code that is a unit test reproducing an issue, but not fixing
it.

I created branches in my own fork of MetaModel with failing unit tests for
several tickets. Currently only one of them is still open and no fix is on
the way:
https://issues.apache.org/jira/browse/METAMODEL-167

Such branches should not be merged into master as the build will fail, but
they are a valuable documentation of the issues. As mentioned, the branches
live only in a fork, but maybe we should consider checking-in them into the
main repo?

I am starting the discussion right now, because I would like to nuke my own
fork soon. I made some commits on my fork's master branch by mistake and it
keeps polluting subsequent branches I create. I know that is probably
killing the fly with a bazooka, but it will save me much time carefully
fixing the mess.

I would love to hear your suggestions regarding the process how we deal
with "red" branches in MetaModel - no doubt that the situatio of
reproducing bugs with unit tests will come up again in the nearest future.

Re: Primary Lookup for Mongo

[Tomasz Guziałek]

Hello Misha and Kasper,

I have confirmed the issue and reported a bug in JIRA together with a unit
test reproducing the problem:
https://issues.apache.org/jira/browse/METAMODEL-211

Pozdrawiam / Regards / Med venlig hilsen
Tomasz Guziałek

2015-11-24 19:17 GMT+01:00 Kasper Sørensen :

> Hi Misha,
>
> Maybe you could try and put a breakpoint in MongoDbDataContext method
> 'executePrimaryKeyLookupQuery'. And then run your scenario in debug mode.
>
> Kasper
>
> 2015-11-24 17:18 GMT+01:00 mishadoff :
>
> > Hello all!
> >
> > I have started using apache metamodel but got stuck in prototyping query
> > for mongo which uses primary lookup.
> > I do not want to duplicate a lot of data so I have already created a
> > question on StackOverflow
> >
> http://stackoverflow.com/questions/33897861/apache-metamodel-select-by-id-from-mongodb
> > <
> >
> http://stackoverflow.com/questions/33897861/apache-metamodel-select-by-id-from-mongodb
> > >
> >
> > Could you please advise me what I am doing wrong or it’s a bug in
> > MongoDBDataContext?
> >
> > Thanks.
> >
> > — Misha
>

Re: Need Help in retrieving columns having NULL Values

[Tomasz Guziałek]

Hello Arunkumar,

You cannot call toString method on a NULL value, you can only do it when
there is a real object assigned to the variable (unless Scala or whatever
language you are using has some special treatment for such situation). Try:

while (ds.next()) {
val row:Row= ds.getRow()
val column1= row.getValue(0)
val column2= row.getValue(1)
   if (column1 != null) {
val column1StrVal = column1.toString
   }
   if (column2 != null) {
val column2StrVal = column2.toString
   }
}

BTW I also fixed indexes in the getValue calls - there were two times 0. I
hope that helps!

Pozdrawiam / Regards / Med venlig hilsen
Tomasz Guziałek

2015-11-25 5:59 GMT+01:00 Arunkumar Pillai :

> Hi
>
> I'm using select query to fetch records and my code is as follows
>
>  val connection = DB.getConnection()
> val dataContext:DataContext =
> DataContextFactory.createJdbcDataContext(connection)
>  var query:Query =
>
> dataContext.query().from("TABLE_NAME").select("COLUMN1").select("COLUMN2").toQuery
>
>
>   val ds:DataSet= dataContext.executeQuery(query)
>
>   while (ds.next()) {
> val row:Row= ds.getRow()
> val column1= row.getValue(0).toString
> val column2= row.getValue(0).toString
>
>   }
>
>
>
> if any of the value is NULL then it breaks there.  Any suggestions or help
> would be highly appreciated.
>

Re: [VOTE] Apache Metamodel release 4.4.1 - take two!

[Tomasz Guziałek]

+1

Pozdrawiam / Regards / Med venlig hilsen
Tomasz Guziałek

2015-10-27 10:16 GMT+01:00 Kasper Sørensen :

> Hi All,
>
> We've corrected the issue we saw before, and are now ready for another vote
> on MM 4.4.1...
>
> Please vote on releasing the following candidate as Apache Metamodel
> version 4.4.1.
>
> The Git tag to be voted on is MetaModel-4.4.1:
>
> https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=6409a5b9df2b48e05b2f8365186ab0c8f5cea1da
>
> The source artifact to be voted on is:
>
> http://repository.apache.org/content/repositories/orgapachemetamodel-1014/org/apache/metamodel/MetaModel/4.4.1/MetaModel-4.4.1-source-release.zip
>
> Parent directory (including MD5, SHA1 hashes etc.) of the source is:
>
> http://repository.apache.org/content/repositories/orgapachemetamodel-1014/org/apache/metamodel/MetaModel/4.4.1/
>
> NOTE! This is the first time we build also the 'packaged'/binary
> distribution also as part of the release. Here is the link for that
> artifact:
>
> https://repository.apache.org/content/repositories/orgapachemetamodel-1014/org/apache/metamodel/MetaModel-full/4.4.1/MetaModel-full-4.4.1-packaged.zip
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/kaspersor.asc
>
> Release engineer public key id: 1FE1C2F5
>
> The staging Maven repository for this release can be found at:
> http://repository.apache.org/content/repositories/orgapachemetamodel-1014
>
> Please vote on releasing this package as Apache MetaModel 4.4.1.
>
> The vote is open for 72 hours.
>
> [ ] +1 Release this package as Apache MetaModel 4.4.1
> [ ] -1 Do not release this package because ...
>
> Thank you in advance for participating.
>
> Regards,
> Kasper Sørensen
>

Re: [VOTE] Apache Metamodel release 4.4.1

[Tomasz Guziałek]

+1

Pozdrawiam / Regards / Med venlig hilsen
Tomasz Guziałek

2015-10-26 15:10 GMT+01:00 Alberto Rodriguez :

> +1
>
> Alberto Rodríguez
>
>
> <http://www.stratio.com/>
> Vía de las Dos Castillas, 33, Ática 4, 3ª Planta.
> 28224 Pozuelo de Alarcón, Madrid
> Tel: +34 91 352 59 42 // *@stratiobd <https://twitter.com/StratioBD>*
>
> 2015-10-26 14:50 GMT+01:00 Pesu, Claudia  >:
>
> >  +1
> >
> > > On Oct 26, 2015, at 2:43 PM, Kasper Sørensen <
> > i.am.kasper.soren...@gmail.com> wrote:
> > >
> > > Hi All,
> > >
> > > Please vote on releasing the following candidate as Apache Metamodel
> > > version 4.4.1.
> > >
> > > The Git tag to be voted on is MetaModel-4.4.1:
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=424e918fdb08475b3dbf784ffba00be53b7675e3
> > >
> > > The source artifact to be voted on is:
> > >
> >
> http://repository.apache.org/content/repositories/orgapachemetamodel-1013/org/apache/metamodel/MetaModel/4.4.1/MetaModel-4.4.1-source-release.zip
> > >
> > > Parent directory (including MD5, SHA1 hashes etc.) of the source is:
> > >
> >
> http://repository.apache.org/content/repositories/orgapachemetamodel-1013/org/apache/metamodel/MetaModel/4.4.1/
> > >
> > > NOTE! This is the first time we build also the 'packaged'/binary
> > > distribution also as part of the release. Here is the link for that
> > > artifact:
> > >
> >
> https://repository.apache.org/content/repositories/orgapachemetamodel-1013/org/apache/metamodel/MetaModel-full/4.4.1/MetaModel-full-4.4.1-packaged.zip
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/kaspersor.asc
> > >
> > > Release engineer public key id: 1FE1C2F5
> > >
> > > The staging Maven repository for this release can be found at:
> > >
> >
> http://repository.apache.org/content/repositories/orgapachemetamodel-1013
> > >
> > > Please vote on releasing this package as Apache MetaModel 4.4.1.
> > >
> > > The vote is open for 72 hours.
> > >
> > > [ ] +1 Release this package as Apache MetaModel 4.4.1
> > > [ ] -1 Do not release this package because ...
> > >
> > > Thank you in advance for participating.
> > >
> > > Regards,
> > > Kasper Sørensen
> >
> >
>

RE: Who's going to ApacheCon or Apache Big Data

[Tomasz Guziałek]

Hello Kasper and Alberto,

Kasper, great to hear your talk has been accepted! I am coming to both Apache 
Big Data and Apache Con, so you have already a spectator ;). Here is the link 
to the talk in the official conference schedule: http://sched.co/3zzw

Alberto, are you coming to the conference at least as a visitor? It would be 
great to meet you there.

Best regards,
Tomasz

-Original Message-
From: Alberto Rodriguez [mailto:ardl...@gmail.com] 
Sent: Thursday, July 30, 2015 09:50
To: dev@metamodel.apache.org
Subject: Re: Who's going to ApacheCon or Apache Big Data

Hi Kasper,

I also sent a talk to the Apache Con Core but it was finally rejected. I wanted 
to talk about how are we using MetaModel to create our data visualization tool. 
I'm very glad that your talk has been selected and you are talking about MM in 
the conference!!

If you want to talk about MM use cases do not hesitate to contact me to get 
more info about how are we using the project.

2015-07-30 9:13 GMT+02:00 Kasper Sørensen :

> Hi all,
>
> Since I am going (and doing a talk on MetaModel btw) to the Apache Big 
> Data event 2015 in Budapest I was wondering if anybody else in here is 
> joining?
> Would be awesome to meet up!
>
> Kasper
>

Re: [VOTE] Apache Metamodel release 4.3.4

[Tomasz Guziałek]

Hello Alberto,

That's alright :). Thanks for taking the trouble of releasing, good job!

Best regards,
Tomasz


Sent from Samsung Mobile


 Original message 
From: Alberto Rodriguez
Date:24/05/2015 10:56 (GMT+00:00)
To: dev@metamodel.apache.org
Subject: Re: [VOTE] Apache Metamodel release 4.3.4

Hi all,

please ignore my previous email. I've just double-checked the MM PMC list
and found out that Tomasz Guziałek is also a member. I'm so sorry Tomasz,
is my first time as release engineer and didn't know all the PMC members :(

Kind regards,

Alberto Rodriguez

2015-05-24 11:41 GMT+02:00 Alberto Rodriguez :

> Hi everyone,
>
> the VOTE for releasing Apache MetaModel 4.3.4 is about to finish and so
> far we have 7 +1's but just 2 binding votes:
>
> Dennis Du Krøger
> Alberto Rodriguez *
> Ashish Mukherjee
> Tomasz Guziałek
> Hosur Narahari
> Alessandro Portosa
> Kasper Sørensen *
>
> * - indicates PMC
>
> As per the ASF voting rules <http://www.apache.org/foundation/voting.html>,
> I think at least three PMC members must vote affirmatively for release.
>
> I will keep open the voting process for a while to wait for another PMC
> members.
>
> Kind regards,
>
> Alberto Rodriguez
>
> 2015-05-22 10:00 GMT+02:00 Kasper Sørensen  >:
>
>> +1
>>
>> Everything looks good (great) now!
>>
>> 2015-05-22 9:21 GMT+02:00 Alberto Rodriguez :
>>
>> > Hi Kasper,
>> >
>> > I've just added my public key to the KEYS file. Thank you again for your
>> > help.
>> >
>> > Kind regards,
>> >
>> >
>> > Alberto Rodríguez
>> >
>> >
>> > <http://www.stratio.com/>
>> > Vía de las Dos Castillas, 33, Ática 4, 3ª Planta.
>> > 28224 Pozuelo de Alarcón, Madrid
>> > Tel: +34 91 352 59 42 // *@stratiobd <https://twitter.com/StratioBD>*
>> >
>> > 2015-05-22 8:55 GMT+02:00 Kasper Sørensen <
>> i.am.kasper.soren...@gmail.com
>> > >:
>> >
>> > > Hi Alberto,
>> > >
>> > > I believe you should have commit access via SVN to the KEYS file.
>> You're
>> > > supposed to add your public key in it yourself. I realize this is
>> missing
>> > > from the release guide, so I will add it.
>> > >
>> > > In the mean time the svn URL is
>> > > https://dist.apache.org/repos/dist/release/metamodel/KEYS
>> > >
>> > > Kasper
>> > >
>> > >
>> > >
>> > > 2015-05-22 8:49 GMT+02:00 Kasper Sørensen <
>> > i.am.kasper.soren...@gmail.com
>> > > >:
>> > >
>> > > > Honestly cannot remember. But I will take a look at it and get back.
>> > > >
>> > > > 2015-05-22 8:15 GMT+02:00 Alberto Rodriguez :
>> > > >
>> > > >> Hi Kasper, yesterday I uploaded my PGP public key fingerprint to my
>> > ASF
>> > > >> account through id.apache.org.
>> > > >>
>> > > >> Is there anything left to do?
>> > > >>
>> > > >> 2015-05-21 19:01 GMT+02:00 Kasper Sørensen <
>> > > >> i.am.kasper.soren...@gmail.com>:
>> > > >>
>> > > >> > After importing the provided .asc file [1], the signature checks
>> out
>> > > >> fine.
>> > > >> > I guess we still need to update KEYS file.
>> > > >> >
>> > > >> > [1] https://people.apache.org/keys/committer/ardlema.asc
>> > > >> >
>> > > >> > 2015-05-21 18:48 GMT+02:00 Kasper Sørensen <
>> > > >> i.am.kasper.soren...@gmail.com
>> > > >> > >:
>> > > >> >
>> > > >> >> -0
>> > > >> >>
>> > > >> >> Alberto, I am missing your public key in
>> > > >> >> http://www.apache.org/dist/metamodel/KEYS ... I think you have
>> > > commit
>> > > >> >> rights to add that yourself?
>> > > >> >> Also trying to verify the signature of the files ... so long
>> since
>> > I
>> > > >> had
>> > > >> >> to do this :-)
>> > > >> >>
>> > > >> >> Kasper
>> > > >> >>
>> > > >> >>
>> > > >> >> 2015-05-21 17:37 GMT+02:00 Alessandro Portosa <
>> > > >

RE: [VOTE] Apache Metamodel release 4.3.4

[Tomasz Guziałek]

+1

Best regards,
Tomasz

-Original Message-
From: Ashish Mukherjee [mailto:ashish.mukher...@gmail.com] 
Sent: Thursday, May 21, 2015 12:03
To: dev@metamodel.apache.org
Subject: Re: [VOTE] Apache Metamodel release 4.3.4

+1

On Thu, May 21, 2015 at 3:30 PM, Alberto Rodriguez 
wrote:

> +1
>
> 2015-05-21 11:59 GMT+02:00 Dennis Du Krøger <
> dennis.dukro...@humaninference.com>:
>
> > +1
> >
> > -Original Message-
> > From: Alberto Rodriguez [mailto:ardl...@gmail.com]
> > Sent: 21. maj 2015 11:58
> > To: dev@metamodel.apache.org
> > Subject: [VOTE] Apache Metamodel release 4.3.4
> >
> > Hi All,
> >
> > Please vote on releasing the following candidate as Apache Metamodel 
> > version 4.3.4.
> >
> > The Git tag to be voted on is MetaModel-4.3.4:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=11c
> 5e8cf12c235904056b03de829d0a51f411662
> >
> > The source artifact to be voted on is:
> >
> >
> https://repository.apache.org/content/repositories/orgapachemetamodel-
> 1008/org/apache/metamodel/MetaModel/4.3.4/MetaModel-4.3.4-source-relea
> se.zip
> >
> > Parent directory (including MD5, SHA1 hashes etc.) of the source is:
> >
> >
> http://repository.apache.org/content/repositories/orgapachemetamodel-1
> 008/org/apache/metamodel/MetaModel/4.3.4/
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/ardlema.asc
> >
> > Release engineer public key id: 1194EFEB
> >
> > The staging Maven repository for this release can be found at:
> >
> http://repository.apache.org/content/repositories/orgapachemetamodel-1
> 008
> >
> > Please vote on releasing this package as Apache MetaModel 4.3.4.
> >
> > The vote is open for 72 hours.
> >
> > [ ] +1 Release this package as Apache MetaModel 4.3.4 [ ] -1 Do not 
> > release this package because ...
> >
> > Thank you in advance for participating.
> >
> > Regards,
> >
> > Alberto Rodriguez
> >
>

Re: Article on HadoopSphere:

[Tomasz Guziałek]

Cool stuff!

Regards,
Tomasz

> On 07 Apr 2015, at 20:47, Kasper Sørensen  
> wrote:
> 
> Hi all,
> 
> If you wanna see MetaModel in the (online) press, here's a goodie for ya!
> Just published :-)
> 
> http://www.hadoopsphere.com/2015/04/exploring-varied-data-stores-with.html
> 
> Thanks to HadoopSphere for the interest!
> 
> Kasper

RE: [VOTE] Apache Metamodel incubating release 4.3.2

[Tomasz Guziałek]

+1

Regards,
Tomasz

-Original Message-
From: Dennis Du Krøger [mailto:dennis.dukro...@humaninference.com] 
Sent: Friday, March 13, 2015 10:45
To: dev@metamodel.apache.org
Subject: RE: [VOTE] Apache Metamodel incubating release 4.3.2

+1

-Original Message-
From: Kasper Sørensen [mailto:i.am.kasper.soren...@gmail.com] 
Sent: 12. marts 2015 10:54
To: dev@metamodel.apache.org
Subject: [VOTE] Apache Metamodel incubating release 4.3.2

Hi All,

Please vote on releasing the following candidate as Apache Metamodel version 
4.3.2.

The Git tag to be voted on is MetaModel-4.3.2:
https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=2aacf8f23eef661e5dac710479ae853dfc27019d

The source artifact to be voted on is:
https://repository.apache.org/content/repositories/orgapachemetamodel-1006/org/apache/metamodel/MetaModel/4.3.2/MetaModel-4.3.2-source-release.zip

Parent directory (including MD5, SHA1 hashes etc.) of the source is:
https://repository.apache.org/content/repositories/orgapachemetamodel-1006/org/apache/metamodel/MetaModel/4.3.2

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/kaspersor.asc

Release engineer public key id: 1FE1C2F5

The staging Maven repository for this release can be found at:
https://repository.apache.org/content/repositories/orgapachemetamodel-1006

Please vote on releasing this package as Apache MetaModel 4.3.2.

The vote is open for 72 hours.

[ ] +1 Release this package as Apache MetaModel 4.3.2 [ ] -1 Do not release 
this package because ...

Thank you in advance for participating.

Regards,
Kasper Sørensen

RE: [DISCUSS] Documentation improvements?

[Tomasz Guziałek]

A new page in the Wiki is now online: 
https://wiki.apache.org/metamodel/GettingStartedNewConnectors

Best regards,
Tomasz

-Original Message-
From: Tomasz Guziałek [mailto:tomasz.guzia...@humaninference.com] 
Sent: Wednesday, January 21, 2015 12:47
To: dev@metamodel.apache.org
Subject: RE: [DISCUSS] Documentation improvements?

Thanks, it is working now :).

Best regards,
Tomasz

-Original Message-
From: Kasper Sørensen [mailto:i.am.kasper.soren...@gmail.com]
Sent: Wednesday, January 21, 2015 12:43
To: dev@metamodel.apache.org
Subject: Re: [DISCUSS] Documentation improvements?

Figure it out :-) You have access now.

2015-01-21 12:38 GMT+01:00 Kasper Sørensen :

> I've been granted admin rights now ... trying to figure out how to 
> give you access to write new pages Tomasz ... :-)
>
> 2015-01-20 16:47 GMT+01:00 Tomasz Guziałek <
> tomasz.guzia...@humaninference.com>:
>
>> I forgot about it actually. However, my INFRA ticket is still unresolved:
>> https://issues.apache.org/jira/browse/INFRA-8902 Hopefully, some of 
>> you can add me as a contributor to the Wiki when you get your admin rights 
>> back.
>>
>> Best regards,
>> Tomasz
>>
>> -Original Message-
>> From: Kasper Sørensen [mailto:i.am.kasper.soren...@gmail.com]
>> Sent: Wednesday, January 14, 2015 23:22
>> To: dev@metamodel.apache.org
>> Subject: Re: [DISCUSS] Documentation improvements?
>>
>> Hi everybody,
>>
>> I know it's been a while, but I felt like bumping this topic. I was 
>> thinking a bit about "what's most important for MetaModel at this point"
>> and I think documentation is high on my list, if not highest. If the 
>> wiki is in any way blocking work (Tomasz?) then please raise it here 
>> and let's get it fixed. And while waiting for such a thing we should 
>> still be able to work on the docs - either via emails, documentation 
>> in .md files or whatever.
>>
>> Cheers,
>> Kasper
>>
>> 2014-12-18 21:20 GMT+01:00 Kasper Sørensen <
>> i.am.kasper.soren...@gmail.com>:
>>
>> > Javadocs are now available at:
>> >
>> > http://metamodel.apache.org/apidocs/3.4.1
>> >
>> > or via this redirect url that we can always make point to new versions:
>> > http://metamodel.apache.org/apidocs/current
>> >
>> > Kasper
>> >
>> >
>> > 2014-12-17 17:02 GMT+01:00 Henry Saputra :
>> >>
>> >> Hi Tomasz,
>> >>
>> >> Hmm somehow I also do not have admin access to add individual to 
>> >> edit access, unfortunately you need to file ASF INFRA ticket to 
>> >> get help on this =(
>> >>
>> >> - Henry
>> >>
>> >> On Wed, Dec 17, 2014 at 3:33 AM, Tomasz Guziałek 
>> >>  wrote:
>> >> > I registered myself at the Wiki, but I believe I do not have the 
>> >> > rights
>> >> for editing. Henry, is that you who can fix that for me? My 
>> >> username is "tomaszguzialek". Thank you!
>> >> >
>> >> > Best regards,
>> >> > Tomasz
>> >> >
>> >> > -Original Message-
>> >> > From: Kasper Sørensen [mailto:i.am.kasper.soren...@gmail.com]
>> >> > Sent: Tuesday, December 16, 2014 20:04
>> >> > To: dev@metamodel.apache.org
>> >> > Subject: Re: [DISCUSS] Documentation improvements?
>> >> >
>> >> > Hi Tomasz,
>> >> >
>> >> > Good info too! I like the analogies to existing implementations
>> >> > - I can
>> >> imagine these are valueable examples for implementors.
>> >> >
>> >> > Maybe you could start a page on the MM wiki about this? To begin 
>> >> > with
>> >> it could even be just a dump of that email. We can adjust and 
>> >> refine it easily when it's in that wiki format I think.
>> >> >
>> >> > I would call this page something like "GettingStartedNewConnectors".
>> >> >
>> >> > Best regards,
>> >> > Kasper
>> >> >
>> >> > 2014-12-15 12:48 GMT+01:00 Tomasz Guziałek <
>> >> > tomasz.guzia...@humaninference.com>:
>> >> >>
>> >> >> Hello Alberto and others,
>> >> >>
>> >> >> My first thought also was around building new connectors - what 
>> >> >> is the minimum I need to provide as a developer to query a new 
&

RE: [DISCUSS] Documentation improvements?

[Tomasz Guziałek]

Thanks, it is working now :).

Best regards,
Tomasz

-Original Message-
From: Kasper Sørensen [mailto:i.am.kasper.soren...@gmail.com] 
Sent: Wednesday, January 21, 2015 12:43
To: dev@metamodel.apache.org
Subject: Re: [DISCUSS] Documentation improvements?

Figure it out :-) You have access now.

2015-01-21 12:38 GMT+01:00 Kasper Sørensen :

> I've been granted admin rights now ... trying to figure out how to 
> give you access to write new pages Tomasz ... :-)
>
> 2015-01-20 16:47 GMT+01:00 Tomasz Guziałek <
> tomasz.guzia...@humaninference.com>:
>
>> I forgot about it actually. However, my INFRA ticket is still unresolved:
>> https://issues.apache.org/jira/browse/INFRA-8902 Hopefully, some of 
>> you can add me as a contributor to the Wiki when you get your admin rights 
>> back.
>>
>> Best regards,
>> Tomasz
>>
>> -Original Message-
>> From: Kasper Sørensen [mailto:i.am.kasper.soren...@gmail.com]
>> Sent: Wednesday, January 14, 2015 23:22
>> To: dev@metamodel.apache.org
>> Subject: Re: [DISCUSS] Documentation improvements?
>>
>> Hi everybody,
>>
>> I know it's been a while, but I felt like bumping this topic. I was 
>> thinking a bit about "what's most important for MetaModel at this point"
>> and I think documentation is high on my list, if not highest. If the 
>> wiki is in any way blocking work (Tomasz?) then please raise it here 
>> and let's get it fixed. And while waiting for such a thing we should 
>> still be able to work on the docs - either via emails, documentation 
>> in .md files or whatever.
>>
>> Cheers,
>> Kasper
>>
>> 2014-12-18 21:20 GMT+01:00 Kasper Sørensen <
>> i.am.kasper.soren...@gmail.com>:
>>
>> > Javadocs are now available at:
>> >
>> > http://metamodel.apache.org/apidocs/3.4.1
>> >
>> > or via this redirect url that we can always make point to new versions:
>> > http://metamodel.apache.org/apidocs/current
>> >
>> > Kasper
>> >
>> >
>> > 2014-12-17 17:02 GMT+01:00 Henry Saputra :
>> >>
>> >> Hi Tomasz,
>> >>
>> >> Hmm somehow I also do not have admin access to add individual to 
>> >> edit access, unfortunately you need to file ASF INFRA ticket to 
>> >> get help on this =(
>> >>
>> >> - Henry
>> >>
>> >> On Wed, Dec 17, 2014 at 3:33 AM, Tomasz Guziałek 
>> >>  wrote:
>> >> > I registered myself at the Wiki, but I believe I do not have the 
>> >> > rights
>> >> for editing. Henry, is that you who can fix that for me? My 
>> >> username is "tomaszguzialek". Thank you!
>> >> >
>> >> > Best regards,
>> >> > Tomasz
>> >> >
>> >> > -Original Message-
>> >> > From: Kasper Sørensen [mailto:i.am.kasper.soren...@gmail.com]
>> >> > Sent: Tuesday, December 16, 2014 20:04
>> >> > To: dev@metamodel.apache.org
>> >> > Subject: Re: [DISCUSS] Documentation improvements?
>> >> >
>> >> > Hi Tomasz,
>> >> >
>> >> > Good info too! I like the analogies to existing implementations 
>> >> > - I can
>> >> imagine these are valueable examples for implementors.
>> >> >
>> >> > Maybe you could start a page on the MM wiki about this? To begin 
>> >> > with
>> >> it could even be just a dump of that email. We can adjust and 
>> >> refine it easily when it's in that wiki format I think.
>> >> >
>> >> > I would call this page something like "GettingStartedNewConnectors".
>> >> >
>> >> > Best regards,
>> >> > Kasper
>> >> >
>> >> > 2014-12-15 12:48 GMT+01:00 Tomasz Guziałek <
>> >> > tomasz.guzia...@humaninference.com>:
>> >> >>
>> >> >> Hello Alberto and others,
>> >> >>
>> >> >> My first thought also was around building new connectors - what 
>> >> >> is the minimum I need to provide as a developer to query a new 
>> >> >> datastore and what I will get "for free" from MetaModel. My 
>> >> >> (quick sketch of) step-by-step guide would look like this:
>> >> >>
>> >> >> 1) Create a new XXXDataContext class that extends 
>> >> >> QueryPos

RE: [DISCUSS] Documentation improvements?

[Tomasz Guziałek]

I forgot about it actually. However, my INFRA ticket is still unresolved: 
https://issues.apache.org/jira/browse/INFRA-8902 Hopefully, some of you can add 
me as a contributor to the Wiki when you get your admin rights back.

Best regards,
Tomasz

-Original Message-
From: Kasper Sørensen [mailto:i.am.kasper.soren...@gmail.com] 
Sent: Wednesday, January 14, 2015 23:22
To: dev@metamodel.apache.org
Subject: Re: [DISCUSS] Documentation improvements?

Hi everybody,

I know it's been a while, but I felt like bumping this topic. I was thinking a 
bit about "what's most important for MetaModel at this point"
and I think documentation is high on my list, if not highest. If the wiki is in 
any way blocking work (Tomasz?) then please raise it here and let's get it 
fixed. And while waiting for such a thing we should still be able to work on 
the docs - either via emails, documentation in .md files or whatever.

Cheers,
Kasper

2014-12-18 21:20 GMT+01:00 Kasper Sørensen :

> Javadocs are now available at:
>
> http://metamodel.apache.org/apidocs/3.4.1
>
> or via this redirect url that we can always make point to new versions:
> http://metamodel.apache.org/apidocs/current
>
> Kasper
>
>
> 2014-12-17 17:02 GMT+01:00 Henry Saputra :
>>
>> Hi Tomasz,
>>
>> Hmm somehow I also do not have admin access to add individual to edit 
>> access, unfortunately you need to file ASF INFRA ticket to get help 
>> on this =(
>>
>> - Henry
>>
>> On Wed, Dec 17, 2014 at 3:33 AM, Tomasz Guziałek 
>>  wrote:
>> > I registered myself at the Wiki, but I believe I do not have the 
>> > rights
>> for editing. Henry, is that you who can fix that for me? My username 
>> is "tomaszguzialek". Thank you!
>> >
>> > Best regards,
>> > Tomasz
>> >
>> > -Original Message-
>> > From: Kasper Sørensen [mailto:i.am.kasper.soren...@gmail.com]
>> > Sent: Tuesday, December 16, 2014 20:04
>> > To: dev@metamodel.apache.org
>> > Subject: Re: [DISCUSS] Documentation improvements?
>> >
>> > Hi Tomasz,
>> >
>> > Good info too! I like the analogies to existing implementations - I 
>> > can
>> imagine these are valueable examples for implementors.
>> >
>> > Maybe you could start a page on the MM wiki about this? To begin 
>> > with
>> it could even be just a dump of that email. We can adjust and refine 
>> it easily when it's in that wiki format I think.
>> >
>> > I would call this page something like "GettingStartedNewConnectors".
>> >
>> > Best regards,
>> > Kasper
>> >
>> > 2014-12-15 12:48 GMT+01:00 Tomasz Guziałek <
>> > tomasz.guzia...@humaninference.com>:
>> >>
>> >> Hello Alberto and others,
>> >>
>> >> My first thought also was around building new connectors - what is 
>> >> the minimum I need to provide as a developer to query a new 
>> >> datastore and what I will get "for free" from MetaModel. My (quick 
>> >> sketch of) step-by-step guide would look like this:
>> >>
>> >> 1) Create a new XXXDataContext class that extends 
>> >> QueryPostProcessDataContext (to get functionalities for free) that 
>> >> holds a reference to a native API object. Taking existing examples:
>> >> CouchDbDataContext holds Ektorp' CouchDbInstance
>> >> HBaseDataContext holds HTablePool
>> >> CsvDataContext holds a handle to a file (through 
>> >> MetaModel's Resource class, to be precise)
>> >> 2) Implement materializeMainSchemaTable to fetch the data that is 
>> >> going to represent the table, using the native API. Existing examples:
>> >> CouchDbDataContext fetches a view will all docs through 
>> >> Ektorp's CouchDbInstance
>> >> HBaseDataContext creates a Scan of a table through
>> HBaseTablePool
>> >> CsvDataContext reads the whole file using our file handle
>> >> 3) Return a new XXXDataSet instance with the native result passed 
>> >> as a parameter. XXXDataSet class takes the native result object 
>> >> and translates it to the MetaModel's Row objects.
>> >> CouchDbDataSet will parse the JSON document and 
>> >> instantiate MetaModel's Row object with this data
>> >> HBaseDataSet extracts the values from the Scan and 
>> >> instantiates MetaModel's Row object with the values
>> >>  

Re: Website design update

[Tomasz Guziałek]

I have checked the website on my mobile (Android) before and now. All the 
issues Dennis mentioned are now fixed on my device too. Nice!

BR,
Tomasz


Sent from Samsung Mobile


 Original message 
From: Kasper Sørensen
Date:2014/12/23 11:33 (GMT+01:00)
To: dev@metamodel.apache.org
Subject: Re: Website design update

After fixing all the nitty gritty details, the new site is now online!

http://metamodel.apache.org/

Check it out on a desktop AND a mobile device near you ;-)

2014-12-23 10:37 GMT+01:00 Kasper Sørensen :

> Fixed a bunch of those points, because I saw them too :-) Thanks for the
> valuable feedback Dennis!
>
> 2014-12-23 10:19 GMT+01:00 Dennis Du Krøger <
> dennis.dukro...@humaninference.com>:
>
>> Whoops, of course attachments doesn't work on the mailing list. See it
>> here: https://www.dropbox.com/s/upsmh9xqhxsgjna/tempFileForShare.jpg?dl=0
>>
>>
>> -Original Message-
>> From: Dennis Du Krøger [mailto:dennis.dukro...@humaninference.com]
>> Sent: 23. december 2014 10:17
>> To: dev@metamodel.apache.org
>> Subject: RE: Website design update
>>
>> Cool!
>>
>> A few comments on looks on my phone:
>> Everything is hugging the left edge with tons of space on the right. i.e.
>> the News sections a bound to the left edge, but the right has a margin.
>> I've seen this on quite a few pages, so it might by my phone that is weird.
>>
>> The page is zoomable, but looks weird when zoomede. I believe playing
>> with the options for the meta tag can stop that.
>>
>> The connector badges/icons look a bit strange: I get two badges on the
>> left side with aalmost space for a third. See "connector badges.jpg"
>> attachment. They also look a bit fuzzy on my phone.
>> I think the Bootstrap .col system can help out here. It should be able to
>> break and adjust the badges properly on all devices.
>>
>> The download and sections are not doing well with the small width; Text
>> on top of text.
>>
>> Almost the same with the mailing list, but here the text breaks out of
>> the box instead. That might actually be the thing that causes the right
>> margin I talked about before.
>>
>> BR,
>> Dennis
>>
>> -Original Message-
>> From: Kasper Sørensen [mailto:i.am.kasper.soren...@gmail.com]
>> Sent: 23. december 2014 09:53
>> To: dev@metamodel.apache.org
>> Subject: RE: Website design update
>>
>> That (the meta tag) did the trick! Good catch!
>> Den 23/12/2014 09.40 skrev "Dennis Du Krøger" <
>> dennis.dukro...@humaninference.com>:
>>
>> > There's many containers, which seems a bit weird, but I don't think
>> > that's illegal, they are just not nestable like before. As far as I
>> > remember, the only ill effect of not following the rules is weird
>> > offsets. But I think the "proper" way is to have each section as a
>> Bootstrap .row.
>> >
>> > In their examples, they have a '> > content="width=device-width, initial-scale=1">' header. I guess that
>> > could trigger the proper behavior on mobile.
>> >
>> > By the way, looking at the code, it seems a little bit of a mix of
>> > using Bootstrap with manual styling. I'm not sure that will work out
>> > very well, with for all the ways the site can be laid out by BS on
>> differing devices.
>> >
>> > BR,
>> > Dennis
>> >
>> > -Original Message-
>> > From: Kasper Sørensen [mailto:i.am.kasper.soren...@gmail.com]
>> > Sent: 23. december 2014 09:24
>> > To: dev@metamodel.apache.org
>> > Subject: Re: Website design update
>> >
>> > Hmm I removed all the nested containers, but I still see that issue...
>> > Very strange.
>> >
>> > 2014-12-23 9:00 GMT+01:00 Kasper Sørensen
>> > > > >:
>> >
>> > > Thanks for the tip, Dennis. Lemme see how it works if I remove the
>> > > multiple nested containers...
>> > >
>> > > 2014-12-23 8:36 GMT+01:00 Dennis Du Krøger <
>> > > dennis.dukro...@humaninference.com>:
>> > >
>> > >> It looks good, but there seem to be some kind of problem with
>> > >> detecting my phone (Galaxy Note 3): The Bootstrap website looks
>> > >> properly... Mobile, but the (Bootstrapped) MetaModel site looks
>> > >> like a
>> > desktop site.
>> > >>
>> > >> Looking at the source, it looks a bit strange: There's a .container
>> > >> within a .container-fluid? As far as I remember, you can only have
>> > >> a top level container (.container-fluid for full width, .container
>> > >> for a narrow site), everything else must be .row and .col.
>> > >>
>> > >> Best regards,
>> > >> Dennis
>> > >>
>> > >> -Original Message-
>> > >> From: Kasper Sørensen [mailto:i.am.kasper.soren...@gmail.com]
>> > >> Sent: 22. december 2014 23:48
>> > >> To: dev@metamodel.apache.org
>> > >> Subject: Website design update
>> > >>
>> > >> Hi guys,
>> > >>
>> > >> I've spent a bit of time learning Bootstrap, the responsive web UI
>> > >> framework. So I decided to try and convert the MetaModel website to
>> > >> a proper bootstrap site. And before I knew it, I was also trying
>> > >> out some new ideas for how the "front page" / splash should look.

RE: [DISCUSS] Documentation improvements?

[Tomasz Guziałek]

Hello Alberto,

I have found your INFRA JIRA issue: 
https://issues.apache.org/jira/browse/INFRA-8508 The comment suggests that Matt 
Franklin and Henry Saputra as MetaModel's Wiki admins have rights to grant the 
access (so INFRA ticket is kind of mistargetted). However, I also found an 
older post in the mailing list where Henry suggests creating one, so I am a 
little confused to be honest. Henry, could you clarify that?

Best regards,
Tomasz

-Original Message-
From: Alberto Rodriguez [mailto:ardl...@gmail.com] 
Sent: Wednesday, December 17, 2014 14:48
To: dev@metamodel.apache.org
Subject: Re: [DISCUSS] Documentation improvements?

Hi Tomasz,

You have to open a ticket in the infra project's jira.

Regards,

Alberto

2014-12-17 12:33 GMT+01:00 Tomasz Guziałek <
tomasz.guzia...@humaninference.com>:
>
> I registered myself at the Wiki, but I believe I do not have the 
> rights for editing. Henry, is that you who can fix that for me? My 
> username is "tomaszguzialek". Thank you!
>
> Best regards,
> Tomasz
>
> -Original Message-
> From: Kasper Sørensen [mailto:i.am.kasper.soren...@gmail.com]
> Sent: Tuesday, December 16, 2014 20:04
> To: dev@metamodel.apache.org
> Subject: Re: [DISCUSS] Documentation improvements?
>
> Hi Tomasz,
>
> Good info too! I like the analogies to existing implementations - I 
> can imagine these are valueable examples for implementors.
>
> Maybe you could start a page on the MM wiki about this? To begin with 
> it could even be just a dump of that email. We can adjust and refine 
> it easily when it's in that wiki format I think.
>
> I would call this page something like "GettingStartedNewConnectors".
>
> Best regards,
> Kasper
>
> 2014-12-15 12:48 GMT+01:00 Tomasz Guziałek <
> tomasz.guzia...@humaninference.com>:
> >
> > Hello Alberto and others,
> >
> > My first thought also was around building new connectors - what is 
> > the minimum I need to provide as a developer to query a new 
> > datastore and what I will get "for free" from MetaModel. My (quick 
> > sketch of) step-by-step guide would look like this:
> >
> > 1) Create a new XXXDataContext class that extends 
> > QueryPostProcessDataContext (to get functionalities for free) that 
> > holds a reference to a native API object. Taking existing examples:
> > CouchDbDataContext holds Ektorp' CouchDbInstance
> > HBaseDataContext holds HTablePool
> > CsvDataContext holds a handle to a file (through MetaModel's 
> > Resource class, to be precise)
> > 2) Implement materializeMainSchemaTable to fetch the data that is 
> > going to represent the table, using the native API. Existing examples:
> > CouchDbDataContext fetches a view will all docs through 
> > Ektorp's CouchDbInstance
> > HBaseDataContext creates a Scan of a table through HBaseTablePool
> > CsvDataContext reads the whole file using our file handle
> > 3) Return a new XXXDataSet instance with the native result passed as 
> > a parameter. XXXDataSet class takes the native result object and 
> > translates it to the MetaModel's Row objects.
> > CouchDbDataSet will parse the JSON document and instantiate 
> > MetaModel's Row object with this data
> > HBaseDataSet extracts the values from the Scan and 
> > instantiates MetaModel's Row object with the values
> > CsvDataSet translates a line from a CSV file into 
> > MetaModel's Row object
> >
> > This is the minimum that needs to be implemented. While we have the 
> > native result translated to MetaModel's Row objects, selecting 
> > specific columns, filtering and so on we get for free from 
> > QueryPostProcessDataContext class that we subclassed. Of course, it 
> > is not the most performant way of querying, for example doing a full 
> > scan to get a single row by its primary key is optimized in many databases.
> > Delegating primary key lookups, count queries, queries with simple 
> > WHERE clauses to the native API instead of post-processing it in 
> > Java is the next step for a developer of a new MetaModel connector.
> >
> > I would benefit a lot from such a guide at the beginning of my 
> > journey with MetaModel...
> >
> > Best regards,
> > Tomasz
> >
> >
> > -Original Message-
> > From: Alberto Rodriguez [mailto:ardl...@gmail.com]
> > Sent: Friday, December 12, 2014 11:42
> > To: dev@metamodel.apache.org
> > Cc: juan.rodriguez.hort...@gmail.com
> > Subject: Re: [DISCUSS] Documentation improvements?
> >
> >

RE: [DISCUSS] Documentation improvements?

[Tomasz Guziałek]

I registered myself at the Wiki, but I believe I do not have the rights for 
editing. Henry, is that you who can fix that for me? My username is 
"tomaszguzialek". Thank you!

Best regards,
Tomasz

-Original Message-
From: Kasper Sørensen [mailto:i.am.kasper.soren...@gmail.com] 
Sent: Tuesday, December 16, 2014 20:04
To: dev@metamodel.apache.org
Subject: Re: [DISCUSS] Documentation improvements?

Hi Tomasz,

Good info too! I like the analogies to existing implementations - I can imagine 
these are valueable examples for implementors.

Maybe you could start a page on the MM wiki about this? To begin with it could 
even be just a dump of that email. We can adjust and refine it easily when it's 
in that wiki format I think.

I would call this page something like "GettingStartedNewConnectors".

Best regards,
Kasper

2014-12-15 12:48 GMT+01:00 Tomasz Guziałek <
tomasz.guzia...@humaninference.com>:
>
> Hello Alberto and others,
>
> My first thought also was around building new connectors - what is the 
> minimum I need to provide as a developer to query a new datastore and 
> what I will get "for free" from MetaModel. My (quick sketch of) 
> step-by-step guide would look like this:
>
> 1) Create a new XXXDataContext class that extends 
> QueryPostProcessDataContext (to get functionalities for free) that 
> holds a reference to a native API object. Taking existing examples:
> CouchDbDataContext holds Ektorp' CouchDbInstance
> HBaseDataContext holds HTablePool
> CsvDataContext holds a handle to a file (through MetaModel's 
> Resource class, to be precise)
> 2) Implement materializeMainSchemaTable to fetch the data that is 
> going to represent the table, using the native API. Existing examples:
> CouchDbDataContext fetches a view will all docs through 
> Ektorp's CouchDbInstance
> HBaseDataContext creates a Scan of a table through HBaseTablePool
> CsvDataContext reads the whole file using our file handle
> 3) Return a new XXXDataSet instance with the native result passed as a 
> parameter. XXXDataSet class takes the native result object and 
> translates it to the MetaModel's Row objects.
> CouchDbDataSet will parse the JSON document and instantiate 
> MetaModel's Row object with this data
> HBaseDataSet extracts the values from the Scan and 
> instantiates MetaModel's Row object with the values
> CsvDataSet translates a line from a CSV file into MetaModel's 
> Row object
>
> This is the minimum that needs to be implemented. While we have the 
> native result translated to MetaModel's Row objects, selecting 
> specific columns, filtering and so on we get for free from 
> QueryPostProcessDataContext class that we subclassed. Of course, it is 
> not the most performant way of querying, for example doing a full scan 
> to get a single row by its primary key is optimized in many databases. 
> Delegating primary key lookups, count queries, queries with simple 
> WHERE clauses to the native API instead of post-processing it in Java 
> is the next step for a developer of a new MetaModel connector.
>
> I would benefit a lot from such a guide at the beginning of my journey 
> with MetaModel...
>
> Best regards,
> Tomasz
>
>
> -Original Message-
> From: Alberto Rodriguez [mailto:ardl...@gmail.com]
> Sent: Friday, December 12, 2014 11:42
> To: dev@metamodel.apache.org
> Cc: juan.rodriguez.hort...@gmail.com
> Subject: Re: [DISCUSS] Documentation improvements?
>
> Hi all,
>
> When I first came across the project I wasn't sure how and where MM "plays"
> with the data. I mean, for the different datasources I didn't know 
> whether MM was fetching the data in memory and then performing joins, 
> selects and so on or was delegating this behaviour to the native 
> drivers. The table that you guys put together in the wiki: 
> QueryExecutionStrategies < 
> https://wiki.apache.org/metamodel/QueryExecutionStrategies> is quite 
> clarifying.
>
> In my particular case, as we needed new connectors that wasn't 
> implemented yet and decided to contribute to the project implementing 
> them, I was "fighting" with the code from day 0 and I must say that 
> the code is pretty self-explanatory. Kasper has been done a great job 
> and if you have some Java experience you might have a new connector 
> ready-to-use within few days. I think we should make an effort and try 
> to share this with the world, MM is great as it is now but I think one 
> of its main powerful features is that you can create your own 
> connectors without much effort. It might be a good idea to create a 
> section on the website like "

RE: [DISCUSS] Documentation improvements?

[Tomasz Guziałek]

Hello Alberto and others,

My first thought also was around building new connectors - what is the minimum 
I need to provide as a developer to query a new datastore and what I will get 
"for free" from MetaModel. My (quick sketch of) step-by-step guide would look 
like this:

1) Create a new XXXDataContext class that extends QueryPostProcessDataContext 
(to get functionalities for free) that holds a reference to a native API 
object. Taking existing examples:
CouchDbDataContext holds Ektorp' CouchDbInstance
HBaseDataContext holds HTablePool
CsvDataContext holds a handle to a file (through MetaModel's Resource 
class, to be precise)
2) Implement materializeMainSchemaTable to fetch the data that is going to 
represent the table, using the native API. Existing examples:
CouchDbDataContext fetches a view will all docs through Ektorp's 
CouchDbInstance
HBaseDataContext creates a Scan of a table through HBaseTablePool
CsvDataContext reads the whole file using our file handle
3) Return a new XXXDataSet instance with the native result passed as a 
parameter. XXXDataSet class takes the native result object and translates it to 
the MetaModel's Row objects.
CouchDbDataSet will parse the JSON document and instantiate MetaModel's 
Row object with this data
HBaseDataSet extracts the values from the Scan and instantiates 
MetaModel's Row object with the values
CsvDataSet translates a line from a CSV file into MetaModel's Row object

This is the minimum that needs to be implemented. While we have the native 
result translated to MetaModel's Row objects, selecting specific columns, 
filtering and so on we get for free from QueryPostProcessDataContext class that 
we subclassed. Of course, it is not the most performant way of querying, for 
example doing a full scan to get a single row by its primary key is optimized 
in many databases. Delegating primary key lookups, count queries, queries with 
simple WHERE clauses to the native API instead of post-processing it in Java is 
the next step for a developer of a new MetaModel connector.

I would benefit a lot from such a guide at the beginning of my journey with 
MetaModel...

Best regards,
Tomasz


-Original Message-
From: Alberto Rodriguez [mailto:ardl...@gmail.com] 
Sent: Friday, December 12, 2014 11:42
To: dev@metamodel.apache.org
Cc: juan.rodriguez.hort...@gmail.com
Subject: Re: [DISCUSS] Documentation improvements?

Hi all,

When I first came across the project I wasn't sure how and where MM "plays"
with the data. I mean, for the different datasources I didn't know whether MM 
was fetching the data in memory and then performing joins, selects and so on or 
was delegating this behaviour to the native drivers. The table that you guys 
put together in the wiki: QueryExecutionStrategies 
 is quite 
clarifying.

In my particular case, as we needed new connectors that wasn't implemented yet 
and decided to contribute to the project implementing them, I was "fighting" 
with the code from day 0 and I must say that the code is pretty 
self-explanatory. Kasper has been done a great job and if you have some Java 
experience you might have a new connector ready-to-use within few days. I think 
we should make an effort and try to share this with the world, MM is great as 
it is now but I think one of its main powerful features is that you can create 
your own connectors without much effort. It might be a good idea to create a 
section on the website like "Create your own connectors" and a guide to 
implement them. What do you think?

I would also be more than happy to help in any decision we take regarding the 
documentation.

Kind regards,

2014-12-12 9:32 GMT+01:00 Kasper Sørensen :
>
> Hi Juan,
>
> Thanks for that feedback. I think it helps a lot to see what relevant 
> and good information we already have (some of it on third party sites 
> - we should look to integrate it some more) and also what we should 
> improve (the javadoc thing is such a simple thing - I'll create a JIRA 
> issue about doing it ASAP).
>
> Kasper
>
> 2014-12-11 20:36 GMT+01:00 Juan Rodríguez Hortalá <
> juan.rodriguez.hort...@gmail.com>:
> >
> > Hi all,
> >
> > I don't have a lot of experience with Metamodel, I did my first
> experiments
> > with it in the capstone project for a MSc, and then I used it in my 
> > work combined with Apache Sqoop to import data from a relational 
> > database,
> where
> > Metamodel was in charge of obtaining the data schema. But maybe my
> limited
> > experience could be of use for answering this question.
> > I think I discovered Metamodel when searching the internet for a way 
> > to connect a BI visualization tool with HBase. As the starting 
> > points I
> used:
> >
> >  * This post 
> > http://www.infoq.com/articles/apache-incubator-metamodel by Kasper, 
> > which I think is a pretty good quick start, with several code snippets.
>

RE: About HBase dependencies in Maven

[Tomasz Guziałek]

Hello Lin,

It seems we forgot to include HBase module in the MetaModel-full artifact.  
However, you can use MetaModel-hbase directly:


org.apache.metamodel
MetaModel-hbase
4.3.1


You should also be aware that MetaModel-hbase uses HBase in version 
0.95.1-hadoop1. If you use Hadoop 2, hbase-client should be excluded and you 
should include your desired version of hbase-client manually. I hope it helps, 
feel free to ask if you have more questions.

Best regards,
Tomasz

-Original Message-
From: Lin, Yunzhen [mailto:yunzhen@contractor.ca.com] 
Sent: Monday, December 15, 2014 10:01
To: dev@metamodel.apache.org
Subject: About HBase dependencies in Maven

Hi guys,

I found that there is no more HBase libraries in the maven dependencies:

http://www.mvnrepository.com/artifact/org.apache.metamodel/MetaModel-full/4.3.0-incubating

Now we have

org.apache.metamodel

MetaModel-cassandra
 
4.3.0-incubating

org.apache.metamodel

MetaModel-core
   
4.3.0-incubating

org.apache.metamodel

MetaModel-couchdb
 
4.3.0-incubating

org.apache.metamodel

MetaModel-csv
 
4.3.0-incubating

org.apache.metamodel

MetaModel-elasticsearch
 
4.3.0-incubating

org.apache.metamodel

MetaModel-excel
 
4.3.0-incubating

org.apache.metamodel

MetaModel-fixedwidth
   
4.3.0-incubating

org.apache.metamodel

MetaModel-jdbc
   
4.3.0-incubating

org.apache.metamodel

MetaModel-json
   
4.3.0-incubating

org.apache.metamodel

MetaModel-mongodb
 
4.3.0-incubating

org.apache.metamodel

MetaModel-openoffice
   
4.3.0-incubating

org.apache.metamodel

MetaModel-pojo
   
4.3.0-incubating

org.apache.metamodel

MetaModel-salesforce
   
4.3.0-incubating

org.apache.metamodel