Re: MetaModel PMC activity and health

[Kasper Sørensen]

Dear community,

Following the inactivity and health concerns of the MetaModel community,
the board has decided to terminate the project and move it to the Apache
Attic [1].
I am thankful for the great work we have done here and the good times that
I have had working with this community. Every good thing comes to an end.
Thank you for everything.

Best regards,
Kasper

[1] https://attic.apache.org/

Den tir. 18. maj 2021 kl. 22.19 skrev Kasper Sørensen <
i.am.kasper.soren...@gmail.com>:

> Dear MetaModel community,
>
> I want to let you all know of the state of the MetaModel PMC, which needs
> help in order for us to continue to operate as an active Apache project.
>
> I have personally been reconsidering my role as PMC Chair [1] since I feel
> that I no longer have the sufficient energy to operate as a chair for this
> project. I would be very happy to continue as a member of the PMC, and to
> help someone else take over the chair duties. But in the @private list for
> MetaModel's PMC it has not been possible to find a replacement.
>
> Last week we conducted a roll call to see which PMC members are still
> active and willing to continue the PMC work. This unfortunately only
> resulted in us recognizing that a few people would not be able to
> contribute any more. We did not establish the required three active PMC
> members that is required for us to operate in the Apache way.
>
> So now we will either need to populate the PMC with at least three members
> who are interested in this task, or else we should recommend moving the
> project to Apache Attic [2]. Note that we will not accept complete
> newcomers to the project to the PMC, but in the case that there are folks
> on this list who have made contributions, or existing PMC members who did
> not respond initially but are having second thoughts, then please come
> forward and we will see if we can reboot the MetaModel PMC.
>
> Thank you all in advance.
>
> Best regards,
> Kasper
>
> [1] Overview of the chair duties can be found here:
> https://www.apache.org/dev/pmc.html#chair
> [2] About the attic move:
> https://www.apache.org/dev/pmc.html#move-to-attic
>

MetaModel PMC activity and health

[Kasper Sørensen]

Dear MetaModel community,

I want to let you all know of the state of the MetaModel PMC, which needs
help in order for us to continue to operate as an active Apache project.

I have personally been reconsidering my role as PMC Chair [1] since I feel
that I no longer have the sufficient energy to operate as a chair for this
project. I would be very happy to continue as a member of the PMC, and to
help someone else take over the chair duties. But in the @private list for
MetaModel's PMC it has not been possible to find a replacement.

Last week we conducted a roll call to see which PMC members are still
active and willing to continue the PMC work. This unfortunately only
resulted in us recognizing that a few people would not be able to
contribute any more. We did not establish the required three active PMC
members that is required for us to operate in the Apache way.

So now we will either need to populate the PMC with at least three members
who are interested in this task, or else we should recommend moving the
project to Apache Attic [2]. Note that we will not accept complete
newcomers to the project to the PMC, but in the case that there are folks
on this list who have made contributions, or existing PMC members who did
not respond initially but are having second thoughts, then please come
forward and we will see if we can reboot the MetaModel PMC.

Thank you all in advance.

Best regards,
Kasper

[1] Overview of the chair duties can be found here:
https://www.apache.org/dev/pmc.html#chair
[2] About the attic move: https://www.apache.org/dev/pmc.html#move-to-attic

Re: [RESULT] [VOTE] Apache MetaModel release 5.3.3

[Kasper Sørensen]

Thank you for pointing that out Justin. That's definitely something for us
to be aware of. Seems we should have called for a revote, but I don't think
there's much we can do about it now?

Den man. 10. maj 2021 kl. 07.21 skrev Justin Mclean :

> Hi,
>
> In order to make a release it need 3 +1 binding votes from PMC members, it
> looks like this rase only had 2 binding votes.
>
> Kind Regards,
> Justin
>

Re: [VOTE] Apache MetaModel release 5.3.3

[Kasper Sørensen]

+1

Den tor. 18. feb. 2021 kl. 16.24 skrev Alberto Rodriguez :

> +1
>
> El jue, 18 feb 2021 a las 11:47, Lutzen Luinenburg (<
> l.luinenb...@humaninference.com>) escribió:
>
> > +1
> >
> >
> >
> >
> > Kind regards,
> >
> > Lútzen Luinenburg
> > Product Manager
> >
> >
> > T+31 (0)26 355 06 55
> >
> > M   +31 (0)6 28 25 42 87
> >
> > El.luinenb...@humaninference.com
> >
> > W   www.humaninference.com
> >
> >
> > -Original Message-
> > From: Arjan Seijkens Hagemans 
> > Sent: Thursday, 18 February 2021 11:46
> > To: dev@metamodel.apache.org
> > Subject: [VOTE] Apache MetaModel release 5.3.3
> >
> > Hi All,
> >
> > Please vote on releasing the following candidate as Apache Metamodel
> > version 5.3.3.
> >
> > The Git tag to be voted on is MetaModel-5.3.3:
> >
> >
> https://gitbox.apache.org/repos/asf?p=metamodel.git;a=commit;h=705d9fe37d2792ee5ef161ae4778ab8962aa8168
> >
> > The source artifact to be voted on is:
> >
> >
> https://repository.apache.org/content/repositories/orgapachemetamodel-1044/org/apache/metamodel/MetaModel/5.3.3/MetaModel-5.3.3-source-release.zip
> >
> > Parent directory (including MD5, SHA1 hashes etc.) of the source is:
> >
> >
> https://repository.apache.org/content/repositories/orgapachemetamodel-1044/org/apache/metamodel/MetaModel/5.3.3/
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/arjansh.asc
> >
> > Release engineer public key id: 750FB127
> >
> > The staging Maven repository for this release can be found at:
> >
> http://repository.apache.org/content/repositories/orgapachemetamodel-1044
> >
> > Please vote on releasing this package as Apache MetaModel 5.3.3.
> >
> > The vote is open for 72 hours.
> >
> > [ ] +1 Release this package as Apache MetaModel 5.3.3 [ ] -1 Do not
> > release this package because ...
> >
> > Thank you in advance for participating.
> >
> > Regards,
> > Arjan Seijkens
> >
>

Re: New MetaModel release.

[Kasper Sørensen]

I'm all for it. Let's call a vote.

Den ons. 17. feb. 2021 kl. 09.32 skrev Arjan Seijkens Hagemans <
arja...@gmail.com>:

> Hi,
>
> I'd like to create a new MetaModel release (5.3.3?) (preferably after
> https://github.com/apache/metamodel/pull/247 is merged).
>
> Is that okay?
>
> Kind Regards,
> Arjan Seijkens
>

Re: [RESULT] [VOTE] Apache MetaModel website migration target environment

[Kasper Sørensen]

Perfect. Thanks for organizing this, Arjan!

Den man. 7. sep. 2020 kl. 08.22 skrev Arjan Seijkens Hagemans <
arja...@gmail.com>:

> Hi everyone,
>
> I'm happy to be able to tell that the VOTE for the Apache MetaModel
> website migration target environment has passed with 3 votes (all
> binding).
>
> The result is that 3 votes were for migrating to Jekyll.
>
> Voters:
> Kasper Sørensen *
> Alberto Rodriguez *
> Arjan Seijkens *
>
> * - indicates PMC
>
> So hereby we record as a PMC decision that we voted to make a move to
> Jekyll. I will communicate this to Apache's infrastructure team, so
> they can follow up on this decision.
>
> Thank you to everyone who participated.
>
> Best regards,
> Arjan Seijkens
>

Re: [VOTE] Apache MetaModel website migration target environment

[Kasper Sørensen]

+1 Jekyll


Den tor. 3. sep. 2020 kl. 14.58 skrev Arjan Seijkens Hagemans <
arja...@gmail.com>:

> Hi All,
>
> Since our project website is still running on Apache CMS and that has
> reached end-of-life, we need to migrate.
>
> These pages describe some options for the migration:
> https://infra.apache.org/project-site.html
>
> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
>
> To summarize, Apache offers these options:
>
> 1. Pelican
> 2. Github Pages
> 3. Jekyll
> 4. Hugo
> 5. JBake
>
> So. Please vote on the target environment for migrating the Apache
> MetaModel website to.
>
> The vote is open for 72 hours.
>
> You can choose between
> [ ] +1 Pelican
> [ ] +1 Github Pages
> [ ] +1 Jekyll
> [ ] +1 Hugo
> [ ] +1 JBake
> [ ] -1 Do not use one of the above, but instead migrate to ...
>
> Thank you in advance for participating.
>
> Regards,
> Arjan Seijkens
>

Re: Migration of project website from Apache CMS

[Kasper Sørensen]

I think you should probably call for a vote yes. Let's use this thread for
any discussion on it.

I am fine with more or less either of the options. But I have a bit of
experience using Jekyll since that's what you use to build sites on github
pages, too. So my preference is slightly towards Jekyll.

Den tir. 25. aug. 2020 kl. 15.54 skrev Arjan Seijkens Hagemans <
arja...@gmail.com>:

> Hi,
>
> Since our project website is still running on Apache CMS and that has
> reached end-of-life, we need to migrate.
>
> These pages describe some options for the migration:
> https://infra.apache.org/project-site.html
>
> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
>
> To summarize, Apache offers these options:
>
> 1. Pelican
> 2. Github Pages
> 3. Jekyll
> 4. Hugo
> 5. JBake
>
> The first thing that is expected from us is to decide on one of these
> options and to record a PMC decision to make the move and to authorize
> Infra to remove metamodel artifacts from the CMS once the move is
> done.
>
> Should I call for a vote on this?
>
> Kind regards,
> Arjan Seijkens
>

Re: Your project's website

[Kasper Sørensen]

Hi Arjan,

>From my perspective that would be awesome. I have very limited time at the
moment, so I'd be happy if you can help out!

Best regards,
Kasper

Den man. 17. aug. 2020 kl. 10.17 skrev Arjan Seijkens Hagemans <
arja...@gmail.com>:

> I think they still need a point-of-contact for the migration. I could
> do that if desired.
>
> Kind regards,
> Arjan Seijkens
>
> Op ma 10 aug. 2020 om 20:05 schreef Kasper Sørensen
> :
> >
> > Hi Andrew,
> >
> > Thanks for reaching out. Yes, our website is using the Apache CMS.
> However,
> > we only use it to host static HTML, so not really using much of the real
> > CMS features. Just the SVN pub/sub mechanism I reckon.
> >
> > Best regards,
> > Kasper
> >
> > Den ons. 5. aug. 2020 kl. 14.40 skrev Andrew Wetmore  >:
> >
> > > Hi:
> > >
> > > I am part of the Infrastructure team, and am writing to ask whether
> your
> > > project is still using the Apache CMS for your project website. As you
> > > know, the CMS is reaching end-of-life, and we need projects to move
> their
> > > websites onto a different option within the next few weeks.
> > >
> > > There are several alternatives available, including those listed on
> this
> > > page [1] on managing project websites. Infra is assembling a Wiki page
> [2]
> > > on migrating a website from the CMS, and is looking forward to helping
> > > projects with this transition.
> > >
> > > Please let me know whether your site is still on the Apache CMS and,
> if so,
> > > who will be the project point-of-contact with Infra for the migration.
> > >
> > > Thank you!
> > >
> > >
> > >
> > >
> > > [1] https://infra.apache.org/project-site.html
> > >
> > > [2]
> > >
> > >
> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
> > >
> > >
> > >
> > > --
> > > Andrew Wetmore
> > > Technical Writer-Editor
> > > Infra
> > > *Apache Software Foundation*
> > > andr...@apache.org
> > >
> > > <
> > >
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
> > > >
> > > Virus-free.
> > > www.avast.com
> > > <
> > >
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
> > > >
> > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > >
>

Re: Your project's website

[Kasper Sørensen]

Hi Andrew,

Thanks for reaching out. Yes, our website is using the Apache CMS. However,
we only use it to host static HTML, so not really using much of the real
CMS features. Just the SVN pub/sub mechanism I reckon.

Best regards,
Kasper

Den ons. 5. aug. 2020 kl. 14.40 skrev Andrew Wetmore :

> Hi:
>
> I am part of the Infrastructure team, and am writing to ask whether your
> project is still using the Apache CMS for your project website. As you
> know, the CMS is reaching end-of-life, and we need projects to move their
> websites onto a different option within the next few weeks.
>
> There are several alternatives available, including those listed on this
> page [1] on managing project websites. Infra is assembling a Wiki page [2]
> on migrating a website from the CMS, and is looking forward to helping
> projects with this transition.
>
> Please let me know whether your site is still on the Apache CMS and, if so,
> who will be the project point-of-contact with Infra for the migration.
>
> Thank you!
>
>
>
>
> [1] https://infra.apache.org/project-site.html
>
> [2]
>
> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
>
>
>
> --
> Andrew Wetmore
> Technical Writer-Editor
> Infra
> *Apache Software Foundation*
> andr...@apache.org
>
> <
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
> >
> Virus-free.
> www.avast.com
> <
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
> >
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>

Re: Subscribe requests for issues list by supp...@ideastack.com

[Kasper Sørensen]

Oh shoot, I just approved it, but on second thought it doesn't look like we
want some support system to be responding to our mailing list threads.

Den ons. 6. maj 2020 kl. 06.24 skrev Henry Saputra :

> Hi All,
>
> I saw subscribe requests for issues@ list from supp...@ideastack.com
>
> Anyone know or own this email address?
>
> Thanks,
>
> Henry
>

Re: [Beginner][New Contributor] Need Help with few Queries

[Kasper Sørensen]

Some of those datastores are also configured in Travis CI, so they will be
part of the continuous builds. But that's just *some* of the datastores.
You can find those datastores by looking at our travic config (.travis.yml)
and the integration test properties for travis (
travis-metamodel-integrationtest-configuration.properties
<https://github.com/apache/metamodel/blob/master/travis-metamodel-integrationtest-configuration.properties>
).
For all the integration tests there should be javadocs explaining how you
can set up the datastore locally as well.

Den fre. 24. apr. 2020 kl. 10.06 skrev RATISH BANSAL :

> Hi Kasper,
>
> I understood your point around integration tests, but my query was more
> regarding the developer's perspective.
> Suppose I am working on enhancement/bug under any data source connector say
> (SQLServer), I am expected to test the changes locally before raising the
> PR. This would require a setup of my own. Tomorrow I might be working
> on any other data source, which would require its own setup to verify the
> changes.
> Does dev/contributor follow this approach and set up a data source locally
> to verify the functionality?
> It might not be possible to set up every data source locally sometimes, so
> how does dev proceed in those cases?
>
> Thanks & Regards
> Ratish Bansal
>
> On Fri, Apr 24, 2020 at 3:20 AM Kasper Sørensen <
> i.am.kasper.soren...@gmail.com> wrote:
>
> > Hi Ratish,
> >
> > Testing against all the databases is not required. We offer those tests
> as
> > occasional integration tests that we run whenever we consider the changes
> > to be related to that database. The integration tests themselves
> typically
> > contain javadoc that explains what the prerequisites are.
> >
> > The main technical documentation is located in our wiki (
> > https://cwiki.apache.org/confluence/display/METAMODEL). I would suggest
> > you
> > read through the "Key concepts" pages listed out on the front page.
> >
> > Best regards,
> > Kasper
> >
> > Den tor. 16. apr. 2020 kl. 13.43 skrev RATISH BANSAL <
> ratish1...@gmail.com
> > >:
> >
> > > Hello All,
> > >
> > > I was looking to start contributing to Metamodel, so I analyzed and
> > picked
> > > a few JIRA ticket for beginners to start with.  However, I am facing
> some
> > > difficulties mentioned below.
> > >
> > >1. How do we test the changes? As per my understanding, we do need
> an
> > >actual respective data source setup to verify. Does each contributor
> > > setup
> > >a data source locally? Is there another way, since it won't be
> > feasible
> > > to
> > >setup so many data sources?
> > >2. Do we have any technical documentation to understand the current
> > >architecture, so as to assist new contributors?
> > >
> > >   It would be great if someone could help.
> > >
> > > Thanks & Regards
> > > Ratish Bansal
> > >
> >
>

Re: [Beginner][New Contributor] Need Help with few Queries

[Kasper Sørensen]

Hi Ratish,

Testing against all the databases is not required. We offer those tests as
occasional integration tests that we run whenever we consider the changes
to be related to that database. The integration tests themselves typically
contain javadoc that explains what the prerequisites are.

The main technical documentation is located in our wiki (
https://cwiki.apache.org/confluence/display/METAMODEL). I would suggest you
read through the "Key concepts" pages listed out on the front page.

Best regards,
Kasper

Den tor. 16. apr. 2020 kl. 13.43 skrev RATISH BANSAL :

> Hello All,
>
> I was looking to start contributing to Metamodel, so I analyzed and picked
> a few JIRA ticket for beginners to start with.  However, I am facing some
> difficulties mentioned below.
>
>1. How do we test the changes? As per my understanding, we do need an
>actual respective data source setup to verify. Does each contributor
> setup
>a data source locally? Is there another way, since it won't be feasible
> to
>setup so many data sources?
>2. Do we have any technical documentation to understand the current
>architecture, so as to assist new contributors?
>
>   It would be great if someone could help.
>
> Thanks & Regards
> Ratish Bansal
>

Re: [VOTE] Apache MetaModel release 5.3.2

[Kasper Sørensen]

+1

Den fre. 3. jan. 2020 kl. 10.42 skrev Lutzen Luinenburg <
l.luinenb...@humaninference.com>:

> +1
>
>
> Kind regards,
>
> Lútzen Luinenburg
> Product Development Manager
>
>
>
>
> -Original Message-
> From: Arjan Seijkens Hagemans 
> Sent: Friday, 3 January 2020 10:42
> To: dev@metamodel.apache.org
> Subject: [VOTE] Apache MetaModel release 5.3.2
>
> Hi All,
>
> Please vote on releasing the following candidate as Apache Metamodel
> version 5.3.2.
>
> The Git tag to be voted on is MetaModel-5.3.2:
>
> https://gitbox.apache.org/repos/asf?p=metamodel.git;a=commit;h=ec4cd25d6e21d6eb85cc42ca4ba805e0e383488b
>
> The source artifact to be voted on is:
>
> https://repository.apache.org/content/repositories/orgapachemetamodel-1043/org/apache/metamodel/MetaModel/5.3.2/MetaModel-5.3.2-source-release.zip
>
> Parent directory (including MD5, SHA1 hashes etc.) of the source is:
>
> https://repository.apache.org/content/repositories/orgapachemetamodel-1043/org/apache/metamodel/MetaModel/5.3.2/
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/arjansh.asc
>
> Release engineer public key id: 750FB127
>
> The staging Maven repository for this release can be found at:
> http://repository.apache.org/content/repositories/orgapachemetamodel-1043
>
> Please vote on releasing this package as Apache MetaModel 5.3.2.
>
> The vote is open for 72 hours.
>
> [ ] +1 Release this package as Apache MetaModel 5.3.2 [ ] -1 Do not
> release this package because ...
>
> Thank you in advance for participating.
>
> Regards,
> Arjan Seijkens
>

Re: Time for a release? Call for release engineers...

[Kasper Sørensen]

Just wanna say GREAT WORK to you Arjan. So awesome to see someone else
doing the releases and with close-to-zero assistance needed.

How did you find the release guide? Was anything missing or inaccurate?

Den ons. 21. aug. 2019 kl. 08.20 skrev Kasper Sørensen <
i.am.kasper.soren...@gmail.com>:

> I'm looking into it, hang on.
>
> Den tir. 20. aug. 2019 kl. 13.02 skrev Arjan Seijkens Hagemans <
> arja...@gmail.com>:
>
>> I started and I encountered a problem. I need to have  my public key added
>> to the MetaModel KEYS file on SVN:
>> https://dist.apache.org/repos/dist/release/metamodel/KEYS.
>>
>> I can't commit on that repository however. Do I need more permissions to
>> do
>> that or do I need to commit to another repository?
>>
>> Op di 20 aug. 2019 om 09:28 schreef Arjan Seijkens Hagemans <
>> arja...@gmail.com>:
>>
>> > I'll just start with it and let you know if I encounter any problems.
>> >
>> > Op ma 19 aug. 2019 om 16:33 schreef Kasper Sørensen <
>> > i.am.kasper.soren...@gmail.com>:
>> >
>> >> Perfect! Thanks Arjan!
>> >>
>> >> The process is documented on our Confluence wiki [1]. I hope it's all
>> >> clear
>> >> and as far as I can tell it is pretty complete. Can you skim through it
>> >> and
>> >> let me know what you think? Or just begin if you think it's looking
>> good!
>> >> :-)
>> >>
>> >> [1]
>> https://cwiki.apache.org/confluence/display/METAMODEL/Release+guide
>> >>
>> >> Den man. 19. aug. 2019 kl. 09.30 skrev Arjan Seijkens Hagemans <
>> >> arja...@gmail.com>:
>> >>
>> >> >  Hi Kasper,
>> >> >
>> >> >
>> >> >
>> >> > I would be willing to do/try this.
>> >> >
>> >> >
>> >> >
>> >> > Kind regards,
>> >> >
>> >> > Arjan Seijkens
>> >> >
>> >> >
>> >> >
>> >> > -Original Message-
>> >> > From: Kasper Sørensen 
>> >> > Sent: Wednesday, August 14, 2019 10:00 PM
>> >> > To: dev@metamodel.apache.org
>> >> > Subject: Time for a release? Call for release engineers...
>> >> >
>> >> >
>> >> >
>> >> > Hi all,
>> >> >
>> >> >
>> >> >
>> >> > I think we're close/ready to run another release of MetaModel. I have
>> >> been
>> >> > facilitating the release engineering process for a very long time and
>> >> would
>> >> > like to ask if someone else would like to do/try it? I will happily
>> help
>> >> > out and assist, but I think it would be great if someone else goes
>> >> through
>> >> > the process too. I think it will be good for us to have more people
>> >> capable
>> >> > of doing the release engineering work. It's mostly about setting up
>> >> > signatures and stuff like that. Again, I can help via chat etc. to go
>> >> > through the hurdles.
>> >> >
>> >> >
>> >> >
>> >> > Here are the WIP things based on the current CHANGES.md document:
>> >> >
>> >> >
>> >> >
>> >> >- [METAMODEL-1217] - Fixes dropping JDBC Tables with view as
>> >> TableType
>> >> >
>> >> >- [METAMODEL-1215] - Removed deprecated code from pre-Java 8
>> times.
>> >> >
>> >> >- [METAMODEL-1214] - CompositeDataContext uses wrappedSchema for
>> >> >
>> >> >comparison when searching for it in the cache.
>> >> >
>> >> >- [METAMODEL-1213] - Fixed concurrency bug in single-line CSV
>> >> parallel
>> >> >
>> >> >reader.
>> >> >
>> >> >- [METAMODEL-1211] - Fixed bug of getting all SelectItems when
>> >> >
>> >> >performing nested loop joins.
>> >> >
>> >> >- [METAMODEL-1151] - Created DataContextFactory implementations
>> for
>> >> each
>> >> >
>> >> >remaining module.
>> >> >
>> >> >- Improved HBase query building by scanning columns instead of
>> column
>> >> >
>> >> >families.
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > Best regards,
>> >> >
>> >> > Kasper
>> >> >
>> >>
>> >
>>
>

Re: [VOTE] Apache MetaModel release 5.3.1

[Kasper Sørensen]

I see that the signature file is now available. And the gpg verification
passes.

+1

Den man. 9. sep. 2019 kl. 23.05 skrev Kasper Sørensen <
i.am.kasper.soren...@gmail.com>:

> -1 because the referenced committer key file [1] does not seem to exist.
> The apache people site [2] has some info on getting your key registered.
>
> Willing to change my vote once the key file exists and the artifacts
> signature matches it :-)
>
> [1] https://people.apache.org/keys/committer/arjansh.asc
> [2] http://people.apache.org/keys/
>
> Den man. 9. sep. 2019 kl. 10.24 skrev Lutzen Luinenburg <
> l.luinenb...@humaninference.com>:
>
>> +1
>>
>>
>> Kind regards,
>>
>> Lútzen Luinenburg
>> Product Development Manager
>>
>>
>>
>>
>> -Original Message-
>> From: Arjan Seijkens Hagemans 
>> Sent: Monday, 9 September 2019 10:06
>> To: dev@metamodel.apache.org
>> Subject: [VOTE] Apache MetaModel release 5.3.1
>>
>> Hi All,
>>
>> Please vote on releasing the following candidate as Apache Metamodel
>> version 5.3.1.
>>
>> The Git tag to be voted on is MetaModel-5.3.1:
>>
>> https://gitbox.apache.org/repos/asf?p=metamodel.git;a=commit;h=1c6ab1fdb8f53415b86df05c9ed09b380b9eef61
>>
>> The source artifact to be voted on is:
>>
>> http://repository.apache.org/content/repositories/orgapachemetamodel-1042/org/apache/metamodel/MetaModel/5.3.1/MetaModel-5.3.1-source-release.zip
>>
>> Parent directory (including MD5, SHA1 hashes etc.) of the source is:
>>
>> http://repository.apache.org/content/repositories/orgapachemetamodel-1042/org/apache/metamodel/MetaModel/5.3.1/
>>
>> Release artifacts are signed with the following key:
>> https://people.apache.org/keys/committer/arjansh.asc
>>
>> Release engineer public key id: 750FB127
>>
>> The staging Maven repository for this release can be found at:
>> http://repository.apache.org/content/repositories/orgapachemetamodel-1042
>>
>> Please vote on releasing this package as Apache MetaModel 5.3.1.
>>
>> The vote is open for 72 hours.
>>
>> [ ] +1 Release this package as Apache MetaModel 5.3.1 [ ] -1 Do not
>> release this package because ...
>>
>> Thank you in advance for participating.
>>
>> Regards,
>> Arjan Seijkens
>>
>

Re: [VOTE] Apache MetaModel release 5.3.1

[Kasper Sørensen]

-1 because the referenced committer key file [1] does not seem to exist.
The apache people site [2] has some info on getting your key registered.

Willing to change my vote once the key file exists and the artifacts
signature matches it :-)

[1] https://people.apache.org/keys/committer/arjansh.asc
[2] http://people.apache.org/keys/

Den man. 9. sep. 2019 kl. 10.24 skrev Lutzen Luinenburg <
l.luinenb...@humaninference.com>:

> +1
>
>
> Kind regards,
>
> Lútzen Luinenburg
> Product Development Manager
>
>
>
>
> -Original Message-
> From: Arjan Seijkens Hagemans 
> Sent: Monday, 9 September 2019 10:06
> To: dev@metamodel.apache.org
> Subject: [VOTE] Apache MetaModel release 5.3.1
>
> Hi All,
>
> Please vote on releasing the following candidate as Apache Metamodel
> version 5.3.1.
>
> The Git tag to be voted on is MetaModel-5.3.1:
>
> https://gitbox.apache.org/repos/asf?p=metamodel.git;a=commit;h=1c6ab1fdb8f53415b86df05c9ed09b380b9eef61
>
> The source artifact to be voted on is:
>
> http://repository.apache.org/content/repositories/orgapachemetamodel-1042/org/apache/metamodel/MetaModel/5.3.1/MetaModel-5.3.1-source-release.zip
>
> Parent directory (including MD5, SHA1 hashes etc.) of the source is:
>
> http://repository.apache.org/content/repositories/orgapachemetamodel-1042/org/apache/metamodel/MetaModel/5.3.1/
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/arjansh.asc
>
> Release engineer public key id: 750FB127
>
> The staging Maven repository for this release can be found at:
> http://repository.apache.org/content/repositories/orgapachemetamodel-1042
>
> Please vote on releasing this package as Apache MetaModel 5.3.1.
>
> The vote is open for 72 hours.
>
> [ ] +1 Release this package as Apache MetaModel 5.3.1 [ ] -1 Do not
> release this package because ...
>
> Thank you in advance for participating.
>
> Regards,
> Arjan Seijkens
>

Announcement of new PMC Member: Arjan Seijken

[Kasper Sørensen]

Hi everybody,

I want to let you know that we've appointed a new PMC member for Apache
MetaModel: Arjan Seijkens. Congratulations to Arjan and thank you for all
your great contributions already. Great job!

Cheers,
Kasper

Re: Time for a release? Call for release engineers...

[Kasper Sørensen]

I'm looking into it, hang on.

Den tir. 20. aug. 2019 kl. 13.02 skrev Arjan Seijkens Hagemans <
arja...@gmail.com>:

> I started and I encountered a problem. I need to have  my public key added
> to the MetaModel KEYS file on SVN:
> https://dist.apache.org/repos/dist/release/metamodel/KEYS.
>
> I can't commit on that repository however. Do I need more permissions to do
> that or do I need to commit to another repository?
>
> Op di 20 aug. 2019 om 09:28 schreef Arjan Seijkens Hagemans <
> arja...@gmail.com>:
>
> > I'll just start with it and let you know if I encounter any problems.
> >
> > Op ma 19 aug. 2019 om 16:33 schreef Kasper Sørensen <
> > i.am.kasper.soren...@gmail.com>:
> >
> >> Perfect! Thanks Arjan!
> >>
> >> The process is documented on our Confluence wiki [1]. I hope it's all
> >> clear
> >> and as far as I can tell it is pretty complete. Can you skim through it
> >> and
> >> let me know what you think? Or just begin if you think it's looking
> good!
> >> :-)
> >>
> >> [1] https://cwiki.apache.org/confluence/display/METAMODEL/Release+guide
> >>
> >> Den man. 19. aug. 2019 kl. 09.30 skrev Arjan Seijkens Hagemans <
> >> arja...@gmail.com>:
> >>
> >> >  Hi Kasper,
> >> >
> >> >
> >> >
> >> > I would be willing to do/try this.
> >> >
> >> >
> >> >
> >> > Kind regards,
> >> >
> >> > Arjan Seijkens
> >> >
> >> >
> >> >
> >> > -Original Message-
> >> > From: Kasper Sørensen 
> >> > Sent: Wednesday, August 14, 2019 10:00 PM
> >> > To: dev@metamodel.apache.org
> >> > Subject: Time for a release? Call for release engineers...
> >> >
> >> >
> >> >
> >> > Hi all,
> >> >
> >> >
> >> >
> >> > I think we're close/ready to run another release of MetaModel. I have
> >> been
> >> > facilitating the release engineering process for a very long time and
> >> would
> >> > like to ask if someone else would like to do/try it? I will happily
> help
> >> > out and assist, but I think it would be great if someone else goes
> >> through
> >> > the process too. I think it will be good for us to have more people
> >> capable
> >> > of doing the release engineering work. It's mostly about setting up
> >> > signatures and stuff like that. Again, I can help via chat etc. to go
> >> > through the hurdles.
> >> >
> >> >
> >> >
> >> > Here are the WIP things based on the current CHANGES.md document:
> >> >
> >> >
> >> >
> >> >- [METAMODEL-1217] - Fixes dropping JDBC Tables with view as
> >> TableType
> >> >
> >> >- [METAMODEL-1215] - Removed deprecated code from pre-Java 8 times.
> >> >
> >> >- [METAMODEL-1214] - CompositeDataContext uses wrappedSchema for
> >> >
> >> >comparison when searching for it in the cache.
> >> >
> >> >- [METAMODEL-1213] - Fixed concurrency bug in single-line CSV
> >> parallel
> >> >
> >> >reader.
> >> >
> >> >- [METAMODEL-1211] - Fixed bug of getting all SelectItems when
> >> >
> >> >performing nested loop joins.
> >> >
> >> >- [METAMODEL-1151] - Created DataContextFactory implementations for
> >> each
> >> >
> >> >remaining module.
> >> >
> >> >- Improved HBase query building by scanning columns instead of
> column
> >> >
> >> >families.
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > Best regards,
> >> >
> >> > Kasper
> >> >
> >>
> >
>

Re: Time for a release? Call for release engineers...

[Kasper Sørensen]

Perfect! Thanks Arjan!

The process is documented on our Confluence wiki [1]. I hope it's all clear
and as far as I can tell it is pretty complete. Can you skim through it and
let me know what you think? Or just begin if you think it's looking good!
:-)

[1] https://cwiki.apache.org/confluence/display/METAMODEL/Release+guide

Den man. 19. aug. 2019 kl. 09.30 skrev Arjan Seijkens Hagemans <
arja...@gmail.com>:

>  Hi Kasper,
>
>
>
> I would be willing to do/try this.
>
>
>
> Kind regards,
>
> Arjan Seijkens
>
>
>
> -Original Message-
> From: Kasper Sørensen 
> Sent: Wednesday, August 14, 2019 10:00 PM
> To: dev@metamodel.apache.org
> Subject: Time for a release? Call for release engineers...
>
>
>
> Hi all,
>
>
>
> I think we're close/ready to run another release of MetaModel. I have been
> facilitating the release engineering process for a very long time and would
> like to ask if someone else would like to do/try it? I will happily help
> out and assist, but I think it would be great if someone else goes through
> the process too. I think it will be good for us to have more people capable
> of doing the release engineering work. It's mostly about setting up
> signatures and stuff like that. Again, I can help via chat etc. to go
> through the hurdles.
>
>
>
> Here are the WIP things based on the current CHANGES.md document:
>
>
>
>- [METAMODEL-1217] - Fixes dropping JDBC Tables with view as TableType
>
>- [METAMODEL-1215] - Removed deprecated code from pre-Java 8 times.
>
>- [METAMODEL-1214] - CompositeDataContext uses wrappedSchema for
>
>comparison when searching for it in the cache.
>
>- [METAMODEL-1213] - Fixed concurrency bug in single-line CSV parallel
>
>reader.
>
>- [METAMODEL-1211] - Fixed bug of getting all SelectItems when
>
>performing nested loop joins.
>
>- [METAMODEL-1151] - Created DataContextFactory implementations for each
>
>remaining module.
>
>- Improved HBase query building by scanning columns instead of column
>
>families.
>
>
>
>
>
> Best regards,
>
> Kasper
>

Time for a release? Call for release engineers...

[Kasper Sørensen]

Hi all,

I think we're close/ready to run another release of MetaModel. I have been
facilitating the release engineering process for a very long time and would
like to ask if someone else would like to do/try it? I will happily help
out and assist, but I think it would be great if someone else goes through
the process too. I think it will be good for us to have more people capable
of doing the release engineering work. It's mostly about setting up
signatures and stuff like that. Again, I can help via chat etc. to go
through the hurdles.

Here are the WIP things based on the current CHANGES.md document:

   - [METAMODEL-1217] - Fixes dropping JDBC Tables with view as TableType
   - [METAMODEL-1215] - Removed deprecated code from pre-Java 8 times.
   - [METAMODEL-1214] - CompositeDataContext uses wrappedSchema for
   comparison when searching for it in the cache.
   - [METAMODEL-1213] - Fixed concurrency bug in single-line CSV parallel
   reader.
   - [METAMODEL-1211] - Fixed bug of getting all SelectItems when
   performing nested loop joins.
   - [METAMODEL-1151] - Created DataContextFactory implementations for each
   remaining module.
   - Improved HBase query building by scanning columns instead of column
   families.


Best regards,
Kasper

Fwd: ApacheCon EU 2019 Travel Assistance Applications now open!

[Kasper Sørensen]

Hi MetaModel community,

I wanted to let you know of this opportunity for folks to go to the
ApacheCon conference in Berlin this year. I'm certain it will be good and
will likely go myself, but not sure yet. Contact the TAC people if you
would like to apply for financial assistance going there!

Best regards,
Kasper

-- Forwarded message -
Fra: Christofer Dutz 
Date: fre. 21. jun. 2019 kl. 09.56
Subject: ApacheCon EU 2019 Travel Assistance Applications now open!
To: 


Hi pmcs@!,

The Travel Assistance Committee (TAC) are pleased to announce that travel
assistance applications for ApacheCon EU 2019 are now open!

This announcement serves as a purpose for you (pmcs@) to let members of
your community know about both ApacheCon EU 2019 and about the TAC
assistance available to attend. Could you please forward this announcement
to your community, along with (if possible) information on how your project
is involved in ApacheCon this year?

We will be supporting ApacheCon EU, Berlin, Germany, 22nd - 24th October
2019.

TAC exists to help those that would like to attend ApacheCon events, but
are unable to do so for financial reasons. For more info on this years
applications and qualifying criteria, please visit the TAC website at <
https://www.apache.org/travel/ >. Applications are already open, so don't
delay!

*Important: Applications close on Wednesday, July 14th, 2019.*

Applicants have until the closing date above to submit their applications
(which should contain as much supporting material as required to
efficiently and accurately process their request), this will enable TAC to
announce successful awards shortly afterwards.

As usual, TAC expects to deal with a range of applications from a diverse
range of backgrounds; therefore, we encourage (as always) anyone thinking
about sending in an application to do so ASAP.

We look forward to greeting many of you in Berlin in Oktober, 2019!

Kind Regards,
Chris
(On behalf of the Travel Assistance Committee)

[RESULT] [VOTE] Apache MetaModel release 5.3.0

[Kasper Sørensen]

Hi everyone,

The vote has passed with 3 votes for, 0 against. Thank you all for voting.

Voters:
Kasper Sørensen *
Alberto Rodriguez *
Dennis Du Krøger *

 * = Indicates PMC

I'll continue with the release steps.

Best regards,
Kasper Sørensen

Den tir. 2. apr. 2019 kl. 10.09 skrev Dennis Krøger :

> +1
>
> On Mon, Apr 1, 2019 at 8:16 PM Kasper Sørensen <
> i.am.kasper.soren...@gmail.com> wrote:
>
> > Hi All,
> >
> > Please vote on releasing the following candidate as Apache Metamodel
> > version 5.3.0.
> >
> > The Git tag to be voted on is MetaModel-5.3.0:
> >
> >
> https://gitbox.apache.org/repos/asf?p=metamodel.git;a=commit;h=bfc9224f94a48851eeed3f0d43a88c1a1d527f8d
> >
> > The source artifact to be voted on is:
> >
> >
> http://repository.apache.org/content/repositories/orgapachemetamodel-1041/org/apache/metamodel/MetaModel/5.3.0/MetaModel-5.3.0-source-release.zip
> >
> > Parent directory (including MD5, SHA1 hashes etc.) of the source is:
> >
> >
> http://repository.apache.org/content/repositories/orgapachemetamodel-1041/org/apache/metamodel/MetaModel/5.3.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-1041
> >
> > Please vote on releasing this package as Apache MetaModel 5.3.0.
> >
> > The vote is open for 72 hours.
> >
> > [ ] +1 Release this package as Apache MetaModel 5.3.0
> > [ ] -1 Do not release this package because ...
> >
> > Thank you in advance for participating.
> >
> > Regards,
> > Kasper Sørensen
> >
>

Re: [VOTE] Apache MetaModel release 5.3.0

[Kasper Sørensen]

+1

Den man. 1. apr. 2019 kl. 11.16 skrev Kasper Sørensen <
i.am.kasper.soren...@gmail.com>:

> Hi All,
>
> Please vote on releasing the following candidate as Apache Metamodel
> version 5.3.0.
>
> The Git tag to be voted on is MetaModel-5.3.0:
>
> https://gitbox.apache.org/repos/asf?p=metamodel.git;a=commit;h=bfc9224f94a48851eeed3f0d43a88c1a1d527f8d
>
> The source artifact to be voted on is:
>
> http://repository.apache.org/content/repositories/orgapachemetamodel-1041/org/apache/metamodel/MetaModel/5.3.0/MetaModel-5.3.0-source-release.zip
>
> Parent directory (including MD5, SHA1 hashes etc.) of the source is:
>
> http://repository.apache.org/content/repositories/orgapachemetamodel-1041/org/apache/metamodel/MetaModel/5.3.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-1041
>
> Please vote on releasing this package as Apache MetaModel 5.3.0.
>
> The vote is open for 72 hours.
>
> [ ] +1 Release this package as Apache MetaModel 5.3.0
> [ ] -1 Do not release this package because ...
>
> Thank you in advance for participating.
>
> Regards,
> Kasper Sørensen
>

[VOTE] Apache MetaModel release 5.3.0

[Kasper Sørensen]

Hi All,

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

The Git tag to be voted on is MetaModel-5.3.0:
https://gitbox.apache.org/repos/asf?p=metamodel.git;a=commit;h=bfc9224f94a48851eeed3f0d43a88c1a1d527f8d

The source artifact to be voted on is:
http://repository.apache.org/content/repositories/orgapachemetamodel-1041/org/apache/metamodel/MetaModel/5.3.0/MetaModel-5.3.0-source-release.zip

Parent directory (including MD5, SHA1 hashes etc.) of the source is:
http://repository.apache.org/content/repositories/orgapachemetamodel-1041/org/apache/metamodel/MetaModel/5.3.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-1041

Please vote on releasing this package as Apache MetaModel 5.3.0.

The vote is open for 72 hours.

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

Thank you in advance for participating.

Regards,
Kasper Sørensen

Google Summer of Code 2019 Mentor Registration

[Kasper Sørensen]

Dear MetaModelers,

The Apache Software Foundation (ASF) has made it onto the list of accepted
organizations for Google Summer of Code 2019! [1, 2] In this email I'm
passing on the information for folks who would like to engage in it.

If you would like to mentor for this event, this is your chance. If you
aren’t already subscribed to ment...@community.apache.org you should do so
now else you might miss important information.

Mentor signup requires two steps: mentor signup in Google's system [3] and
PMC acknowledgement.

If you want to mentor a project in this year's SoC you will have to

1. Be an Apache committer.
2. Request an acknowledgement from the PMC for which you want to mentor
projects. Use the below
template and *do not forget to copy ment...@community.apache.org*. We will
use the email adress you
indicate to send the invite to be a mentor for Apache.

PMCs, read carefully please.

We request that each mentor is acknowledged by a PMC member. This is to
ensure the mentor is in good
standing with the community. When you receive a request for
acknowledgement, please ACK it and cc
ment...@community.apache.org

Best regards,
Kasper

mentor request email template:

to: private@.apache.org
cc: ment...@community.apache.org
subject: GSoC 2019 mentor request for 

 PMC,

please acknowledge my request to become a mentor for Google Summer of Code
2018 projects for Apache
.

I would like to receive the mentor invite to 


---

[1] https://summerofcode.withgoogle.com/organizations/
[2] https://summerofcode.withgoogle.com/organizations/6614885824200704/
[3] https://summerofcode.withgoogle.com/

[RESULT] [VOTE] Apache Metamodel release 5.2.1

[Kasper Sørensen]

Hi everyone,

The vote is over and we have agreement to release. I forgot to cast my vote
myself, which would have been a +1, so given that, we have 4 votes for,
none against.

I'll continue the release process then.

Best regards,
Kasper



>
> Den tir. 5. mar. 2019 kl. 16.59 skrev xiaobao li  >:
>
>> +1
>>
>> Kasper Sørensen  于2019年3月5日周二 下午1:11写道：
>>
>> > Hi All,
>> >
>> > Please vote on releasing the following candidate as Apache Metamodel
>> > version 5.2.1.
>> >
>> > The Git tag to be voted on is MetaModel-5.2.1:
>> >
>> >
>> https://gitbox.apache.org/repos/asf?p=metamodel.git;a=tag;h=387c2f76c6ebb9df8c806de06a491bb0f578e8f1
>> >
>> > The source artifact to be voted on is:
>> >
>> >
>> https://repository.apache.org/content/repositories/orgapachemetamodel-1040/org/apache/metamodel/MetaModel/5.2.1/MetaModel-5.2.1-source-release.zip
>> >
>> > Parent directory (including MD5, SHA1 hashes etc.) of the source is:
>> >
>> >
>> https://repository.apache.org/content/repositories/orgapachemetamodel-1040/org/apache/metamodel/MetaModel/5.2.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-1040
>> >
>> > Please vote on releasing this package as Apache MetaModel 5.2.1.
>> >
>> > The vote is open for 72 hours.
>> >
>> > [ ] +1 Release this package as Apache MetaModel 5.2.1
>> > [ ] -1 Do not release this package because ...
>> >
>> > Thank you in advance for participating.
>> >
>> > Regards,
>> > Kasper Sørensen
>> >
>>
>

Re: [VOTE] Apache Metamodel release 5.2.1

[Kasper Sørensen]

Hi everyone,

The vote is over and we have agreement to release. I forgot to cast my vote
myself, which would have been a +1, so given that, we have 4 votes for,
none against.

I'll continue the release process then.

Best regards,
Kasper

Den tir. 5. mar. 2019 kl. 16.59 skrev xiaobao li :

> +1
>
> Kasper Sørensen  于2019年3月5日周二 下午1:11写道：
>
> > Hi All,
> >
> > Please vote on releasing the following candidate as Apache Metamodel
> > version 5.2.1.
> >
> > The Git tag to be voted on is MetaModel-5.2.1:
> >
> >
> https://gitbox.apache.org/repos/asf?p=metamodel.git;a=tag;h=387c2f76c6ebb9df8c806de06a491bb0f578e8f1
> >
> > The source artifact to be voted on is:
> >
> >
> https://repository.apache.org/content/repositories/orgapachemetamodel-1040/org/apache/metamodel/MetaModel/5.2.1/MetaModel-5.2.1-source-release.zip
> >
> > Parent directory (including MD5, SHA1 hashes etc.) of the source is:
> >
> >
> https://repository.apache.org/content/repositories/orgapachemetamodel-1040/org/apache/metamodel/MetaModel/5.2.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-1040
> >
> > Please vote on releasing this package as Apache MetaModel 5.2.1.
> >
> > The vote is open for 72 hours.
> >
> > [ ] +1 Release this package as Apache MetaModel 5.2.1
> > [ ] -1 Do not release this package because ...
> >
> > Thank you in advance for participating.
> >
> > Regards,
> > Kasper Sørensen
> >
>

[VOTE] Apache Metamodel release 5.2.1

[Kasper Sørensen]

Hi All,

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

The Git tag to be voted on is MetaModel-5.2.1:
https://gitbox.apache.org/repos/asf?p=metamodel.git;a=tag;h=387c2f76c6ebb9df8c806de06a491bb0f578e8f1

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

Parent directory (including MD5, SHA1 hashes etc.) of the source is:
https://repository.apache.org/content/repositories/orgapachemetamodel-1040/org/apache/metamodel/MetaModel/5.2.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-1040

Please vote on releasing this package as Apache MetaModel 5.2.1.

The vote is open for 72 hours.

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

Thank you in advance for participating.

Regards,
Kasper Sørensen

Re: Pool + timer threads in JdbcCompiledQuery

[Kasper Sørensen]

HI Dana,

The CompiledQuery is intended for reuse, so the fact that you re-create it
for every query is the crux of the issue here. If you don't intend to reuse
the query, then you don't have any benefit in compiling it. So your
solutions could either be:

(1) Don't use compiled query, just execute a normal query.
(2) Save the compiled query and reuse it across many/all requests. This
will likely be higher performing but of course will make the web layer more
stateful. One nice thing I'll add though is that compiled queries are
thread safe, so you don't have to worry about race conditions or such.

Best regards,
Kasper


Den fre. 22. feb. 2019 kl. 12.57 skrev Dana Borger :

>
> Hi group --
>
> We have a service that’s doing high volumes of queries using
> JdbcCompiledQuery. On MM 5.0.
>
> Our usage is basically: requests come in via REST, then the following code
> is done, and the result returned. We’re not running queries in a loop or
> re-using JdbcCompiledQuery objects, they just get created and closed and
> fall out of scope after each request. There are multiple threads doing same
> thing, but potentially with different queries.
>
>
> try (CompiledQuery compiledQuery = dataContext.compileQuery(...) {  //
> dataContext is JdbcDataContext
> result = doExecute(compiledQuery, ...);
> }
>
> This closes the compiled-query, which in turn closes the generic object
> pool inside it, which has an evictor / timer thread inside.
>
> The issue we’re observing is under certain heavy loads we start piling up
> new Java timer threads by the thousands, eventually leading to “cannot
> create thread” exceptions. This seems to be timing dependent, probably due
> to the Evictor’s timer and this always-closing of the compiled-query.
>
> So, we’re looking for some guidance on this. For example, what use cases
> make the pool inside JdbcCompiledQuery beneficial?
>
> Our use case doesn’t seem that unusual, and we’ll need to fix it somehow.
> We tried a patched version of JdbcCompiledQuery that doesn’t use an
> object-pool+timer and that seems to fix the thread issue w/o any new
> negative effects.
>
> Thanks much for any advice,
> Dana
>
>

Re: [RESULT] [VOTE] Initiate the migration to Apache gitbox

[Kasper Sørensen]

Hi everyone,

Just as a courtesy, I wanted to share the proper NEW git remote URL for
your "git clone" or "git remote add" statements:
MetaModel: https://gitbox.apache.org/repos/asf/metamodel.git
MetaModel membrane:
https://gitbox.apache.org/repos/asf/metamodel-membrane.git

So...
Cloning MetaModel anew:
> git clone https://gitbox.apache.org/repos/asf/metamodel.git

Or just adding a new remote called 'gitbox':
> git remote add gitbox https://gitbox.apache.org/repos/asf/metamodel.git

Took me a couple of minutes of research to figure out, so I thought to
share it after all that ;-)

Den tor. 10. jan. 2019 kl. 18.10 skrev Kasper Sørensen <
i.am.kasper.soren...@gmail.com>:

> INFRA ticket is here: https://issues.apache.org/jira/browse/INFRA-17614
>
> Den tor. 10. jan. 2019 kl. 18.06 skrev Kasper Sørensen <
> i.am.kasper.soren...@gmail.com>:
>
>> Looks like we have a decision: 4 votes for, none against.
>>
>> I will let INFRA know. Thank you for participating.
>>
>> Den tor. 10. jan. 2019 kl. 03.44 skrev Alberto Rodriguez <
>> ardl...@gmail.com>:
>>
>>> +1
>>>
>>> El jue., 10 ene. 2019 a las 6:31, Dennis Krøger ()
>>> escribió:
>>>
>>> > +1
>>> >
>>> > On Tue, Jan 8, 2019 at 8:11 AM Arjan Seijkens >> >
>>> > wrote:
>>> >
>>> > > +1
>>> > >
>>> > > -Original Message-
>>> > > From: Kasper Sørensen 
>>> > > Sent: Tuesday, January 8, 2019 1:16 AM
>>> > > To: dev@metamodel.apache.org
>>> > > Subject: Re: [VOTE] Initiate the migration to Apache gitbox
>>> > >
>>> > > +1
>>> > >
>>> > > Den man. 7. jan. 2019 kl. 16.15 skrev Kasper Sørensen <
>>> > > i.am.kasper.soren...@gmail.com>:
>>> > >
>>> > > > Hi all,
>>> > > >
>>> > > > As you have maybe seen in the mail thread "[NOTICE] Mandatory
>>> > > > migration of git repositories to gitbox.apache.org" [1], we need
>>> to
>>> > > > change our Git repository to be hosted by Apache gitbox. This
>>> happens
>>> > > > automatically on Feb 7, but INFRA would like to do it earlier for
>>> > > > those projects that are capable of doing that.
>>> > > >
>>> > > > I think we're ready to do it. Let's have a VOTE for the next 72
>>> hours
>>> > > > and unless there are compelling reasons to NOT move, we shall let
>>> > > > INFRA know that we're ready.
>>> > > >
>>> > > > Best regards,
>>> > > > Kasper
>>> > > >
>>> > > > [1]
>>> > > >
>>> http://mail-archives.apache.org/mod_mbox/metamodel-dev/201901.mbox/
>>> > > > <154652152635.18883.1644020783020365096.gitbox%40gitbox.apache.org
>>> >
>>> > > >
>>> > >
>>> >
>>>
>>

Re: [JDBC][MySQL] Schema for integration test

[Kasper Sørensen]

Hi Ratish,

Glad that you're looking to do some contributions to MetaModel :-)

The integration test data is usually documented in the javadoc of the test
class itself. So for MySQL, check out this class documentation:
https://github.com/apache/metamodel/blob/master/jdbc/src/test/java/org/apache/metamodel/jdbc/integrationtests/MysqlTest.java

As for Travis CI, it doesn't run _all_ the integration tests, only the ones
that are enabled in the
/travis-metamodel-integrationtest-configuration.properties file. Take a
look at /.travis.yml to see hwo it is set up with things like Docker,
CouchDB etc. I don't believe MySQL is one of the ones that are enabled in
Travis CI though.

Best regards,
Kasper

Den tor. 17. jan. 2019 kl. 12.20 skrev RATISH BANSAL :

> Hello,
>
> I want to start contributing to the Apache metamodel project, so pulled the
> latest code and tried to set things up.When I tried running the integration
> tests for MySQL they stared failing because the expected schema is not
> present in my configured MySQL database.Can you please guide, where to look
> for the expected schema.Do we have any db dump somewhere?
>
> Also curious to know how integration tests run in Travis CI ? Who provide
> and how do we configure all database servers with required testcase schema?
>
> Thanks & Regards
> Ratish Bansal
>

[RESULT] [VOTE] Initiate the migration to Apache gitbox

[Kasper Sørensen]

Looks like we have a decision: 4 votes for, none against.

I will let INFRA know. Thank you for participating.

Den tor. 10. jan. 2019 kl. 03.44 skrev Alberto Rodriguez :

> +1
>
> El jue., 10 ene. 2019 a las 6:31, Dennis Krøger ()
> escribió:
>
> > +1
> >
> > On Tue, Jan 8, 2019 at 8:11 AM Arjan Seijkens 
> > wrote:
> >
> > > +1
> > >
> > > -Original Message-
> > > From: Kasper Sørensen 
> > > Sent: Tuesday, January 8, 2019 1:16 AM
> > > To: dev@metamodel.apache.org
> > > Subject: Re: [VOTE] Initiate the migration to Apache gitbox
> > >
> > > +1
> > >
> > > Den man. 7. jan. 2019 kl. 16.15 skrev Kasper Sørensen <
> > > i.am.kasper.soren...@gmail.com>:
> > >
> > > > Hi all,
> > > >
> > > > As you have maybe seen in the mail thread "[NOTICE] Mandatory
> > > > migration of git repositories to gitbox.apache.org" [1], we need to
> > > > change our Git repository to be hosted by Apache gitbox. This happens
> > > > automatically on Feb 7, but INFRA would like to do it earlier for
> > > > those projects that are capable of doing that.
> > > >
> > > > I think we're ready to do it. Let's have a VOTE for the next 72 hours
> > > > and unless there are compelling reasons to NOT move, we shall let
> > > > INFRA know that we're ready.
> > > >
> > > > Best regards,
> > > > Kasper
> > > >
> > > > [1]
> > > > http://mail-archives.apache.org/mod_mbox/metamodel-dev/201901.mbox/
> > > > <154652152635.18883.1644020783020365096.gitbox%40gitbox.apache.org>
> > > >
> > >
> >
>

Re: [RESULT] [VOTE] Initiate the migration to Apache gitbox

[Kasper Sørensen]

INFRA ticket is here: https://issues.apache.org/jira/browse/INFRA-17614

Den tor. 10. jan. 2019 kl. 18.06 skrev Kasper Sørensen <
i.am.kasper.soren...@gmail.com>:

> Looks like we have a decision: 4 votes for, none against.
>
> I will let INFRA know. Thank you for participating.
>
> Den tor. 10. jan. 2019 kl. 03.44 skrev Alberto Rodriguez <
> ardl...@gmail.com>:
>
>> +1
>>
>> El jue., 10 ene. 2019 a las 6:31, Dennis Krøger ()
>> escribió:
>>
>> > +1
>> >
>> > On Tue, Jan 8, 2019 at 8:11 AM Arjan Seijkens 
>> > wrote:
>> >
>> > > +1
>> > >
>> > > -Original Message-
>> > > From: Kasper Sørensen 
>> > > Sent: Tuesday, January 8, 2019 1:16 AM
>> > > To: dev@metamodel.apache.org
>> > > Subject: Re: [VOTE] Initiate the migration to Apache gitbox
>> > >
>> > > +1
>> > >
>> > > Den man. 7. jan. 2019 kl. 16.15 skrev Kasper Sørensen <
>> > > i.am.kasper.soren...@gmail.com>:
>> > >
>> > > > Hi all,
>> > > >
>> > > > As you have maybe seen in the mail thread "[NOTICE] Mandatory
>> > > > migration of git repositories to gitbox.apache.org" [1], we need to
>> > > > change our Git repository to be hosted by Apache gitbox. This
>> happens
>> > > > automatically on Feb 7, but INFRA would like to do it earlier for
>> > > > those projects that are capable of doing that.
>> > > >
>> > > > I think we're ready to do it. Let's have a VOTE for the next 72
>> hours
>> > > > and unless there are compelling reasons to NOT move, we shall let
>> > > > INFRA know that we're ready.
>> > > >
>> > > > Best regards,
>> > > > Kasper
>> > > >
>> > > > [1]
>> > > > http://mail-archives.apache.org/mod_mbox/metamodel-dev/201901.mbox/
>> > > > <154652152635.18883.1644020783020365096.gitbox%40gitbox.apache.org>
>> > > >
>> > >
>> >
>>
>

Re: [VOTE] Initiate the migration to Apache gitbox

[Kasper Sørensen]

+1

Den man. 7. jan. 2019 kl. 16.15 skrev Kasper Sørensen <
i.am.kasper.soren...@gmail.com>:

> Hi all,
>
> As you have maybe seen in the mail thread "[NOTICE] Mandatory migration of
> git repositories to gitbox.apache.org" [1], we need to change our Git
> repository to be hosted by Apache gitbox. This happens automatically on Feb
> 7, but INFRA would like to do it earlier for those projects that are
> capable of doing that.
>
> I think we're ready to do it. Let's have a VOTE for the next 72 hours and
> unless there are compelling reasons to NOT move, we shall let INFRA know
> that we're ready.
>
> Best regards,
> Kasper
>
> [1] http://mail-archives.apache.org/mod_mbox/metamodel-dev/201901.mbox/
> <154652152635.18883.1644020783020365096.gitbox%40gitbox.apache.org>
>

[VOTE] Initiate the migration to Apache gitbox

[Kasper Sørensen]

Hi all,

As you have maybe seen in the mail thread "[NOTICE] Mandatory migration of
git repositories to gitbox.apache.org" [1], we need to change our Git
repository to be hosted by Apache gitbox. This happens automatically on Feb
7, but INFRA would like to do it earlier for those projects that are
capable of doing that.

I think we're ready to do it. Let's have a VOTE for the next 72 hours and
unless there are compelling reasons to NOT move, we shall let INFRA know
that we're ready.

Best regards,
Kasper

[1] http://mail-archives.apache.org/mod_mbox/metamodel-dev/201901.mbox/
<154652152635.18883.1644020783020365096.gitbox%40gitbox.apache.org>

Re: [JDBC] Support to capture Auto Increment, Auto Generated as part of column metadata

[Kasper Sørensen]

Hi Ratish,

Thank you very much for raising this issue/discussion. I wonder: In JDBC
it's only possible to get the auto-incremented value for a single column.
That was also the inspiration for the way the metamodel API was designed I
think. So that leads me to think - is it even meaningful for this generated
key to be on anything else than the primary key column? MetaModel does have
a way to get the primary key column. So although there's a bit of an
assumptions going on from my side here, but doesn't that also fit your use
case, that you could just use the primary key column of the table?

Best regards,
Kasper

Den ons. 2. jan. 2019 kl. 05.35 skrev RATISH BANSAL :

> Hello,
>
> *Use case:* I was using Apache Meta Model 5.2.0 in my project.There is
> MySQL source with Table Customer. Customer table has column Id which is
> primary key and marked auto increment.
> The use case is to get the generated *Id *in return when we insert the
> record so that user can again query using same returned *Id *to get the
> record back if required.
>
> The returning of generated keys has been fixed sometime back by introducing
> Update Summary, but update summary does not tell us what is the column name
> of that generated value being returned.i.e it just return the value being
> generated.
>
> Possible solution could be if  somehow we know before hand from column
> metadata what column is marked auto increment/ auto generated.This way we
> can expect the same in return.
>
> *Problem: *Current meta model implementation doesn't capture this auto
> increment property like others i.e name,data types etc; even though the
> underlying driver is returning the information.
>
> *Technical's:*  While debugging through the code for MySQL source ,observed
> that in loadColumns method in JdbcMetadataLoader class we obtain the
> ResultSet from the driver implementation class.This ResultSet has the
> required information at index 23 i.e rs.getString(23) but we only capture
> certain important information like name, datatype etc and create JdbcColumn
> from those.
> The solution can be, introducing another variable to capture this property
> as well just like others.
> Tried the same with PostgreSQL and behavior is similar. The value can be
> null if this information is supported by any source.
>
> It would be great if you could share your thoughts on this.Are there any
> plans for such changes in future.
>
> Thanks & Regards
> Ratish Bansal
>

Re: [RESULT] [VOTE] Apache MetaModel release 5.2.0

[Kasper Sørensen]

Better late than never ... I finally got around to publish the release on
dist.apache.org and update the website!

Cheers and congratulations on another good Apache MetaModel version!

Den tir. 11. dec. 2018 kl. 21.57 skrev Kasper Sørensen <
i.am.kasper.soren...@gmail.com>:

> Hi all,
>
> I'm glad to say that the VOTE has PASSED. There where 6 votes for, and
> none against:
>
> Kasper Sørensen *
> Lutzen Luinenburg
> Henry Saputra *
> Arjan Seijkens
> Alberto Rodriguez *
> Dennis Krøger *
>
> * = indicates PMC
>
> I will go click the "Release" button in the Nexus repository manager now.
> But unfortunately I am dealing with a family emergency also right now so I
> don't have time to sit down and upload artifacts to dist.apache.org and
> update the website right now. If someone else can do that, it would be
> greatly appreciated. Or else I will be back in a couple of days. Thank you.
>
> Kasper
>
> Den tir. 11. dec. 2018 kl. 01.00 skrev Dennis Krøger :
>
>> +1
>>
>> On Sat, Dec 8, 2018 at 7:38 PM Kasper Sørensen <
>> i.am.kasper.soren...@gmail.com> wrote:
>>
>> > Hi All,
>> >
>> > I've staged a release of Apache Metamodel version 5.2.0 and would like
>> to
>> > call for a vote on releasing it.
>> >
>> > The Git tag to be voted on is MetaModel-5.2.0:
>> >
>> >
>> https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=6cb8a164b8b1a4b4bccbd5234b7d05525a819ca9
>> >
>> > The source artifact to be voted on is:
>> >
>> >
>> http://repository.apache.org/content/repositories/orgapachemetamodel-1039/org/apache/metamodel/MetaModel/5.2.0/MetaModel-5.2.0-source-release.zip
>> >
>> > Parent directory (including MD5, SHA1 hashes etc.) of the source is:
>> >
>> >
>> http://repository.apache.org/content/repositories/orgapachemetamodel-1039/org/apache/metamodel/MetaModel/5.2.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-1039
>> >
>> > Please vote on releasing this package as Apache MetaModel 5.2.0.
>> >
>> > The vote is open for 72 hours.
>> >
>> > [ ] +1 Release this package as Apache MetaModel 5.2.0
>> > [ ] -1 Do not release this package because ...
>> >
>> > Thank you in advance for participating.
>> >
>> > Regards,
>> > Kasper
>> >
>>
>

[RESULT] [VOTE] Apache MetaModel release 5.2.0

[Kasper Sørensen]

Hi all,

I'm glad to say that the VOTE has PASSED. There where 6 votes for, and none
against:

Kasper Sørensen *
Lutzen Luinenburg
Henry Saputra *
Arjan Seijkens
Alberto Rodriguez *
Dennis Krøger *

* = indicates PMC

I will go click the "Release" button in the Nexus repository manager now.
But unfortunately I am dealing with a family emergency also right now so I
don't have time to sit down and upload artifacts to dist.apache.org and
update the website right now. If someone else can do that, it would be
greatly appreciated. Or else I will be back in a couple of days. Thank you.

Kasper

Den tir. 11. dec. 2018 kl. 01.00 skrev Dennis Krøger :

> +1
>
> On Sat, Dec 8, 2018 at 7:38 PM Kasper Sørensen <
> i.am.kasper.soren...@gmail.com> wrote:
>
> > Hi All,
> >
> > I've staged a release of Apache Metamodel version 5.2.0 and would like to
> > call for a vote on releasing it.
> >
> > The Git tag to be voted on is MetaModel-5.2.0:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=6cb8a164b8b1a4b4bccbd5234b7d05525a819ca9
> >
> > The source artifact to be voted on is:
> >
> >
> http://repository.apache.org/content/repositories/orgapachemetamodel-1039/org/apache/metamodel/MetaModel/5.2.0/MetaModel-5.2.0-source-release.zip
> >
> > Parent directory (including MD5, SHA1 hashes etc.) of the source is:
> >
> >
> http://repository.apache.org/content/repositories/orgapachemetamodel-1039/org/apache/metamodel/MetaModel/5.2.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-1039
> >
> > Please vote on releasing this package as Apache MetaModel 5.2.0.
> >
> > The vote is open for 72 hours.
> >
> > [ ] +1 Release this package as Apache MetaModel 5.2.0
> > [ ] -1 Do not release this package because ...
> >
> > Thank you in advance for participating.
> >
> > Regards,
> > Kasper
> >
>

Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

[Kasper Sørensen]

Yes that sounds good. I’ll start a vote after the 5.2.0 release.

Kasper Sørensen

> On Dec 10, 2018, at 08:41, Henry Saputra  wrote:
> 
> I think we need to get "consensus" for early on boarding: "Consensus in the
> project (documented via the mailing list)"
> 
> Or we could sit tight and coming along as later batch.
> 
> Thanks,
> 
> - Henry
> 
> On Sun, Dec 9, 2018 at 5:06 PM Kasper Sørensen <
> i.am.kasper.soren...@gmail.com> wrote:
> 
>> The way I read Daniel Gruno's mail, it doesn't sound like we have much
>> choice to even vote on it? :-) Or do you mean we should vote to do it
>> sooner than later?
>> 
>> Den søn. 9. dec. 2018 kl. 11.03 skrev Henry Saputra <
>> henry.sapu...@gmail.com
>>> :
>> 
>>> Thanks, Kasper. I think we could just do VOTE to move to gitbox in
>> parallel
>>> along with release one.
>>> 
>>> - Henry
>>> 
>>> On Sat, Dec 8, 2018 at 10:37 PM Kasper Sørensen <
>>> i.am.kasper.soren...@gmail.com> wrote:
>>> 
>>>> Heads up everybody. The MetaModel repo is hosted on the git-wip-us
>>> server,
>>>> and as per the mail below it seems we need to move over to other
>> servers.
>>>> 
>>>> I suggest we complete the current release VOTE before we do anything.
>>> But I
>>>> also don't see any reason to wait much longer than that. Most of our
>>>> committers use the github mirror AFAIK.
>>>> 
>>>> 
>>>> -- Forwarded message -
>>>> From: Daniel Gruno 
>>>> Date: fre. 7. dec. 2018 kl. 08.53
>>>> Subject: [NOTICE] Mandatory relocation of Apache git repositories on
>>>> git-wip-us.apache.org
>>>> To: us...@infra.apache.org 
>>>> 
>>>> 
>>>> [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
>>>>  DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS]
>>>> 
>>>> Hello Apache projects,
>>>> 
>>>> I am writing to you because you may have git repositories on the
>>>> git-wip-us server, which is slated to be decommissioned in the coming
>>>> months. All repositories will be moved to the new gitbox service which
>>>> includes direct write access on github as well as the standard ASF
>>>> commit access via gitbox.apache.org.
>>>> 
>>>> ## Why this move? ##
>>>> The move comes as a result of retiring the git-wip service, as the
>>>> hardware it runs on is longing for retirement. In lieu of this, we
>>>> have decided to consolidate the two services (git-wip and gitbox), to
>>>> ease the management of our repository systems and future-proof the
>>>> underlying hardware. The move is fully automated, and ideally, nothing
>>>> will change in your workflow other than added features and access to
>>>> GitHub.
>>>> 
>>>> ## Timeframe for relocation ##
>>>> Initially, we are asking that projects voluntarily request to move
>>>> their repositories to gitbox, hence this email. The voluntary
>>>> timeframe is between now and January 9th 2019, during which projects
>>>> are free to either move over to gitbox or stay put on git-wip. After
>>>> this phase, we will be requiring the remaining projects to move within
>>>> one month, after which we will move the remaining projects over.
>>>> 
>>>> To have your project moved in this initial phase, you will need:
>>>> 
>>>> - Consensus in the project (documented via the mailing list)
>>>> - File a JIRA ticket with INFRA to voluntarily move your project repos
>>>>   over to gitbox (as stated, this is highly automated and will take
>>>>   between a minute and an hour, depending on the size and number of
>>>>   your repositories)
>>>> 
>>>> To sum up the preliminary timeline;
>>>> 
>>>> - December 9th 2018 -> January 9th 2019: Voluntary (coordinated)
>>>>   relocation
>>>> - January 9th -> February 6th: Mandated (coordinated) relocation
>>>> - February 7th: All remaining repositories are mass migrated.
>>>> 
>>>> This timeline may change to accommodate various scenarios.
>>>> 
>>>> ## Using GitHub with ASF repositories ##
>>>> When your project has moved, you are free to use either the ASF
>>>> repository system (gitbox.apache.org) OR GitHub for your development
>>>> and code pushes. To be able to use GitHub, please follow the primer
>>>> at: https://reference.apache.org/committer/github
>>>> 
>>>> 
>>>> We appreciate your understanding of this issue, and hope that your
>>>> project can coordinate voluntarily moving your repositories in a
>>>> timely manner.
>>>> 
>>>> All settings, such as commit mail targets, issue linking, PR
>>>> notification schemes etc will automatically be migrated to gitbox as
>>>> well.
>>>> 
>>>> With regards, Daniel on behalf of ASF Infra.
>>>> 
>>>> PS:For inquiries, please reply to us...@infra.apache.org, not your
>>>> project's dev list :-).
>>>> 
>>> 
>> 

Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

[Kasper Sørensen]

The way I read Daniel Gruno's mail, it doesn't sound like we have much
choice to even vote on it? :-) Or do you mean we should vote to do it
sooner than later?

Den søn. 9. dec. 2018 kl. 11.03 skrev Henry Saputra :

> Thanks, Kasper. I think we could just do VOTE to move to gitbox in parallel
> along with release one.
>
> - Henry
>
> On Sat, Dec 8, 2018 at 10:37 PM Kasper Sørensen <
> i.am.kasper.soren...@gmail.com> wrote:
>
> > Heads up everybody. The MetaModel repo is hosted on the git-wip-us
> server,
> > and as per the mail below it seems we need to move over to other servers.
> >
> > I suggest we complete the current release VOTE before we do anything.
> But I
> > also don't see any reason to wait much longer than that. Most of our
> > committers use the github mirror AFAIK.
> >
> >
> > -- Forwarded message -
> > From: Daniel Gruno 
> > Date: fre. 7. dec. 2018 kl. 08.53
> > Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> > git-wip-us.apache.org
> > To: us...@infra.apache.org 
> >
> >
> > [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
> >   DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS]
> >
> > Hello Apache projects,
> >
> > I am writing to you because you may have git repositories on the
> > git-wip-us server, which is slated to be decommissioned in the coming
> > months. All repositories will be moved to the new gitbox service which
> > includes direct write access on github as well as the standard ASF
> > commit access via gitbox.apache.org.
> >
> > ## Why this move? ##
> > The move comes as a result of retiring the git-wip service, as the
> > hardware it runs on is longing for retirement. In lieu of this, we
> > have decided to consolidate the two services (git-wip and gitbox), to
> > ease the management of our repository systems and future-proof the
> > underlying hardware. The move is fully automated, and ideally, nothing
> > will change in your workflow other than added features and access to
> > GitHub.
> >
> > ## Timeframe for relocation ##
> > Initially, we are asking that projects voluntarily request to move
> > their repositories to gitbox, hence this email. The voluntary
> > timeframe is between now and January 9th 2019, during which projects
> > are free to either move over to gitbox or stay put on git-wip. After
> > this phase, we will be requiring the remaining projects to move within
> > one month, after which we will move the remaining projects over.
> >
> > To have your project moved in this initial phase, you will need:
> >
> > - Consensus in the project (documented via the mailing list)
> > - File a JIRA ticket with INFRA to voluntarily move your project repos
> >over to gitbox (as stated, this is highly automated and will take
> >between a minute and an hour, depending on the size and number of
> >your repositories)
> >
> > To sum up the preliminary timeline;
> >
> > - December 9th 2018 -> January 9th 2019: Voluntary (coordinated)
> >relocation
> > - January 9th -> February 6th: Mandated (coordinated) relocation
> > - February 7th: All remaining repositories are mass migrated.
> >
> > This timeline may change to accommodate various scenarios.
> >
> > ## Using GitHub with ASF repositories ##
> > When your project has moved, you are free to use either the ASF
> > repository system (gitbox.apache.org) OR GitHub for your development
> > and code pushes. To be able to use GitHub, please follow the primer
> > at: https://reference.apache.org/committer/github
> >
> >
> > We appreciate your understanding of this issue, and hope that your
> > project can coordinate voluntarily moving your repositories in a
> > timely manner.
> >
> > All settings, such as commit mail targets, issue linking, PR
> > notification schemes etc will automatically be migrated to gitbox as
> > well.
> >
> > With regards, Daniel on behalf of ASF Infra.
> >
> > PS:For inquiries, please reply to us...@infra.apache.org, not your
> > project's dev list :-).
> >
>

Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

[Kasper Sørensen]

Heads up everybody. The MetaModel repo is hosted on the git-wip-us server,
and as per the mail below it seems we need to move over to other servers.

I suggest we complete the current release VOTE before we do anything. But I
also don't see any reason to wait much longer than that. Most of our
committers use the github mirror AFAIK.


-- Forwarded message -
From: Daniel Gruno 
Date: fre. 7. dec. 2018 kl. 08.53
Subject: [NOTICE] Mandatory relocation of Apache git repositories on
git-wip-us.apache.org
To: us...@infra.apache.org 


[IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
  DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS]

Hello Apache projects,

I am writing to you because you may have git repositories on the
git-wip-us server, which is slated to be decommissioned in the coming
months. All repositories will be moved to the new gitbox service which
includes direct write access on github as well as the standard ASF
commit access via gitbox.apache.org.

## Why this move? ##
The move comes as a result of retiring the git-wip service, as the
hardware it runs on is longing for retirement. In lieu of this, we
have decided to consolidate the two services (git-wip and gitbox), to
ease the management of our repository systems and future-proof the
underlying hardware. The move is fully automated, and ideally, nothing
will change in your workflow other than added features and access to
GitHub.

## Timeframe for relocation ##
Initially, we are asking that projects voluntarily request to move
their repositories to gitbox, hence this email. The voluntary
timeframe is between now and January 9th 2019, during which projects
are free to either move over to gitbox or stay put on git-wip. After
this phase, we will be requiring the remaining projects to move within
one month, after which we will move the remaining projects over.

To have your project moved in this initial phase, you will need:

- Consensus in the project (documented via the mailing list)
- File a JIRA ticket with INFRA to voluntarily move your project repos
   over to gitbox (as stated, this is highly automated and will take
   between a minute and an hour, depending on the size and number of
   your repositories)

To sum up the preliminary timeline;

- December 9th 2018 -> January 9th 2019: Voluntary (coordinated)
   relocation
- January 9th -> February 6th: Mandated (coordinated) relocation
- February 7th: All remaining repositories are mass migrated.

This timeline may change to accommodate various scenarios.

## Using GitHub with ASF repositories ##
When your project has moved, you are free to use either the ASF
repository system (gitbox.apache.org) OR GitHub for your development
and code pushes. To be able to use GitHub, please follow the primer
at: https://reference.apache.org/committer/github


We appreciate your understanding of this issue, and hope that your
project can coordinate voluntarily moving your repositories in a
timely manner.

All settings, such as commit mail targets, issue linking, PR
notification schemes etc will automatically be migrated to gitbox as
well.

With regards, Daniel on behalf of ASF Infra.

PS:For inquiries, please reply to us...@infra.apache.org, not your
project's dev list :-).

[VOTE] Apache MetaModel release 5.2.0

[Kasper Sørensen]

Hi All,

I've staged a release of Apache Metamodel version 5.2.0 and would like to
call for a vote on releasing it.

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

The source artifact to be voted on is:
http://repository.apache.org/content/repositories/orgapachemetamodel-1039/org/apache/metamodel/MetaModel/5.2.0/MetaModel-5.2.0-source-release.zip

Parent directory (including MD5, SHA1 hashes etc.) of the source is:
http://repository.apache.org/content/repositories/orgapachemetamodel-1039/org/apache/metamodel/MetaModel/5.2.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-1039

Please vote on releasing this package as Apache MetaModel 5.2.0.

The vote is open for 72 hours.

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

Thank you in advance for participating.

Regards,
Kasper

Re: [VOTE] Apache MetaModel release 5.2.0

[Kasper Sørensen]

+1 from myself :-)

Den lør. 8. dec. 2018 kl. 10.38 skrev Kasper Sørensen <
i.am.kasper.soren...@gmail.com>:

> Hi All,
>
> I've staged a release of Apache Metamodel version 5.2.0 and would like to
> call for a vote on releasing it.
>
> The Git tag to be voted on is MetaModel-5.2.0:
>
> https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=6cb8a164b8b1a4b4bccbd5234b7d05525a819ca9
>
> The source artifact to be voted on is:
>
> http://repository.apache.org/content/repositories/orgapachemetamodel-1039/org/apache/metamodel/MetaModel/5.2.0/MetaModel-5.2.0-source-release.zip
>
> Parent directory (including MD5, SHA1 hashes etc.) of the source is:
>
> http://repository.apache.org/content/repositories/orgapachemetamodel-1039/org/apache/metamodel/MetaModel/5.2.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-1039
>
> Please vote on releasing this package as Apache MetaModel 5.2.0.
>
> The vote is open for 72 hours.
>
> [ ] +1 Release this package as Apache MetaModel 5.2.0
> [ ] -1 Do not release this package because ...
>
> Thank you in advance for participating.
>
> Regards,
> Kasper
>

Re: I'd like to release. You agree? And what should we name the version?

[Kasper Sørensen]

I agree. So I made https://github.com/apache/metamodel/pull/200

Den tor. 6. dec. 2018 kl. 05.26 skrev Arjan Seijkens <
a.seijk...@quadient.com>:

> I think it's best if we only depend on the spec. Without actually diving
> into the material I don't know how hard it is to get it to work in that
> manner though.
>
> Kind regards,
> Arjan Seijkens
>
> -----Original Message-
> From: Kasper Sørensen 
> Sent: Wednesday, December 5, 2018 6:51 PM
> To: dev@metamodel.apache.org
> Subject: Re: I'd like to release. You agree? And what should we name the
> version?
>
> I'm doing a bit of the same actually, on DataCleaner community edition
> though. And I'm running into a banned dependency issue which I can fix
> locally in DataCleaner, but I wonder what the best to do is ...
>
> The issue is with JAXB-RT and JAXWS-RT. With the changes to SugarCRM we
> now depend directly on the com.sun... dependencies. We used to only depend
> on the spec. What do you think is best?
>
> Den ons. 5. dec. 2018 kl. 08.11 skrev Kasper Sørensen <
> i.am.kasper.soren...@gmail.com>:
>
> > That sounds reasonable :-)
> >
> > Den tir. 4. dec. 2018 kl. 23.06 skrev Arjan Seijkens <
> > a.seijk...@quadient.com>:
> >
> >> I'll be mostly checking if it doesn't cause any serious problems for
> >> building DataCleaner (it works fine for Java 8 after adding a few
> >> exclusions in dependencies to DataCleaner), next to that I'm going to
> >> do a little bit of testing with SugarCRM. If you don't hear any
> >> complaints from me before Friday, please start the release procedure.
> >>
> >> Kind regards,
> >> Arjan Seijkens
> >>
> >> -Original Message-
> >> From: Kasper Sørensen 
> >> Sent: Tuesday, December 4, 2018 8:43 PM
> >> To: dev@metamodel.apache.org
> >> Subject: Re: I'd like to release. You agree? And what should we name
> >> the version?
> >>
> >> Great, thanks for the input guys. Sounds like we're agreeing on
> >> version
> >> *5.2.0* then.
> >>
> >> @Arjan please let us know how much time you're talking about and what
> >> you're doing and finding :-)
> >>
> >> Den tir. 4. dec. 2018 kl. 00.58 skrev Alberto Rodriguez <
> >> ardl...@gmail.com>:
> >>
> >> > I would bump to 5.2.0 taking into account the updated deps to be
> >> > JDK8-11 compatible.
> >> >
> >> > El mar., 4 dic. 2018 a las 8:10, Arjan Seijkens
> >> > ( >> > >)
> >> > escribió:
> >> >
> >> > > I think releasing is a good idea. I'm personally still testing
> >> > > the latest java 9 through 11 related changes and maybe will come
> >> > > up with some
> >> > findings
> >> > > based on those changes. So I would like a little time for that.
> >> > >
> >> > > I personally think 5.2.0 would be the best option for the
> >> > > version,
> >> > because
> >> > > the introduction of java 9 through 11 support is quite a step up
> >> > > from my perspective.
> >> > >
> >> > > Kind regards,
> >> > > Arjan Seijkens
> >> > >
> >> > > -Original Message-
> >> > > From: Kasper Sørensen 
> >> > > Sent: Tuesday, December 4, 2018 5:54 AM
> >> > > To: dev@metamodel.apache.org
> >> > > Subject: I'd like to release. You agree? And what should we name
> >> > > the version?
> >> > >
> >> > > Hi all,
> >> > >
> >> > > I'd like to release MetaModel rather soon. In the current master
> >> > > branch
> >> > we
> >> > > have these two changes ready:
> >> > >
> >> > > * [METAMODEL-1205] - Updated build and dependencies to be JDK8-11
> >> > > compatible. Important updates include Guava, POI, Cassandra, Hadoop.
> >> > > * [METAMODEL-1206] - Solved Maven version dependent unit test
> >> > > issues in ElasticSearch-native module.
> >> > >
> >> > > They're both pretty much internal, except that the dependency
> >> > > updates are going to be pretty significant for anyone upgrading
> >> > > from version 5.1.0
> >> > (or
> >> > > other recent releases) as their transitive dependencies will
> >> > > likely get upgraded as well.
> >> > >
> >> > > So that brings up the quesion about what to name a new release.
> >> > > On one hand it's almost a non-functional upgrade, so we could go
> >> > > with version
> >> > name
> >> > > *5.1.1*. on the other hand it updates the supported and required
> >> > > versions of dependencies a lot. So I think I personally think it
> >> > > should be version *5.2.0*. What do you think?
> >> > >
> >> > > - Kasper
> >> > >
> >> >
> >>
> >
>

Re: Unable to compile Source Code Error:(41, 28) java: package com.sugarcrm.ws.soap does not exist

[Kasper Sørensen]

You need to build it first with Maven. Those classes you are missing there
are coming from the WSDL generated code in the sugarcrm module.

Den ons. 5. dec. 2018 kl. 20.45 skrev Laxmi Lal Menaria <
menarialaxmi...@gmail.com>:

> Hello,
>
> I have tried to compile whole source code to for custom code change but
> when I tried in Intellij but it says "Error:(41, 28) java: package
> com.sugarcrm.ws.soap does not exist" so please let me know how can compile
> the all packages.
> --
>
> Thanks,
> Laxmilal Menaria | +91 982 955 3793 | http://laxmilalmenaria.com/
>

Re: I'd like to release. You agree? And what should we name the version?

[Kasper Sørensen]

I'm doing a bit of the same actually, on DataCleaner community edition
though. And I'm running into a banned dependency issue which I can fix
locally in DataCleaner, but I wonder what the best to do is ...

The issue is with JAXB-RT and JAXWS-RT. With the changes to SugarCRM we now
depend directly on the com.sun... dependencies. We used to only depend on
the spec. What do you think is best?

Den ons. 5. dec. 2018 kl. 08.11 skrev Kasper Sørensen <
i.am.kasper.soren...@gmail.com>:

> That sounds reasonable :-)
>
> Den tir. 4. dec. 2018 kl. 23.06 skrev Arjan Seijkens <
> a.seijk...@quadient.com>:
>
>> I'll be mostly checking if it doesn't cause any serious problems for
>> building DataCleaner (it works fine for Java 8 after adding a few
>> exclusions in dependencies to DataCleaner), next to that I'm going to do a
>> little bit of testing with SugarCRM. If you don't hear any complaints from
>> me before Friday, please start the release procedure.
>>
>> Kind regards,
>> Arjan Seijkens
>>
>> -Original Message-
>> From: Kasper Sørensen 
>> Sent: Tuesday, December 4, 2018 8:43 PM
>> To: dev@metamodel.apache.org
>> Subject: Re: I'd like to release. You agree? And what should we name the
>> version?
>>
>> Great, thanks for the input guys. Sounds like we're agreeing on version
>> *5.2.0* then.
>>
>> @Arjan please let us know how much time you're talking about and what
>> you're doing and finding :-)
>>
>> Den tir. 4. dec. 2018 kl. 00.58 skrev Alberto Rodriguez <
>> ardl...@gmail.com>:
>>
>> > I would bump to 5.2.0 taking into account the updated deps to be
>> > JDK8-11 compatible.
>> >
>> > El mar., 4 dic. 2018 a las 8:10, Arjan Seijkens
>> > (> > >)
>> > escribió:
>> >
>> > > I think releasing is a good idea. I'm personally still testing the
>> > > latest java 9 through 11 related changes and maybe will come up with
>> > > some
>> > findings
>> > > based on those changes. So I would like a little time for that.
>> > >
>> > > I personally think 5.2.0 would be the best option for the version,
>> > because
>> > > the introduction of java 9 through 11 support is quite a step up
>> > > from my perspective.
>> > >
>> > > Kind regards,
>> > > Arjan Seijkens
>> > >
>> > > -Original Message-
>> > > From: Kasper Sørensen 
>> > > Sent: Tuesday, December 4, 2018 5:54 AM
>> > > To: dev@metamodel.apache.org
>> > > Subject: I'd like to release. You agree? And what should we name the
>> > > version?
>> > >
>> > > Hi all,
>> > >
>> > > I'd like to release MetaModel rather soon. In the current master
>> > > branch
>> > we
>> > > have these two changes ready:
>> > >
>> > > * [METAMODEL-1205] - Updated build and dependencies to be JDK8-11
>> > > compatible. Important updates include Guava, POI, Cassandra, Hadoop.
>> > > * [METAMODEL-1206] - Solved Maven version dependent unit test issues
>> > > in ElasticSearch-native module.
>> > >
>> > > They're both pretty much internal, except that the dependency
>> > > updates are going to be pretty significant for anyone upgrading from
>> > > version 5.1.0
>> > (or
>> > > other recent releases) as their transitive dependencies will likely
>> > > get upgraded as well.
>> > >
>> > > So that brings up the quesion about what to name a new release. On
>> > > one hand it's almost a non-functional upgrade, so we could go with
>> > > version
>> > name
>> > > *5.1.1*. on the other hand it updates the supported and required
>> > > versions of dependencies a lot. So I think I personally think it
>> > > should be version *5.2.0*. What do you think?
>> > >
>> > > - Kasper
>> > >
>> >
>>
>

Re: I'd like to release. You agree? And what should we name the version?

[Kasper Sørensen]

That sounds reasonable :-)

Den tir. 4. dec. 2018 kl. 23.06 skrev Arjan Seijkens <
a.seijk...@quadient.com>:

> I'll be mostly checking if it doesn't cause any serious problems for
> building DataCleaner (it works fine for Java 8 after adding a few
> exclusions in dependencies to DataCleaner), next to that I'm going to do a
> little bit of testing with SugarCRM. If you don't hear any complaints from
> me before Friday, please start the release procedure.
>
> Kind regards,
> Arjan Seijkens
>
> -Original Message-
> From: Kasper Sørensen 
> Sent: Tuesday, December 4, 2018 8:43 PM
> To: dev@metamodel.apache.org
> Subject: Re: I'd like to release. You agree? And what should we name the
> version?
>
> Great, thanks for the input guys. Sounds like we're agreeing on version
> *5.2.0* then.
>
> @Arjan please let us know how much time you're talking about and what
> you're doing and finding :-)
>
> Den tir. 4. dec. 2018 kl. 00.58 skrev Alberto Rodriguez  >:
>
> > I would bump to 5.2.0 taking into account the updated deps to be
> > JDK8-11 compatible.
> >
> > El mar., 4 dic. 2018 a las 8:10, Arjan Seijkens
> > ( > >)
> > escribió:
> >
> > > I think releasing is a good idea. I'm personally still testing the
> > > latest java 9 through 11 related changes and maybe will come up with
> > > some
> > findings
> > > based on those changes. So I would like a little time for that.
> > >
> > > I personally think 5.2.0 would be the best option for the version,
> > because
> > > the introduction of java 9 through 11 support is quite a step up
> > > from my perspective.
> > >
> > > Kind regards,
> > > Arjan Seijkens
> > >
> > > -Original Message-
> > > From: Kasper Sørensen 
> > > Sent: Tuesday, December 4, 2018 5:54 AM
> > > To: dev@metamodel.apache.org
> > > Subject: I'd like to release. You agree? And what should we name the
> > > version?
> > >
> > > Hi all,
> > >
> > > I'd like to release MetaModel rather soon. In the current master
> > > branch
> > we
> > > have these two changes ready:
> > >
> > > * [METAMODEL-1205] - Updated build and dependencies to be JDK8-11
> > > compatible. Important updates include Guava, POI, Cassandra, Hadoop.
> > > * [METAMODEL-1206] - Solved Maven version dependent unit test issues
> > > in ElasticSearch-native module.
> > >
> > > They're both pretty much internal, except that the dependency
> > > updates are going to be pretty significant for anyone upgrading from
> > > version 5.1.0
> > (or
> > > other recent releases) as their transitive dependencies will likely
> > > get upgraded as well.
> > >
> > > So that brings up the quesion about what to name a new release. On
> > > one hand it's almost a non-functional upgrade, so we could go with
> > > version
> > name
> > > *5.1.1*. on the other hand it updates the supported and required
> > > versions of dependencies a lot. So I think I personally think it
> > > should be version *5.2.0*. What do you think?
> > >
> > > - Kasper
> > >
> >
>

Re: I'd like to release. You agree? And what should we name the version?

[Kasper Sørensen]

Great, thanks for the input guys. Sounds like we're agreeing on version
*5.2.0* then.

@Arjan please let us know how much time you're talking about and what
you're doing and finding :-)

Den tir. 4. dec. 2018 kl. 00.58 skrev Alberto Rodriguez :

> I would bump to 5.2.0 taking into account the updated deps to be JDK8-11
> compatible.
>
> El mar., 4 dic. 2018 a las 8:10, Arjan Seijkens ( >)
> escribió:
>
> > I think releasing is a good idea. I'm personally still testing the latest
> > java 9 through 11 related changes and maybe will come up with some
> findings
> > based on those changes. So I would like a little time for that.
> >
> > I personally think 5.2.0 would be the best option for the version,
> because
> > the introduction of java 9 through 11 support is quite a step up from my
> > perspective.
> >
> > Kind regards,
> > Arjan Seijkens
> >
> > -Original Message-
> > From: Kasper Sørensen 
> > Sent: Tuesday, December 4, 2018 5:54 AM
> > To: dev@metamodel.apache.org
> > Subject: I'd like to release. You agree? And what should we name the
> > version?
> >
> > Hi all,
> >
> > I'd like to release MetaModel rather soon. In the current master branch
> we
> > have these two changes ready:
> >
> > * [METAMODEL-1205] - Updated build and dependencies to be JDK8-11
> > compatible. Important updates include Guava, POI, Cassandra, Hadoop.
> > * [METAMODEL-1206] - Solved Maven version dependent unit test issues in
> > ElasticSearch-native module.
> >
> > They're both pretty much internal, except that the dependency updates are
> > going to be pretty significant for anyone upgrading from version 5.1.0
> (or
> > other recent releases) as their transitive dependencies will likely get
> > upgraded as well.
> >
> > So that brings up the quesion about what to name a new release. On one
> > hand it's almost a non-functional upgrade, so we could go with version
> name
> > *5.1.1*. on the other hand it updates the supported and required versions
> > of dependencies a lot. So I think I personally think it should be version
> > *5.2.0*. What do you think?
> >
> > - Kasper
> >
>

I'd like to release. You agree? And what should we name the version?

[Kasper Sørensen]

Hi all,

I'd like to release MetaModel rather soon. In the current master branch we
have these two changes ready:

* [METAMODEL-1205] - Updated build and dependencies to be JDK8-11
compatible. Important updates include Guava, POI, Cassandra, Hadoop.
* [METAMODEL-1206] - Solved Maven version dependent unit test issues in
ElasticSearch-native module.

They're both pretty much internal, except that the dependency updates are
going to be pretty significant for anyone upgrading from version 5.1.0 (or
other recent releases) as their transitive dependencies will likely get
upgraded as well.

So that brings up the quesion about what to name a new release. On one hand
it's almost a non-functional upgrade, so we could go with version name
*5.1.1*. on the other hand it updates the supported and required versions
of dependencies a lot. So I think I personally think it should be version
*5.2.0*. What do you think?

- Kasper

Re: Problem building MetaModel master

[Kasper Sørensen]

I've also seen this on one of my machines. I didn't dig into it TBH, but
now that you raise it I guess it's a general problem. We should fix it.

(part of me just wants to get rid of the ES native module)

Den man. 26. nov. 2018 kl. 05.33 skrev Arjan Seijkens <
a.seijk...@quadient.com>:

> Hi,
>
> For some reason I’m no longer able to build Apache MetaModel from the
> master. I’m using java version 1.8.0_152 and maven version 3.6.0.
>
> When I do “mvn install”, it fails in the MetaModel-elasticsearch-native
> module:
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test)
> on project MetaModel-elasticsearch-native: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> C:\Work\git\metamodel\elasticsearch\native\target\surefire-reports for the
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] There was an error in the forked process
> [ERROR] access denied ("java.util.PropertyPermission" "*" "read,write")
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException:
> There was an error in the forked process
> [ERROR] access denied ("java.util.PropertyPermission" "*" "read,write")
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:658)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:278)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:244)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1194)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1022)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:868)
> [ERROR] at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR] at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> [ERROR] at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)
> [ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:192)
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> [ERROR] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:498)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> [ERROR]
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :MetaModel-elasticsearch-native
>
>
> I can work around this by lowering the version number of the
> maven-surefire-plugin. If I add this to the pom:
>
> 

Re: [postgres] Insert and Update execution fails if table column name contains Upper case

[Kasper Sørensen]

I don't have much insight. One thought though: Are you doing these
inserts/updates with the same DataContext that you used for creating the
table? Or was the table pre-existing? I'm asking because I guess it could
be related to the CREATE TABLE which defined the column names too. And if
MetaModel is responsible for creating the columns, but maybe not quoting
their names at that time, then I could see a discrepancy occuring when you
try to insert. So is that a possibility?

Den fre. 2. nov. 2018 kl. 03.05 skrev Dennis Krøger :

> According to
>
> https://www.postgresql.org/docs/current/static/sql-syntax-lexical.html#SQL-SYNTAX-IDENTIFIERS
> ,
> columns are case-insensitive if created without quotes, but case-sensitive
> if created with quotes.
>
> I'm not entirely sure how we're handling that. It's not really a difference
> the table creation classes handles AFAIK, and I suspect we don't really
> expect case-sensitivity in PostgreSQL tables, but it's been quite a while
> for me, so I might remember wrong.
>
> Kasper, do you have some more insight?
>
> BR,
> Dennis
>
> On Fri, Nov 2, 2018 at 10:19 AM Vijay Kumar Jalagari
>  wrote:
>
> > Hi,
> >
> > I am using Apache metamodel with data source PostgreSQL 11 and while
> > executing insert(InsertInto) or update statement query is failing if
> table
> > column name contains upper characters.
> > According to logs statement is generating properly but it seems
> postgresql
> > is converting column names to lowercases.
> >
> > Is it know issue? Is there any workaround for resolving it?
> >
> > Logs
> > org.apache.metamodel.jdbc.JdbcUtils Could not execute insert statement:
> > INSERT INTO "public"."employee"
> > (id,name,age,dob,mobileNo,zip,profilePicture,vendor) VALUES
> > (?,?,?,?,?,?,?,?): ERROR: column "mobileno" of relation "employee" does
> not
> > exist
> >   Position: 50, Error code=0, SQL state=42703
> > org.postgresql.util.PSQLException: ERROR: column "mobileno" of relation
> > "employee" does not exist
> >   Position: 50
> > at
> >
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2440)
> > [org.postgresql.jdbc42:42.2.5]
> > at
> >
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2183)
> > [org.postgresql.jdbc42:42.2.5]
> > at
> >
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:308)
> > [org.postgresql.jdbc42:42.2.5]
> > at
> > org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:441)
> > [org.postgresql.jdbc42:42.2.5]
> > at
> > org.postgresql.jdbc.PgStatement.execute(PgStatement.java:365)
> > [org.postgresql.jdbc42:42.2.5]
> > at
> >
> org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:143)
> > [org.postgresql.jdbc42:42.2.5]
> > at
> >
> org.postgresql.jdbc.PgPreparedStatement.executeUpdate(PgPreparedStatement.java:120)
> > [org.postgresql.jdbc42:42.2.5]
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> > Method)
> > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
> > Source)
> > at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> > Source)
> > at java.lang.reflect.Method.invoke(Unknown Source)
> > at
> >
> org.apache.tomcat.jdbc.pool.interceptor.AbstractQueryReport$StatementProxy.invoke(AbstractQueryReport.java:235)
> > [org.apache.sling.datasource:1.0.2]
> > at com.sun.proxy.$Proxy195.executeUpdate(Unknown Source)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> > Method)
> > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
> > Source)
> > at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> > Source)
> > at java.lang.reflect.Method.invoke(Unknown Source)
> > at
> >
> org.apache.tomcat.jdbc.pool.interceptor.StatementDecoratorInterceptor$StatementProxy.invoke(StatementDecoratorInterceptor.java:261)
> > [org.apache.sling.datasource:1.0.2]
> > at com.sun.proxy.$Proxy195.executeUpdate(Unknown Source)
> > at
> >
> org.apache.metamodel.jdbc.JdbcSimpleUpdateCallback.executePreparedStatement(JdbcSimpleUpdateCallback.java:45)
> > [aem-dermis-core:3.0.33.SNAPSHOT]
> > at
> >
> org.apache.metamodel.jdbc.JdbcUpdateCallback.executePreparedStatement(JdbcUpdateCallback.java:71)
> > [aem-dermis-core:3.0.33.SNAPSHOT]
> > at
> >
> org.apache.metamodel.jdbc.JdbcUpdateCallback.executeInsert(JdbcUpdateCallback.java:272)
> > [aem-dermis-core:3.0.33.SNAPSHOT]
> > at
> >
> org.apache.metamodel.jdbc.JdbcInsertBuilder.execute(JdbcInsertBuilder.java:85)
> > [aem-dermis-core:3.0.33.SNAPSHOT]
> >
> >
> > Regards,
> > Vijay Kumar J
> >
> --
> Med venlig hilsen,
> Dennis Du Krøger
>

Re: Best way to use RowInsertBuilder with Millions of insert query

[Kasper Sørensen]

Right, so a buffer size of 300k seems like it's probably just too big.
You're trying to hold all that in memory which may be too much - depending
on the number of fields/columns in your data set. Now that you've
eliminated the empty catch block, I'd try going back down to a few thousand
records at a time.

Den tir. 23. okt. 2018 kl. 21.38 skrev Laxmi Lal Menaria <
menarialaxmi...@gmail.com>:

> Ok. the current code is throwing OutOfMemoryException after 300K rows.
> Stack trace :
>
> java.lang.OutOfMemoryError: GC overhead limit exceeded
>at java.util.Arrays.copyOf(Arrays.java:3332)
>at
> java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:124)
>at
> java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:649)
>at java.lang.StringBuilder.append(StringBuilder.java:202)
>at
> org.apache.metamodel.jdbc.JdbcInsertBuilder.createSqlStatement(JdbcInsertBuilder.java:117)
>at
> org.apache.metamodel.jdbc.JdbcInsertBuilder.createSqlStatement(JdbcInsertBuilder.java:96)
>at
> org.apache.metamodel.jdbc.JdbcInsertBuilder.execute(JdbcInsertBuilder.java:63)
>
>
> I have already used try-catch in for that block where required. Please have
> a look it once and let me know if there any option that we can close the
> connection with Preparedstatement after 100k rows with greater buffer size.
> This will improve the memory issue and will be much better for large data
> blocks.
>
> Thanks,
> Laxmi Lal Menaria
>
>
> On Thu, Oct 18, 2018 at 11:29 PM Kasper Sørensen <
> i.am.kasper.soren...@gmail.com> wrote:
>
> > That code example doesn't look wrong to me, except I would never just
> catch
> > RuntimeException and then do nothing about it. Actually I wouldn't want
> to
> > try-catch anything here... Let it crash if something is truly wrong. You
> > may be hiding an important error message?
> >
> > You could try using different buffer sizes... In another open source
> > project that I work on that uses this (DataCleaner) we allow selecting
> > between something like 1k, 10k, 20k and 100k size buffers. I can't recall
> > if that buffer number is an actual record number - I think it may be a
> > "value count" so columns X rows.
> >
> > Den ons. 17. okt. 2018 kl. 21.21 skrev Laxmi Lal Menaria <
> > menarialaxmi...@gmail.com>:
> >
> > > Hello Everyone,
> > >
> > > I have created a sample which insert data from csv to SQL table, I used
> > > RowInsertBuilder with BatchUpdateScript, it is working fine but takes
> too
> > > much time to complete the operation because we have millions of rows in
> > > csv.
> > >
> > > I would need a better way to speedup the process, please let me know
> how
> > > can I improve it, i.e. close the PreparedStatement after 10k rows or
> > > something else, so few thousands rows  executed and it will free up the
> > > list.
> > >
> > > Current code block is:
> > >
> > > final UpdateableDataContext dc = con.getUpdateableDataContext();
> > > dc.executeUpdate((BatchUpdateScript) callback -> {
> > > for (final Object[] rowData : buffer) {
> > > RowInsertionBuilder insertBuilder =
> > > callback.insertInto(columns[0].getTable());
> > > for (int i = 0; i < columns.length; i++) {
> > > insertBuilder = insertBuilder.value(columns[i],
> > > rowData[i]);
> > > }
> > > try {
> > > insertBuilder.execute();
> > >
> > > } catch (final RuntimeException e) {
> > >
> > > }
> > > }
> > > });
> > >
> > > --
> > >
> > > Thanks,
> > > Laxmilal Menaria | +91 982 955 3793 | http://laxmilalmenaria.com/
> > >
> >
>
>
> --
>
> Thanks,
> Laxmilal Menaria | +91 982 955 3793 | http://laxmilalmenaria.com/
>

Re: Best way to use RowInsertBuilder with Millions of insert query

[Kasper Sørensen]

That code example doesn't look wrong to me, except I would never just catch
RuntimeException and then do nothing about it. Actually I wouldn't want to
try-catch anything here... Let it crash if something is truly wrong. You
may be hiding an important error message?

You could try using different buffer sizes... In another open source
project that I work on that uses this (DataCleaner) we allow selecting
between something like 1k, 10k, 20k and 100k size buffers. I can't recall
if that buffer number is an actual record number - I think it may be a
"value count" so columns X rows.

Den ons. 17. okt. 2018 kl. 21.21 skrev Laxmi Lal Menaria <
menarialaxmi...@gmail.com>:

> Hello Everyone,
>
> I have created a sample which insert data from csv to SQL table, I used
> RowInsertBuilder with BatchUpdateScript, it is working fine but takes too
> much time to complete the operation because we have millions of rows in
> csv.
>
> I would need a better way to speedup the process, please let me know how
> can I improve it, i.e. close the PreparedStatement after 10k rows or
> something else, so few thousands rows  executed and it will free up the
> list.
>
> Current code block is:
>
> final UpdateableDataContext dc = con.getUpdateableDataContext();
> dc.executeUpdate((BatchUpdateScript) callback -> {
> for (final Object[] rowData : buffer) {
> RowInsertionBuilder insertBuilder =
> callback.insertInto(columns[0].getTable());
> for (int i = 0; i < columns.length; i++) {
> insertBuilder = insertBuilder.value(columns[i],
> rowData[i]);
> }
> try {
> insertBuilder.execute();
>
> } catch (final RuntimeException e) {
>
> }
> }
> });
>
> --
>
> Thanks,
> Laxmilal Menaria | +91 982 955 3793 | http://laxmilalmenaria.com/
>

[RESULT] [VOTE] Apache Metamodel release 5.1.1

[Kasper Sørensen]

Hi all,

Thank you so much for voting. We have 5 votes for and 0 against the release:

Arjan Seijkens
Alberto Rodriguez *
Laxmi Lal Menaria
Kasper Sørensen *
Dennis Krøger *

* = Indicates PMC.

I will continue with the release procedure.

Best regards,
Kasper

Den ons. 3. okt. 2018 kl. 05.11 skrev Dennis Krøger :

> +1
>
> On Wed, Oct 3, 2018 at 4:42 AM Kasper Sørensen <
> i.am.kasper.soren...@gmail.com> wrote:
>
> > +1 from myself too :-)
> >
> > Den man. 1. okt. 2018 kl. 01.48 skrev Laxmi Lal Menaria <
> > menarialaxmi...@gmail.com>:
> >
> > > +1
> > >
> > > On Mon, Oct 1, 2018 at 12:17 PM Alberto Rodriguez 
> > > wrote:
> > >
> > > > +1
> > > >
> > > > El lun., 1 oct. 2018 a las 8:14, Arjan Seijkens (<
> > > a.seijk...@quadient.com
> > > > >)
> > > > escribió:
> > > >
> > > > > +1
> > > > >
> > > > > Kind regards,
> > > > > Arjan Seijkens
> > > > >
> > > > > -Original Message-
> > > > > From: Kasper Sørensen 
> > > > > Sent: Monday, October 1, 2018 5:35 AM
> > > > > To: dev@metamodel.apache.org
> > > > > Subject: [VOTE] Apache Metamodel release 5.1.1
> > > > >
> > > > > Hi All,
> > > > >
> > > > > I hope you will join this vote to release the following candidate
> as
> > > > > Apache Metamodel version 5.1.1.
> > > > >
> > > > > The Git tag to be voted on is MetaModel-5.1.1:
> > > > >
> > > > >
> > > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=d3db702516679ea7ee51fe4f08a9305d1ae90d7a
> > > > >
> > > > > The source artifact to be voted on is:
> > > > >
> > > > >
> > > >
> > >
> >
> http://repository.apache.org/content/repositories/orgapachemetamodel-1038/org/apache/metamodel/MetaModel/5.1.1/MetaModel-5.1.1-source-release.zip
> > > > >
> > > > > Parent directory (including MD5, SHA1 hashes etc.) of the source
> is:
> > > > >
> > > > >
> > > >
> > >
> >
> http://repository.apache.org/content/repositories/orgapachemetamodel-1038/org/apache/metamodel/MetaModel/5.1.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:
> > > > >
> > > >
> > >
> >
> http://repository.apache.org/content/repositories/orgapachemetamodel-1038
> > > > >
> > > > > Please vote on releasing this package as Apache MetaModel 5.1.1.
> > > > >
> > > > > The vote is open for 72 hours.
> > > > >
> > > > > [ ] +1 Release this package as Apache MetaModel 5.1.1 [ ] -1 Do not
> > > > > release this package because ...
> > > > >
> > > > > Thank you in advance for participating.
> > > > >
> > > > > Regards,
> > > > > Kasper
> > > > >
> > > >
> > >
> > >
> > > --
> > >
> > > Thanks,
> > > Laxmilal Menaria | +91 982 955 3793 <+91%2098295%2053793> |
> > http://laxmilalmenaria.com/
> > >
> >
> --
> Med venlig hilsen,
> Dennis Du Krøger
>

Re: [VOTE] Apache Metamodel release 5.1.1

[Kasper Sørensen]

+1 from myself too :-)

Den man. 1. okt. 2018 kl. 01.48 skrev Laxmi Lal Menaria <
menarialaxmi...@gmail.com>:

> +1
>
> On Mon, Oct 1, 2018 at 12:17 PM Alberto Rodriguez 
> wrote:
>
> > +1
> >
> > El lun., 1 oct. 2018 a las 8:14, Arjan Seijkens (<
> a.seijk...@quadient.com
> > >)
> > escribió:
> >
> > > +1
> > >
> > > Kind regards,
> > > Arjan Seijkens
> > >
> > > -Original Message-
> > > From: Kasper Sørensen 
> > > Sent: Monday, October 1, 2018 5:35 AM
> > > To: dev@metamodel.apache.org
> > > Subject: [VOTE] Apache Metamodel release 5.1.1
> > >
> > > Hi All,
> > >
> > > I hope you will join this vote to release the following candidate as
> > > Apache Metamodel version 5.1.1.
> > >
> > > The Git tag to be voted on is MetaModel-5.1.1:
> > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=d3db702516679ea7ee51fe4f08a9305d1ae90d7a
> > >
> > > The source artifact to be voted on is:
> > >
> > >
> >
> http://repository.apache.org/content/repositories/orgapachemetamodel-1038/org/apache/metamodel/MetaModel/5.1.1/MetaModel-5.1.1-source-release.zip
> > >
> > > Parent directory (including MD5, SHA1 hashes etc.) of the source is:
> > >
> > >
> >
> http://repository.apache.org/content/repositories/orgapachemetamodel-1038/org/apache/metamodel/MetaModel/5.1.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:
> > >
> >
> http://repository.apache.org/content/repositories/orgapachemetamodel-1038
> > >
> > > Please vote on releasing this package as Apache MetaModel 5.1.1.
> > >
> > > The vote is open for 72 hours.
> > >
> > > [ ] +1 Release this package as Apache MetaModel 5.1.1 [ ] -1 Do not
> > > release this package because ...
> > >
> > > Thank you in advance for participating.
> > >
> > > Regards,
> > > Kasper
> > >
> >
>
>
> --
>
> Thanks,
> Laxmilal Menaria | +91 982 955 3793 | http://laxmilalmenaria.com/
>

[VOTE] Apache Metamodel release 5.1.1

[Kasper Sørensen]

Hi All,

I hope you will join this vote to release the following candidate as Apache
Metamodel version 5.1.1.

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

The source artifact to be voted on is:
http://repository.apache.org/content/repositories/orgapachemetamodel-1038/org/apache/metamodel/MetaModel/5.1.1/MetaModel-5.1.1-source-release.zip

Parent directory (including MD5, SHA1 hashes etc.) of the source is:
http://repository.apache.org/content/repositories/orgapachemetamodel-1038/org/apache/metamodel/MetaModel/5.1.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:
http://repository.apache.org/content/repositories/orgapachemetamodel-1038

Please vote on releasing this package as Apache MetaModel 5.1.1.

The vote is open for 72 hours.

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

Thank you in advance for participating.

Regards,
Kasper

Re: Issue with NULL and Blank values

[Kasper Sørensen]

That's not how open source works, at least in my opinion :-) You build
concensus about some approach of solving an issue (which it seems we have
the rough idea for) and then the people who has the itch to fix it, can do
so. I will happily review patches coming in to fix stuff like this though.

Den tir. 25. sep. 2018 kl. 19.19 skrev Laxmi Lal Menaria <
menarialaxmi...@gmail.com>:

> Thank you, please let me know once you add that
>
> Get Outlook for iOS<https://aka.ms/o0ukef>
>
> ____
> From: Kasper Sørensen 
> Sent: Wednesday, September 26, 2018 1:56 AM
> To: dev@metamodel.apache.org
> Subject: Re: Issue with NULL and Blank values
>
> I could see us adding something in MetaModel, as long as it is optional,
> and turned off by default. Existing CSV users should not experience this,
> but we could add something in the CsvConfiguration class for example, which
> would something like a "literal null value indicator".
>
> Den man. 24. sep. 2018 kl. 21.10 skrev Ashwin Rayaprolu <
> ashwin.rayapr...@gmail.com>:
>
> > That depends on whether NULL is defined as literal in your own data
> > dictionary or as key word. If you define it as keyword then there should
> > be an option to escape it.
> >
> > This is standard practice across all protocol's to define keywords and
> > escape them. Ideally it will be better if its a single character.
> >
> > But as kasper said there is not a standard definition for null in
> official
> > csv protocol. It will be better for you to do post process after loading
> > and not complicating original csv loader.
> >
> >
> >
> > On Mon, Sep 24, 2018 at 9:03 PM, Laxmi Lal Menaria <
> > menarialaxmi...@gmail.com> wrote:
> >
> > > I think we should handle both, if NULL then write NULL to csv and if
> > blank
> > > then write "" to csv, this will solve null vs blank.
> > >
> > > Please let me know is it possible?
> > >
> > > Thanks,
> > > Laxmi Lal
> > >
> > > On Tue, Sep 25, 2018 at 8:17 AM, Kasper Sørensen <
> > > i.am.kasper.soren...@gmail.com> wrote:
> > >
> > > > CSV files do not have a way to represent null values, so they
> > > automatically
> > > > become blank. They're just text files and there is no way that a text
> > > file
> > > > can distinguish between a blank and a null. I guess we could
> introduce
> > a
> > > > system property or something like that, which could turn all blanks
> > into
> > > > null. But I imagine that then you would ask the inverse question
> about
> > > how
> > > > to represent blank strings as non-null? :-)
> > > >
> > > > Den tor. 20. sep. 2018 kl. 21.48 skrev Laxmi Lal Menaria <
> > > > menarialaxmi...@gmail.com>:
> > > >
> > > > > Hi All,
> > > > >
> > > > > I am trying to write MSSQL data to csv files and use Apache
> MetaModel
> > > for
> > > > > the same, It is working fine for most of the case but failed when I
> > > > restore
> > > > > the csv to Test database.
> > > > >
> > > > > When I compare the both database I got that BLANK values are
> migrated
> > > to
> > > > > NULL values. This should not happens due to data integrity.
> > > > >
> > > > > I look the metamodel code and found that it is converting the NULL
> > > values
> > > > > to BLANK
> > > > >
> > > > > (CsvInsertBuilder)
> > > > >
> > > > > for(int i = 0; i < stringValues.length; ++i) {
> > > > > stringValues[i] = values[i] == null ? "" : values[i].toString();
> > > > > }
> > > > >
> > > > > So please let me know how can I separate both values NULL and
> BLANK.
> > > > >
> > > > > --
> > > > >
> > > > > Thanks,
> > > > > Laxmilal Menaria | +91 982 955 3793 | http://laxmilalmenaria.com/
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > >
> > > Thanks,
> > > Laxmilal Menaria | +91 982 955 3793 | http://laxmilalmenaria.com/
> > >
> >
>

Re: Issue with NULL and Blank values

[Kasper Sørensen]

I could see us adding something in MetaModel, as long as it is optional,
and turned off by default. Existing CSV users should not experience this,
but we could add something in the CsvConfiguration class for example, which
would something like a "literal null value indicator".

Den man. 24. sep. 2018 kl. 21.10 skrev Ashwin Rayaprolu <
ashwin.rayapr...@gmail.com>:

> That depends on whether NULL is defined as literal in your own data
> dictionary or as key word.  If you define it as keyword then there should
> be an option to escape it.
>
> This is standard practice across all protocol's to define keywords and
> escape them.  Ideally it will be better if its a single character.
>
> But as kasper said there is not a standard definition for null in official
> csv protocol. It will be better for you to do post process after loading
> and not complicating original csv loader.
>
>
>
> On Mon, Sep 24, 2018 at 9:03 PM, Laxmi Lal Menaria <
> menarialaxmi...@gmail.com> wrote:
>
> > I think we should handle both, if NULL then write NULL to csv and if
> blank
> > then write "" to csv, this will solve null vs blank.
> >
> > Please let me know is it possible?
> >
> > Thanks,
> > Laxmi Lal
> >
> > On Tue, Sep 25, 2018 at 8:17 AM, Kasper Sørensen <
> > i.am.kasper.soren...@gmail.com> wrote:
> >
> > > CSV files do not have a way to represent null values, so they
> > automatically
> > > become blank. They're just text files and there is no way that a text
> > file
> > > can distinguish between a blank and a null. I guess we could introduce
> a
> > > system property or something like that, which could turn all blanks
> into
> > > null. But I imagine that then you would ask the inverse question about
> > how
> > > to represent blank strings as non-null? :-)
> > >
> > > Den tor. 20. sep. 2018 kl. 21.48 skrev Laxmi Lal Menaria <
> > > menarialaxmi...@gmail.com>:
> > >
> > > > Hi All,
> > > >
> > > > I am trying to write MSSQL data to csv files and use Apache MetaModel
> > for
> > > > the same, It is working fine for most of the case but failed when I
> > > restore
> > > > the csv to Test database.
> > > >
> > > > When I compare the both database I got that BLANK values are migrated
> > to
> > > > NULL values. This should not happens due to data integrity.
> > > >
> > > > I look the metamodel code and found that it is converting the NULL
> > values
> > > > to BLANK
> > > >
> > > > (CsvInsertBuilder)
> > > >
> > > > for(int i = 0; i < stringValues.length; ++i) {
> > > > stringValues[i] = values[i] == null ? "" : values[i].toString();
> > > > }
> > > >
> > > > So please let me know how can I separate both values NULL and BLANK.
> > > >
> > > > --
> > > >
> > > > Thanks,
> > > > Laxmilal Menaria | +91 982 955 3793 | http://laxmilalmenaria.com/
> > > >
> > >
> >
> >
> >
> > --
> >
> > Thanks,
> > Laxmilal Menaria | +91 982 955 3793 | http://laxmilalmenaria.com/
> >
>

Re: Issue with NULL and Blank values

[Kasper Sørensen]

CSV files do not have a way to represent null values, so they automatically
become blank. They're just text files and there is no way that a text file
can distinguish between a blank and a null. I guess we could introduce a
system property or something like that, which could turn all blanks into
null. But I imagine that then you would ask the inverse question about how
to represent blank strings as non-null? :-)

Den tor. 20. sep. 2018 kl. 21.48 skrev Laxmi Lal Menaria <
menarialaxmi...@gmail.com>:

> Hi All,
>
> I am trying to write MSSQL data to csv files and use Apache MetaModel for
> the same, It is working fine for most of the case but failed when I restore
> the csv to Test database.
>
> When I compare the both database I got that BLANK values are migrated to
> NULL values. This should not happens due to data integrity.
>
> I look the metamodel code and found that it is converting the NULL values
> to BLANK
>
> (CsvInsertBuilder)
>
> for(int i = 0; i < stringValues.length; ++i) {
> stringValues[i] = values[i] == null ? "" : values[i].toString();
> }
>
> So please let me know how can I separate both values NULL and BLANK.
>
> --
>
> Thanks,
> Laxmilal Menaria | +91 982 955 3793 | http://laxmilalmenaria.com/
>

Re: [RESULT] [VOTE] Apache MetaModel release 5.1.0

[Kasper Sørensen]

I've updated the website [1] with the release info and added a new page
about Kafka connectivity in the wiki [2]. Anyone wants to add more
documentation or help spread the word - Go! :-)

[1] http://metamodel.apache.org
[2] https://cwiki.apache.org/confluence/display/METAMODEL

Den tir. 26. jun. 2018 kl. 10.22 skrev Kasper Sørensen <
i.am.kasper.soren...@gmail.com>:

> Hi all,
>
> It's my pleasure to announce that the vote has passed :-)
>
> 5 votes for, of which 3 are PMC
> 0 votes against
>
> I will continue with the release in the Maven repos. Hope to do the
> website and such tonight.
>
> Best regards,
> Kasper
>
> Den man. 25. jun. 2018 kl. 01.57 skrev Dennis Krøger :
>
>> +1
>>
>> On Mon, Jun 25, 2018 at 8:04 AM Arjan Seijkens 
>> wrote:
>>
>> > +1
>> >
>> > -Original Message-
>> > From: Alberto Rodriguez 
>> > Sent: Monday, June 25, 2018 8:04 AM
>> > To: dev@metamodel.apache.org
>> > Subject: Re: [VOTE] Apache MetaModel release 5.1.0
>> >
>> > +1
>> >
>> > 2018-06-23 7:31 GMT+02:00 Lutzen Luinenburg > >:
>> >
>> > > +1
>> > > 
>> > > Van: Kasper Sørensen 
>> > > Verzonden: zaterdag 23 juni 2018 06:54:04
>> > > Aan: dev@metamodel.apache.org
>> > > Onderwerp: Re: [VOTE] Apache MetaModel release 5.1.0
>> > >
>> > > +1
>> > >
>> > > Den fre. 22. jun. 2018 kl. 21.53 skrev Kasper Sørensen <
>> > > i.am.kasper.soren...@gmail.com>:
>> > >
>> > > > Hi All,
>> > > > Please vote on releasing the following candidate as Apache Metamodel
>> > > > version 5.1.0.
>> > > >
>> > > > The Git tag to be voted on is MetaModel-5.1.0:
>> > > >
>> > > > https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=
>> > > ac37546b49d551763f63d9cd65bd664281ef0827
>> > > >
>> > > > The source artifact to be voted on is:
>> > > >
>> > > > http://repository.apache.org/content/repositories/
>> > > orgapachemetamodel-1037/org/apache/metamodel/MetaModel/5.
>> > > 1.0/MetaModel-5.1.0-source-release.zip
>> > > >
>> > > > Parent directory (including MD5, SHA1 hashes etc.) of the source is:
>> > > >
>> > > > http://repository.apache.org/content/repositories/
>> > > orgapachemetamodel-1037/org/apache/metamodel/MetaModel/5.1.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-1037
>> > > >
>> > > > Please vote on releasing this package as Apache MetaModel 5.1.0.
>> > > >
>> > > > The vote is open for 72 hours.
>> > > >
>> > > > [ ] +1 Release this package as Apache MetaModel 5.1.0 [ ] -1 Do not
>> > > > release this package because ...
>> > > >
>> > > > Thank you in advance for participating.
>> > > >
>> > > > Regards,
>> > > > Kasper
>> > > >
>> > >
>> >
>> --
>> Med venlig hilsen,
>> Dennis Du Krøger
>>
>

[RESULT] [VOTE] Apache MetaModel release 5.1.0

[Kasper Sørensen]

Hi all,

It's my pleasure to announce that the vote has passed :-)

5 votes for, of which 3 are PMC
0 votes against

I will continue with the release in the Maven repos. Hope to do the website
and such tonight.

Best regards,
Kasper

Den man. 25. jun. 2018 kl. 01.57 skrev Dennis Krøger :

> +1
>
> On Mon, Jun 25, 2018 at 8:04 AM Arjan Seijkens 
> wrote:
>
> > +1
> >
> > -Original Message-
> > From: Alberto Rodriguez 
> > Sent: Monday, June 25, 2018 8:04 AM
> > To: dev@metamodel.apache.org
> > Subject: Re: [VOTE] Apache MetaModel release 5.1.0
> >
> > +1
> >
> > 2018-06-23 7:31 GMT+02:00 Lutzen Luinenburg :
> >
> > > +1
> > > 
> > > Van: Kasper Sørensen 
> > > Verzonden: zaterdag 23 juni 2018 06:54:04
> > > Aan: dev@metamodel.apache.org
> > > Onderwerp: Re: [VOTE] Apache MetaModel release 5.1.0
> > >
> > > +1
> > >
> > > Den fre. 22. jun. 2018 kl. 21.53 skrev Kasper Sørensen <
> > > i.am.kasper.soren...@gmail.com>:
> > >
> > > > Hi All,
> > > > Please vote on releasing the following candidate as Apache Metamodel
> > > > version 5.1.0.
> > > >
> > > > The Git tag to be voted on is MetaModel-5.1.0:
> > > >
> > > > https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=
> > > ac37546b49d551763f63d9cd65bd664281ef0827
> > > >
> > > > The source artifact to be voted on is:
> > > >
> > > > http://repository.apache.org/content/repositories/
> > > orgapachemetamodel-1037/org/apache/metamodel/MetaModel/5.
> > > 1.0/MetaModel-5.1.0-source-release.zip
> > > >
> > > > Parent directory (including MD5, SHA1 hashes etc.) of the source is:
> > > >
> > > > http://repository.apache.org/content/repositories/
> > > orgapachemetamodel-1037/org/apache/metamodel/MetaModel/5.1.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-1037
> > > >
> > > > Please vote on releasing this package as Apache MetaModel 5.1.0.
> > > >
> > > > The vote is open for 72 hours.
> > > >
> > > > [ ] +1 Release this package as Apache MetaModel 5.1.0 [ ] -1 Do not
> > > > release this package because ...
> > > >
> > > > Thank you in advance for participating.
> > > >
> > > > Regards,
> > > > Kasper
> > > >
> > >
> >
> --
> Med venlig hilsen,
> Dennis Du Krøger
>

[VOTE] Apache MetaModel release 5.1.0

[Kasper Sørensen]

Hi All,
Please vote on releasing the following candidate as Apache Metamodel
version 5.1.0.

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

The source artifact to be voted on is:
http://repository.apache.org/content/repositories/orgapachemetamodel-1037/org/apache/metamodel/MetaModel/5.1.0/MetaModel-5.1.0-source-release.zip

Parent directory (including MD5, SHA1 hashes etc.) of the source is:
http://repository.apache.org/content/repositories/orgapachemetamodel-1037/org/apache/metamodel/MetaModel/5.1.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-1037

Please vote on releasing this package as Apache MetaModel 5.1.0.

The vote is open for 72 hours.

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

Thank you in advance for participating.

Regards,
Kasper

Re: [VOTE] Apache MetaModel release 5.1.0

[Kasper Sørensen]

+1

Den fre. 22. jun. 2018 kl. 21.53 skrev Kasper Sørensen <
i.am.kasper.soren...@gmail.com>:

> Hi All,
> Please vote on releasing the following candidate as Apache Metamodel
> version 5.1.0.
>
> The Git tag to be voted on is MetaModel-5.1.0:
>
> https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=ac37546b49d551763f63d9cd65bd664281ef0827
>
> The source artifact to be voted on is:
>
> http://repository.apache.org/content/repositories/orgapachemetamodel-1037/org/apache/metamodel/MetaModel/5.1.0/MetaModel-5.1.0-source-release.zip
>
> Parent directory (including MD5, SHA1 hashes etc.) of the source is:
>
> http://repository.apache.org/content/repositories/orgapachemetamodel-1037/org/apache/metamodel/MetaModel/5.1.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-1037
>
> Please vote on releasing this package as Apache MetaModel 5.1.0.
>
> The vote is open for 72 hours.
>
> [ ] +1 Release this package as Apache MetaModel 5.1.0
> [ ] -1 Do not release this package because ...
>
> Thank you in advance for participating.
>
> Regards,
> Kasper
>

Re: Trying to stage a release for vote, but facing issues

[Kasper Sørensen]

Turns out the issues I was facing wasn't popping up on my other computer.
Strange, I cannot locate what's wrong. But the vote release is coming SOON
now :-)

Den tor. 21. jun. 2018 kl. 22.17 skrev Kasper Sørensen <
i.am.kasper.soren...@gmail.com>:

> Hi all,
>
> Just a FYI in case you're looking at the commits from the last 24 hours
> and wondering "What the heck is Kasper up to?". I'm trying to get a release
> ready for voting, but our Nexus repository is acting up in various ways.
> First I had a MD5 issue, then a ASC issue and now the connections are
> timing out. Not sure what is going on. Don't think anything is different on
> my end compared to the last many releases I've been working on... Will keep
> trying. So don't worry if you see more release-like commits in git.
>
> Best regards,
> Kasper
>

Trying to stage a release for vote, but facing issues

[Kasper Sørensen]

Hi all,

Just a FYI in case you're looking at the commits from the last 24 hours and
wondering "What the heck is Kasper up to?". I'm trying to get a release
ready for voting, but our Nexus repository is acting up in various ways.
First I had a MD5 issue, then a ASC issue and now the connections are
timing out. Not sure what is going on. Don't think anything is different on
my end compared to the last many releases I've been working on... Will keep
trying. So don't worry if you see more release-like commits in git.

Best regards,
Kasper

Re: Neo4j module updated - should we release?

[Kasper Sørensen]

Great, I actually also was considering doing something about the feedback
on the Kafka module (https://github.com/apache/metamodel/pull/178) which I
think would make sense to also include in a point release like this.

2018-06-03 23:12 GMT-07:00 Arjan Seijkens :

> Hi,
>
> We are still working on improving the HBase module, I will push to create
> a pull request for that this week (as early as possible), so it would fit
> us best to wait for that.
>
> King regards,
> Arjan
>
>
> -----Original Message-
> From: Kasper Sørensen 
> Sent: Monday, June 4, 2018 1:08 AM
> To: dev@metamodel.apache.org
> Subject: Neo4j module updated - should we release?
>
> Hi guys,
>
> I just merged the code style update for the neo4j module. Thanks a lot for
> the contributions on improving the neo4j module. Do you think we should
> release this, or do you have more changes lined up that you want in first?
>
> If we release, I think this warrants a version-update in the "minor"
> version number, making it a 5.1.0 release.
>
> Best regards,
> Kasper
>

Neo4j module updated - should we release?

[Kasper Sørensen]

Hi guys,

I just merged the code style update for the neo4j module. Thanks a lot for
the contributions on improving the neo4j module. Do you think we should
release this, or do you have more changes lined up that you want in first?

If we release, I think this warrants a version-update in the "minor"
version number, making it a 5.1.0 release.

Best regards,
Kasper

Re: Extending HBase support

[Kasper Sørensen]

I like the idea of reusing the WideColumn class also for Cassandra. Is
"Wide Column" a term that you've encountered elsewhere, or did you make
that up? I kinda like it, but would want to consider naming as important.

One piece of perspective too is that some databases (notably MongoDB,
CouchDB, ElasticSearch) support "wide rows" in a way, meaning that any
particular row may contain additional fields outside of the norm. Maybe we
could introduce both WideRow and WideColumn interfaces to support that sort
of behaviour?

Kasper

2018-05-22 7:25 GMT-07:00 Arjan Seijkens :

> Hi,
>
>
>
> In the context of an internship we have been working on extending HBase
> support for MetaModel, mainly focusing on adding write support.
>
>
>
> Right now there is a pull request for this on a MetaModel fork, which can
> be found here: https://github.com/GerardDellemann/metamodel/pull/2. Note
> that we will probably have to replace this pull request with a new one to
> be able to merge it into MetaModel master instead of the fork.
>
>
>
> There is one specific change within this pull request which I would like
> to discuss here.
>
>
>
> Within this pull request we introduce the HBaseColumn class, which extends
> the AbstractColumn class and which represents a column in an HBase table.
> We introduced this class because HBase uses a Wide column store for it's
> database model, which works in a different manner as relational database
> columns.
>
>
>
> In its current state the HBaseColumn class has two important new methods:
>
>- HBaseColumn#getColumnFamily()
>- HBaseColumn#getQualifier()
>
>
>
> From this perspective each Column always has a Column family and
> optionally has a qualifier. If a Column has both a Column family and a
> qualifier, we are able to get a specific value from a table row based on
> that column. If a Column only has a Column family, we don't know which
> qualifiers it has, which can be a typical use case because qualifiers are
> dynamic and can be different for each row, then when getting the value from
> a table row base on that column, we get a list of all values.
>
>
>
> This is how it's implemented now in the pull request.
>
>
>
> I would like your opinion on this, so fire away. Some considerations:
>
>- Maybe we shouldn't call the class HBaseColumn, but rename it to
>WideColumn instead and do some more renaming of the methods, so it can be
>reused later on for Cassandra.
>- In the current implementation the HBaseColumn supports both using it
>with and without a qualifier, which causes different behaviors, is this
>desirable, or should we create two different classes?
>
>
>
> Furthermore all other feedback on the pull request is welcome, but you can
> also wait with that until we replace it with a pull request to actually
> merge it into MetaModel (instead of into the fork).
>
>
>
> Kind regards,
>
>
>
> Arjan Seijkens
>
> *Technical Lead Quadient DataCleaner*
>
> Research & Development
>
>
>
> [image: Quadient]
>
> *Quadient®*
>
> a:
>
> Utrechtseweg 310, Building H31
> 
> 6812 AR Arnhem
> 
>
> The Netherlands
> 
>
> w:
>
> www.quadient.com e: a.seijk...@quadient.com
>
>
>
>   [image:
> https://go.pardot.com/l/68752/2015-06-17/dymgk/68752/22130/Twitter_icon_2.png]
> [image:
> https://go.pardot.com/l/68752/2015-06-17/dymg7/68752/22126/LinkedIn_icon_2.png]
> [image:
> https://go.pardot.com/l/68752/2015-06-17/dylq7/68752/22120/Facebook_icon_2.png]
> [image:
> https://go.pardot.com/l/68752/2015-06-17/dymgy/68752/22132/YouTube_icon_2.png]
> 
>
>
>
> The information contained in this e-mail is intended only for the
> individual to whom it is addressed. It may contain privileged and
> confidential information. If you have received this message in error or
> there are any problems, please notify the sender immediately and delete the
> message from your computer. The unauthorized use, disclosure, copying or
> alteration of this message is forbidden. Quadient and/or its worldwide
> subsidiaries will not be liable for direct, special, indirect or
> consequential damage as a result of any virus being passed on, or arising
> from alteration of the contents of this message by a third party.
>
>
>
> Quadient, Max Höggerstrasse 6, CH-8048 Zurich
> 
>
>
>

New committer: Jörg Unbehauen

[Kasper Sørensen]

Hi everyone,

I'm happy to announce that we have added another committer to the Apache
MetaModel project: Jörg Unbehauen!

Jörg, thanks for your contributions already, and thank you for joining the
committers group.

Best regards,
Kasper

Re: Issue with NULL parameter values for compiled queries

[Kasper Sørensen]

Very good finding. I would say that this is probably a bug. We should
report it in JIRA [1] - would you mind doing that?

As for a workaround - I can only think of the obvious one: "don't use
compiled query when your argument is NULL".

Thanks, Kasper

[1] https://issues.apache.org/jira/browse/METAMODEL

2018-04-19 10:23 GMT-07:00 Tim Kingsbury :

> Hello,
>
> I've run into an interesting problem with using compiled queries to search
> for values that are not equal to null.
>
> Our goal is to run a query like this:   SELECT * FROM MyTable WHERE
> MyValue IS NOT NULL.
>
> If I build the query like this, everything works perfectly:
>
> Query query = context.query().from(schema, "MyTable").select("*").
> toQuery();
> SelectItem manufacturer = new SelectItem(schema.getTableByName("MyTable
> ").getColumnByName("MyValue"));
> query.where(new FilterItem(manufacturer, OperatorType.DIFFERENT_FROM,
> null));
> DataSet dataSet = context.executeQuery(query);
>
> However, if I do the same thing with a compiled query, I get into trouble:
>
>
> Query query2 = context.query().from(schema, "MyTable").select("*").
> toQuery();
> query2.where(new FilterItem(manufacturer, OperatorType.DIFFERENT_FROM, new
> QueryParameter()));
> CompiledQuery compiled = context.compileQuery(query2);
> Object[] params = new Object[1];
> params[0] = null;
> DataSet dataSet2 = context.executeQuery(compiled, params);
>
>
>
>
>
> In this case, the generated SQL is:
>
>
>
> SELECT . . .  FROM "MySchema"."MyTable" WHERE ("MyTable"."MyValue" <> ? OR
> "MyTable"."MyValue" IS NULL)
>
>
> If the input parameter is a NULL, this where clause is not helpful.  "<>
> NULL" is likely to be invalid and "IS NULL" is the wrong thing. The goal is
> "IS NOT NULL"
> The generated query would make perfect sense if the input parameter was a
> value like "foo", but this approach falls apart with null input parameters.
>
> Any suggestions for a workaround would be greatly appreciated!
>
>
> Tim Kingsbury
>
>
>
>
>
>

Fwd: REMINDER - TAC Applications closes in 2 weeks for ACNA Montréal

[Kasper Sørensen]

Hi folks,

Anyone contemplating on going to ApacheCon NA 2018? Please check the travel
assistance below!

Best regards,
Kasper

—
Reminder that travel assistance applications for ApacheCon NA 2018 are
still open but only for another* 2 weeks*!
Please get your applications in NOW.

We will be supporting ApacheCon NA Montréal, Canada on 24th - 29th
September 2018

 TAC exists to help those that would like to attend ApacheCon events, but
are unable to do so for financial reasons.
For more info on this years applications and qualifying criteria, please
visit the TAC website at < http://www.apache.org/travel/ >. Applications
are now open and will close 1st May.

*Important*: Applications close on May 1st, 2018. Applicants have until the
closing date above to submit their applications (which should contain as
much supporting material as required to efficiently and accurately process
their request), this will enable TAC to announce successful awards shortly
afterwards.

As usual, TAC expects to deal with a range of applications from a diverse
range of backgrounds. We therefore encourage (as always) anyone thinking
about sending in an application to do so ASAP.
We look forward to greeting many of you in Montreal

Kind Regards,
Gavin - (On behalf of the Travel Assistance Committee)

Travel Assistance applications open. Please inform your communities

[Kasper Sørensen]

For anyone considering joining ApacheCon:

> From: Gavin McDonald 
> Date: February 14, 2018 at 01:34:11 PST
> To: travel-assista...@apache.org
> Subject: Travel Assistance applications open. Please inform your communities
> Reply-To: priv...@metamodel.apache.org
> Reply-To: travel-assista...@apache.org
> 
> Hello PMCs.
> 
> Please could you forward on the below email to your dev and user lists.
> 
> Thanks
> 
> Gav…
> 
> —
> The Travel Assistance Committee (TAC) are pleased to announce that travel 
> assistance applications for ApacheCon NA 2018 are now open!
> 
> We will be supporting ApacheCon NA Montreal, Canada on 24th - 29th September 
> 2018
> 
>  TAC exists to help those that would like to attend ApacheCon events, but are 
> unable to do so for financial reasons. 
> For more info on this years applications and qualifying criteria, please 
> visit the TAC website at < http://www.apache.org/travel/ >. Applications are 
> now open and will close 1st May. 
> 
> Important: Applications close on May 1st, 2018. Applicants have until the 
> closing date above to submit their applications (which should contain as much 
> supporting material as required to efficiently and accurately process their 
> request), this will enable TAC to announce successful awards shortly 
> afterwards. 
> 
> As usual, TAC expects to deal with a range of applications from a diverse 
> range of backgrounds. We therefore encourage (as always) anyone thinking 
> about sending in an application to do so ASAP.   
> We look forward to greeting many of you in Montreal
> 
> Kind Regards, 
> Gavin - (On behalf of the Travel Assistance Committee)
> — 
> 
> 

Re: Issues with Cassandra

[Kasper Sørensen]

But this assert does not exist in MM. My suggestion: Open a debug session and 
figure out what and why you’re asserting whatever it is you’re asserting 
related to bigint.

> On Jan 31, 2018, at 23:43, Gajanan Patil  wrote:
> 
> Here we wrapped MetaModel layer wrapped by our own custom. However underline 
> we have used functions as is provided by MetaModel. So in this case if we 
> consider FuDataSet.java, it is a mirror copy of IDataset only. In other words 
> we kept the isolation of MetaModel from actual tests in our framework to make 
> it more modular.
> FuDataSet.toRows is nothing but DataSet.toRows.
> 
> 
> On 1 Feb 2018 1:06 pm, Kasper Sørensen  wrote:
> I dont see MetaModel anywhere in that stack so the issue is probably just 
> with your own code?
> 
> Kasper
> 
>> On Jan 31, 2018, at 21:11, Gajanan Patil  wrote:
>> 
>> My bad sorry for spamming
>> 
>> java.lang.AssertionError: Codec not found for requested operation: [bigint
>> <-> java.math.BigInteger] Please check expressions in the filteritems or
>> where statements 
>> 
>>   at org.testng.Assert.fail(Assert.java:93)
>> 
>>   at
>> com.cybage.frameworkutility.utilities.Report.LogFail(Report.java:587)
>> 
>>   at
>> com.cybage.dbFramework.FuDataSet.toRows(FuDataSet.java:39)
>> 
>>   at
>> com.cybage.genericlibrary.DataSetMethods.getRowCount(DataSetMethods.java:286)
>> 
>>   at
>> com.cybage.genericlibrary.DBBaseClass.getRowCount(DBBaseClass.java:519)
>> 
>>   at
>> com.database.tests.CassandraDBTests.EmbededDBTest(CassandraDBTests.java:42)
>> 
>>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>> 
>>   at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> 
>>   at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> 
>>   at java.lang.reflect.Method.invoke(Method.java:498)
>> 
>>   at
>> org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:108)
>> 
>>   at
>> org.testng.internal.Invoker.invokeMethod(Invoker.java:661)
>> 
>>   at
>> org.testng.internal.Invoker.invokeTestMethod(Invoker.java:869)
>> 
>>   at
>> org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1193)
>> 
>>   at
>> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:126)
>> 
>>   at
>> org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
>> 
>>   at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>> 
>>   at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>> 
>>   at java.lang.Thread.run(Thread.java:748)
>> 
>> 
>> 
>> On 1 Feb 2018 10:39 am, "Gajanan Patil"  wrote:
>> 
>> 
>> PFA below trace I got.
>> 
>> 
>> com.cybage.frameworkutility.utilities.Report.LogFail(Report.java:587)
>> 
>>   at com.cybage.dbFramework.FuDataSet.toRows(FuDataSet.
>> java:39)
>> 
>>   at com.cybage.genericlibrary.DataSetMethods.getRowCount(
>> DataSetMethods.java:286)
>> 
>>   at com.cybage.genericlibrary.DBBaseClass.getRowCount(
>> DBBaseClass.java:519)
>> 
>>   at com.database.tests.CassandraDBTests.EmbededDBTest(
>> CassandraDBTests.java:42)
>> 
>> On 1 Feb 2018 10:29 am, "Kasper Sørensen" 
>> wrote:
>> 
>>> Sorry, no I don't have much clue about it.
>>> 
>>> That AssertionError ... can you show us the stack trace for it?
>>> 
>>> 2018-01-31 20:51 GMT-08:00 Gajanan Patil :
>>> 
>>>> Any clue on this?
>>>> 
>>>> 
>>>> 
>>>> I am trying below scenarios but unable to do so
>>>> 
>>>> 1- when a *wrong* columnname is provided in where clause for cassandra
>>>> query,  MetaModel; parse it successfully and proceed further instead
>>>> throwing exception message while parsing itself.
>>>> 
>>>> 2- another is while querying on the column with *BigInt* Datatype in the
>>>> table,  of cassandra db throws below error
>>>> 
>>>> *Java. Lang. Assertionerror: Codec not found for requested ope

Re: Issues with Cassandra

[Kasper Sørensen]

I dont see MetaModel anywhere in that stack so the issue is probably just with 
your own code?

Kasper

> On Jan 31, 2018, at 21:11, Gajanan Patil  wrote:
> 
> My bad sorry for spamming
> 
> java.lang.AssertionError: Codec not found for requested operation: [bigint
> <-> java.math.BigInteger] Please check expressions in the filteritems or
> where statements 
> 
>at org.testng.Assert.fail(Assert.java:93)
> 
>at
> com.cybage.frameworkutility.utilities.Report.LogFail(Report.java:587)
> 
>at
> com.cybage.dbFramework.FuDataSet.toRows(FuDataSet.java:39)
> 
>at
> com.cybage.genericlibrary.DataSetMethods.getRowCount(DataSetMethods.java:286)
> 
>at
> com.cybage.genericlibrary.DBBaseClass.getRowCount(DBBaseClass.java:519)
> 
>at
> com.database.tests.CassandraDBTests.EmbededDBTest(CassandraDBTests.java:42)
> 
>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> 
>at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 
>at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 
>at java.lang.reflect.Method.invoke(Method.java:498)
> 
>at
> org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:108)
> 
>at
> org.testng.internal.Invoker.invokeMethod(Invoker.java:661)
> 
>at
> org.testng.internal.Invoker.invokeTestMethod(Invoker.java:869)
> 
>at
> org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1193)
> 
>at
> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:126)
> 
>at
> org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
> 
>at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 
>at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 
>at java.lang.Thread.run(Thread.java:748)
> 
> 
> 
> On 1 Feb 2018 10:39 am, "Gajanan Patil"  wrote:
> 
> 
> PFA below trace I got.
> 
> 
> com.cybage.frameworkutility.utilities.Report.LogFail(Report.java:587)
> 
>at com.cybage.dbFramework.FuDataSet.toRows(FuDataSet.
> java:39)
> 
>at com.cybage.genericlibrary.DataSetMethods.getRowCount(
> DataSetMethods.java:286)
> 
>at com.cybage.genericlibrary.DBBaseClass.getRowCount(
> DBBaseClass.java:519)
> 
>at com.database.tests.CassandraDBTests.EmbededDBTest(
> CassandraDBTests.java:42)
> 
> On 1 Feb 2018 10:29 am, "Kasper Sørensen" 
> wrote:
> 
>> Sorry, no I don't have much clue about it.
>> 
>> That AssertionError ... can you show us the stack trace for it?
>> 
>> 2018-01-31 20:51 GMT-08:00 Gajanan Patil :
>> 
>>> Any clue on this?
>>> 
>>> 
>>> 
>>> I am trying below scenarios but unable to do so
>>> 
>>> 1- when a *wrong* columnname is provided in where clause for cassandra
>>> query,  MetaModel; parse it successfully and proceed further instead
>>> throwing exception message while parsing itself.
>>> 
>>> 2- another is while querying on the column with *BigInt* Datatype in the
>>> table,  of cassandra db throws below error
>>> 
>>> *Java. Lang. Assertionerror: Codec not found for requested operation : [
>>> bigint <-> java. math. BigInteger ] please check expressions in the
>> filter
>>> items or where statements.*
>>> 
>>> 
>>> 
>>> 
>>> Thank you
>>> 
>>> Regards,
>>> GP
>>> 
>> 

Re: Issues with Cassandra

[Kasper Sørensen]

Sorry, no I don't have much clue about it.

That AssertionError ... can you show us the stack trace for it?

2018-01-31 20:51 GMT-08:00 Gajanan Patil :

> Any clue on this?
>
>
>
> I am trying below scenarios but unable to do so
>
> 1- when a *wrong* columnname is provided in where clause for cassandra
> query,  MetaModel; parse it successfully and proceed further instead
> throwing exception message while parsing itself.
>
> 2- another is while querying on the column with *BigInt* Datatype in the
> table,  of cassandra db throws below error
>
> *Java. Lang. Assertionerror: Codec not found for requested operation : [
> bigint <-> java. math. BigInteger ] please check expressions in the filter
> items or where statements.*
>
>
>
>
> Thank you
>
> Regards,
> GP
>

Re: count / distinct SQL

[Kasper Sørensen]

There's no direct equivalent to COUNT(DISTINCT x)) in MetaModel. But you
could get the same result using a subquery, and most database engines would
probably also plan the query in the same way. Basically you would then do:

SELECT COUNT(*) FROM (SELECT DISTINCT text1 FROM small_table)

2018-01-31 5:16 GMT-08:00 Dana Borger :

>
> Suppose I have a table and rows like (fwiw, Postgres):
>
> CREATE TABLE small_table (
>   key1  INTEGER NOT NULL,
>   text1 VARCHAR(10),
>   text2 VARCHAR(10),
>   text3 VARCHAR(10),
>   text4 VARCHAR(10)
> );
> ALTER TABLE small_table ADD CONSTRAINT small_table_pk PRIMARY KEY (key1);
> INSERT INTO small_table VALUES (1, 'a', 'a', 'a', 'a');
> INSERT INTO small_table VALUES (2, 'a', 'b', 'b', 'b');
> INSERT INTO small_table VALUES (3, 'a', 'b', 'c', 'c');
> INSERT INTO small_table VALUES (4, 'a', 'b', 'c', 'd');
>
>
> Is there a way with the MM API to construct this query:
>
> SELECT COUNT(DISTINCT text1) FROM small_table;
>
> ?
>
> which returns (count) = (1) which is what i want. ‘text1’ has 1 distinct
> value (‘a’).
>
>
> Using the API this way, it produces a different query than what I want:
>
> Table table = connection.getTableByName("small_table");
> Query q = new Query();
> q.from(table).select("text1");
> q.groupBy("text1");
> q.selectDistinct().selectCount();
>
> —>
>
> SELECT DISTINCT “small_table”."text1", COUNT(*)
> FROM ”small_table”
> GROUP BY “small_table”."text1"
>
> which returns: (text1,count) = (a, 4)  [ not what i want ]
>
>
> Thanks,
> Dana
>
>

[RESULT] [VOTE] Apache MetaModel release 5.1.0-RC1

[Kasper Sørensen]

Hi all,

The vote is over and we have 4 votes for, 0 votes against the release:

Kasper Sørensen *
Lutzen Luinenburg
Alberto Rodriguez *
Dennis Du Krøger *

 * = indicates PMC.

I will continue to finalize the release now.

Kasper


2018-01-29 11:32 GMT-08:00 Dennis Krøger :

> +1
>
> On Fri, Jan 26, 2018 at 8:20 PM Kasper Sørensen <
> i.am.kasper.soren...@gmail.com> wrote:
>
> > +1
> >
> > 2018-01-25 23:25 GMT-08:00 Alberto Rodriguez :
> >
> > > +1
> > >
> > > 2018-01-26 7:32 GMT+01:00 Lutzen Luinenburg  >:
> > >
> > > > +1
> > > > 
> > > > Van: Kasper S?rensen 
> > > > Verzonden: vrijdag 26 januari 2018 07:08:59
> > > > Aan: dev@metamodel.apache.org
> > > > Onderwerp: [VOTE] Apache MetaModel release 5.1.0-RC1
> > > >
> > > > Hi All,
> > > >
> > > > Please vote on releasing the following candidate as Apache Metamodel
> > > >  version 5.1.0-RC1.
> > > >
> > > > The Git tag to be voted on is MetaModel-5.1.0-RC1:
> > > > https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=
> > > > 1969a3f13e4bde186328bebb24b6c82c79b7d90a
> > > >
> > > > The source artifact to be voted on is:
> > > > https://repository.apache.org/content/repositories/
> > > > orgapachemetamodel-1030/org/apache/metamodel/MetaModel/5.
> > > > 1.0-RC1/MetaModel-5.1.0-RC1-source-release.zip
> > > >
> > > > Parent directory (including MD5, SHA1 hashes etc.) of the source is:
> > > > https://repository.apache.org/content/repositories/
> > > > orgapachemetamodel-1030/org/apache/metamodel/
> > > >
> > > > Release artifacts are signed with the following key:
> > > > https://people.apache.org/keys/committer/kaspersor.asc
> > > >
> > > > Release engineer public key id: https://people.apache.org/
> > > > keys/committer/kaspersor.asc
> > > >
> > > > The staging Maven repository for this release can be found at:
> > > > https://repository.apache.org/content/repositories/
> > > > orgapachemetamodel-1030/
> > > >
> > > > Please vote on releasing this package as Apache MetaModel 5.1.0-RC1.
> > > >
> > > > The vote is open for 72 hours.
> > > >
> > > > [ ] +1 Release this package as Apache MetaModel 5.1.0-RC1
> > > > [ ] -1 Do not release this package because ...
> > > >
> > > > Thank you in advance for participating.
> > > >
> > > > Regards,
> > > > Kasper
> > > >
> > >
> >
> --
> Med venlig hilsen,
> Dennis Du Krøger
>

Re: [VOTE] Apache MetaModel release 5.1.0-RC1

[Kasper Sørensen]

+1

2018-01-25 23:25 GMT-08:00 Alberto Rodriguez :

> +1
>
> 2018-01-26 7:32 GMT+01:00 Lutzen Luinenburg :
>
> > +1
> > 
> > Van: Kasper S?rensen 
> > Verzonden: vrijdag 26 januari 2018 07:08:59
> > Aan: dev@metamodel.apache.org
> > Onderwerp: [VOTE] Apache MetaModel release 5.1.0-RC1
> >
> > Hi All,
> >
> > Please vote on releasing the following candidate as Apache Metamodel
> >  version 5.1.0-RC1.
> >
> > The Git tag to be voted on is MetaModel-5.1.0-RC1:
> > https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=
> > 1969a3f13e4bde186328bebb24b6c82c79b7d90a
> >
> > The source artifact to be voted on is:
> > https://repository.apache.org/content/repositories/
> > orgapachemetamodel-1030/org/apache/metamodel/MetaModel/5.
> > 1.0-RC1/MetaModel-5.1.0-RC1-source-release.zip
> >
> > Parent directory (including MD5, SHA1 hashes etc.) of the source is:
> > https://repository.apache.org/content/repositories/
> > orgapachemetamodel-1030/org/apache/metamodel/
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/kaspersor.asc
> >
> > Release engineer public key id: https://people.apache.org/
> > keys/committer/kaspersor.asc
> >
> > The staging Maven repository for this release can be found at:
> > https://repository.apache.org/content/repositories/
> > orgapachemetamodel-1030/
> >
> > Please vote on releasing this package as Apache MetaModel 5.1.0-RC1.
> >
> > The vote is open for 72 hours.
> >
> > [ ] +1 Release this package as Apache MetaModel 5.1.0-RC1
> > [ ] -1 Do not release this package because ...
> >
> > Thank you in advance for participating.
> >
> > Regards,
> > Kasper
> >
>

[VOTE] Apache MetaModel release 5.1.0-RC1

[Kasper Sørensen]

Hi All,

Please vote on releasing the following candidate as Apache Metamodel
 version 5.1.0-RC1.

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

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

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

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

Release engineer public key id: https://people.apache.org/
keys/committer/kaspersor.asc

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

Please vote on releasing this package as Apache MetaModel 5.1.0-RC1.

The vote is open for 72 hours.

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

Thank you in advance for participating.

Regards,
Kasper

Re: INSERT with a SELECT subquery

[Kasper Sørensen]

I don't know what you're doing here since your formatting is very strange
looking.
I do see that you're dropping a table, which I don't understand why. Is it
failing because you're trying to insert into the table that was just
dropped?
Regardless, if you want help fixing your issues, please also provide an
exception stack trace.

2018-01-17 1:55 GMT-08:00 gowri.tn :

>
>
> Table table = dataContext.getTableByQualifiedLabel("test");
>
>
> dc.executeUpdate(new UpdateScript() {
>
>  @Override
>
>  public void run(UpdateCallback callback) {
>
>  callback.dropTable(schema.getTableByName("test")).execute();
>
>  }
>  });
>
>
> while(ds.next()) {
>
> >
> >  System.out.println(">>> " + Arrays.toString(ds.getRow().getValues()));
> >
>
>
> >
> >  callback.insertInto(table).values(ds.getRow()).execute();
> >
>
> >
>
>
>
> }
>
> OUTPUT:
>
> Excel sheet:(ds.getRow())
>  >>> [1, abi, female, 21]
> >>> [2, banu, female, 16]
> >>> [3, cibi, female, 18]
> >>> [4, divi, female, 20]
> >>> [5, elakiya, female, 21]
> >>> [6, fahir, true, 25]
> >>> [7, goki, male, 21]
> >>> [8, deep, male, 19]
> >>> [9, false, female, raja]
>
> >
>
> Here is our output for the previous code for getting rows from Excel
> Datasheet. We are not able to insert the values into a Postgresql Table
> with the code given by your last mail The method, public void
> run(UpdateCallback callback) is not working Please help us in this regard.
>
> With regards,
>
> Gowri
>
>
>
>
> On 01/11/18 09:36 AM, Kasper Sørensen  
> wrote:
> >
> > Hi there,
> >
> > No that's not available. But you do get something quite equivalent with
> > this:
> >
> > Table table = dataContext.getTableByName("us_south_es_etg");
> > dataContext.executeUpdate(callback -> {
> >  try (DataSet ds =
> > dataContext.query().from("us_south").selectAll().execute()) {
> >  while (ds.next()) {
> >  callback.insertInto(table).values(ds.getRow()).execute();
> >  }
> >  }
> > });
> >
> >
>
> >
> >
> > 2018-01-10 10:15 GMT-08:00 Tim Kingsbury :
> >
> > > Hello,
> > >
> > > Using Metamodel, is it possible to build an INSERT statement that is
> > > paired with a SELECT subquery? For example:
> > >
> > > INSERT TABLE `us_south_es_etg`
> > > SELECT
> > > `lon`,
> > > `lat`,
> > > `number`,
> > > `street`,
> > > `unit`,
> > > `city`,
> > > `district`,
> > > `region`,
> > > `postcode`,
> > > `id`,
> > > `hash`
> > > FROM us_south;
> > >
> > >
> > > Any suggestions would be greatly appreciated!
> > >
> > >
> > > Tim
> > >
> > >
> >
>

Re: INSERT with a SELECT subquery

[Kasper Sørensen]

Hi there,

No that's not available. But you do get something quite equivalent with
this:

Table table = dataContext.getTableByName("us_south_es_etg");
dataContext.executeUpdate(callback -> {
  try (DataSet ds =
dataContext.query().from("us_south").selectAll().execute()) {
while (ds.next()) {
  callback.insertInto(table).values(ds.getRow()).execute();
}
  }
});


2018-01-10 10:15 GMT-08:00 Tim Kingsbury :

> Hello,
>
> Using Metamodel, is it possible to build an INSERT statement that is
> paired with a SELECT subquery?  For example:
>
> INSERT TABLE `us_south_es_etg`
> SELECT
>`lon`,
>`lat`,
>`number`,
>`street`,
>`unit`,
>`city`,
>`district`,
>`region`,
>`postcode`,
>`id`,
>`hash`
> FROM us_south;
>
>
> Any suggestions would be greatly appreciated!
>
>
> Tim
>
>

Re: Regarding implementation of apache meta model

[Kasper Sørensen]

Hi Gowri,

Looks like your code is almost there. It's querying the excel file, just
not inserting anything into Postgres. Correct?
You just need to make those insert using the "dc" object (which seems to be
your postgres database):

dc.executeUpdate(callback -> {
  callback.insert(...)
});

2018-01-10 2:03 GMT-08:00 gowri.tn :

> Respected Sir/Madam,
>   We are implementing Apache Metamodel for getting
> Excel Sheet Data to Postgresql Table . I am enclosing here with the code
> we have written for the above and the output we got after running the class
> file on console using Eclipse Oxygen
>
> Please see the attached file and give us sample code for inserting the data
> to postgresql table. Your earliest reponse in this regard will be most
> helpful for us.
>
> Thanking you in advance,
>
> With regards,
>
> Gowri S
>

Re: [VOTE] Apache Metamodel release 5.0.1

[Kasper Sørensen]

Thank you to everyone who voted. We have a release with 4 votes for, 0
votes against:

Kasper Sørensen *
Alberto Rodriguez *
Lutzen Luinenburg
Dennis Du Krøger *

* = indicates PMC.

I'll continue to finalize the release process. It might take a while longer
than usual though, due to the holidays, I might not have a ton of time for
website etc.

2017-12-22 1:33 GMT-08:00 Dennis Du Krøger :

> +1
>
>
> On 22 December 2017 10:21:47 CET, Lutzen Luinenburg <
> l.luinenb...@quadient.com> wrote:
> >+1
> >
> >-Original Message-
> >From: Kasper Sørensen [mailto:i.am.kasper.soren...@gmail.com]
> >Sent: Wednesday, 20 December 2017 05:59
> >To: dev@metamodel.apache.org
> >Subject: [VOTE] Apache Metamodel release 5.0.1
> >
> >Hi All,
> >
> >Please vote on releasing the following candidate as Apache Metamodel
> >version 5.0.1.
> >
> >The Git tag to be voted on is MetaModel-5.0.1:
> >https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=
> 2fb51a10866e3ffbf4373dd67959ffb9f67e5d63
> >
> >The source artifact to be voted on is:
> >http://repository.apache.org/content/repositories/
> orgapachemetamodel-1029/org/apache/metamodel/MetaModel/5.
> 0.1/MetaModel-5.0.1-source-release.zip
> >
> >Parent directory (including MD5, SHA1 hashes etc.) of the source is:
> >http://repository.apache.org/content/repositories/
> orgapachemetamodel-1029/org/apache/metamodel/MetaModel/5.0.1/
> >
> >Release artifacts are signed with the following key:
> >https://people.apache.org/keys/committer/kaspersor.asc
> >
> >Release engineer public key id:
> >https://people.apache.org/keys/committer/kaspersor.asc
> >
> >The staging Maven repository for this release can be found at:
> >http://repository.apache.org/content/repositories/orgapachemetamodel-1029
> >
> >Please vote on releasing this package as Apache MetaModel 5.0.1.
> >
> >The vote is open for 72 hours.
> >
> >[ ] +1 Release this package as Apache MetaModel 5.0.1 [ ] -1 Do not
> >release this package because ...
> >
> >Thank you in advance for participating.
> >
> >Regards,
> >Kasper
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [VOTE] Apache Metamodel release 5.0.1

[Kasper Sørensen]

+1 from myself :-)

2017-12-19 20:58 GMT-08:00 Kasper Sørensen :

> Hi All,
>
> Please vote on releasing the following candidate as Apache Metamodel
> version 5.0.1.
>
> The Git tag to be voted on is MetaModel-5.0.1:
> https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=
> 2fb51a10866e3ffbf4373dd67959ffb9f67e5d63
>
> The source artifact to be voted on is:
> http://repository.apache.org/content/repositories/
> orgapachemetamodel-1029/org/apache/metamodel/MetaModel/5.
> 0.1/MetaModel-5.0.1-source-release.zip
>
> Parent directory (including MD5, SHA1 hashes etc.) of the source is:
> http://repository.apache.org/content/repositories/
> orgapachemetamodel-1029/org/apache/metamodel/MetaModel/5.0.1/
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/kaspersor.asc
>
> Release engineer public key id: https://people.apache.org/
> keys/committer/kaspersor.asc
>
> The staging Maven repository for this release can be found at:
> http://repository.apache.org/content/repositories/orgapachemetamodel-1029
>
> Please vote on releasing this package as Apache MetaModel 5.0.1.
>
> The vote is open for 72 hours.
>
> [ ] +1 Release this package as Apache MetaModel 5.0.1
> [ ] -1 Do not release this package because ...
>
> Thank you in advance for participating.
>
> Regards,
> Kasper
>

[VOTE] Apache Metamodel release 5.0.1

[Kasper Sørensen]

Hi All,

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

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

The source artifact to be voted on is:
http://repository.apache.org/content/repositories/orgapachemetamodel-1029/org/apache/metamodel/MetaModel/5.0.1/MetaModel-5.0.1-source-release.zip

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

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

Release engineer public key id:
https://people.apache.org/keys/committer/kaspersor.asc

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

Please vote on releasing this package as Apache MetaModel 5.0.1.

The vote is open for 72 hours.

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

Thank you in advance for participating.

Regards,
Kasper

Re: [RESULT] [VOTE] Apache MetaModel release 4.6.1

[Kasper Sørensen]

Thanks for the update ;-)

2017-11-26 22:53 GMT-08:00 Dennis Du Krøger :

> I don't get it. My mails from MM are super flaky. I get some (like this
> last one), but not others (like all previous mails for this release ). I
> think my mail server or connection might have troubles. Time to move to
> some cloud thing, I guess. Sorry about that.
>
> Anyway, I'd have given a +1.
>
> /Dennis
>
> On 26 November 2017 23:29:56 CET, "Kasper Sørensen"  kasper.soren...@gmail.com> wrote:
>>
>> Okay, seems we have a result and a majority to release. Just two votes 
>> though, which isn’t really a lot and I would encourage more people to 
>> participate. Especially those who helped work on the changes that are in 
>> here.
>>
>> I’ll continue with the release work.
>>
>> Kasper Sørensen
>>
>>  On Nov 26, 2017, at 01:00, Alberto Rodriguez  wrote:
>>>
>>>  +1
>>>
>>>  El 25 nov. 2017 21:29, "Kasper Sørensen" 
>>>  escribió:
>>>
>>>  +1
>>>>
>>>>  And: Bump. Please remember to cast your votes.
>>>>
>>>>  2017-11-23 12:40 GMT-08:00 Kasper Sørensen >>>
>>>>>  :
>>>>>
>>>>
>>>>  Hi All,
>>>>>
>>>>>  Please vote for the release of MetaModel 4.6.1.
>>>>>
>>>>>  The Git tag to be voted on is MetaModel-4.6.1:
>>>>>  *https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=
>>>>>
>>>>  00adacaa8156b496ffe0925e58ac5b063b42fa9d
>>>>
>>>>>  <https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=
>>>>>
>>>>  00adacaa8156b496ffe0925e58ac5b063b42fa9d>*
>>>>
>>>>>
>>>>>  The source artifact to be voted on is:
>>>>>  *https://repository.apache.org/content/repositories/
>>>>>
>>>>  orgapachemetamodel-1028/org/apache/metamodel/MetaModel/4.
>>>>  6.1/MetaModel-4.6.1-source-release.zip
>>>>
>>>>>  <https://repository.apache.org/content/repositories/
>>>>>
>>>>  orgapachemetamodel-1028/org/apache/metamodel/MetaModel/4.
>>>>  6.1/MetaModel-4.6.1-source-release.zip>*
>>>>
>>>>>
>>>>>  Parent directory (including MD5, SHA1 hashes etc.) of the source is:
>>>>>  https://repository.apache.org/content/repositories/
>>>>>  orgapachemetamodel-1028/org/apache/metamodel/MetaModel/4.6.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-1028/
>>>>>
>>>>>  Please vote on releasing this package as Apache MetaModel 4.6.1.
>>>>>
>>>>>  The vote is open for 72 hours.
>>>>>
>>>>>  [ ] +1 Release this package as Apache MetaModel 4.6.1
>>>>>  [ ] -1 Do not release this package because ...
>>>>>
>>>>>  Thank you in advance for participating.
>>>>>
>>>>>  Regards,
>>>>>  Kasper Sørensen
>>>>>
>>>>>
>>>>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>

[RESULT] [VOTE] Apache MetaModel release 4.6.1

[Kasper Sørensen]

Okay, seems we have a result and a majority to release. Just two votes though, 
which isn’t really a lot and I would encourage more people to participate. 
Especially those who helped work on the changes that are in here.

I’ll continue with the release work.

Kasper Sørensen

> On Nov 26, 2017, at 01:00, Alberto Rodriguez  wrote:
> 
> +1
> 
> El 25 nov. 2017 21:29, "Kasper Sørensen" 
> escribió:
> 
>> +1
>> 
>> And: Bump. Please remember to cast your votes.
>> 
>> 2017-11-23 12:40 GMT-08:00 Kasper Sørensen >> :
>> 
>>> Hi All,
>>> 
>>> Please vote for the release of MetaModel 4.6.1.
>>> 
>>> The Git tag to be voted on is MetaModel-4.6.1:
>>> *https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=
>> 00adacaa8156b496ffe0925e58ac5b063b42fa9d
>>> <https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=
>> 00adacaa8156b496ffe0925e58ac5b063b42fa9d>*
>>> 
>>> The source artifact to be voted on is:
>>> *https://repository.apache.org/content/repositories/
>> orgapachemetamodel-1028/org/apache/metamodel/MetaModel/4.
>> 6.1/MetaModel-4.6.1-source-release.zip
>>> <https://repository.apache.org/content/repositories/
>> orgapachemetamodel-1028/org/apache/metamodel/MetaModel/4.
>> 6.1/MetaModel-4.6.1-source-release.zip>*
>>> 
>>> Parent directory (including MD5, SHA1 hashes etc.) of the source is:
>>> https://repository.apache.org/content/repositories/
>>> orgapachemetamodel-1028/org/apache/metamodel/MetaModel/4.6.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-1028/
>>> 
>>> Please vote on releasing this package as Apache MetaModel 4.6.1.
>>> 
>>> The vote is open for 72 hours.
>>> 
>>> [ ] +1 Release this package as Apache MetaModel 4.6.1
>>> [ ] -1 Do not release this package because ...
>>> 
>>> Thank you in advance for participating.
>>> 
>>> Regards,
>>> Kasper Sørensen
>>> 
>> 

Re: [VOTE] Apache MetaModel release 4.6.1

[Kasper Sørensen]

+1

And: Bump. Please remember to cast your votes.

2017-11-23 12:40 GMT-08:00 Kasper Sørensen :

> Hi All,
>
> Please vote for the release of MetaModel 4.6.1.
>
> The Git tag to be voted on is MetaModel-4.6.1:
> *https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=00adacaa8156b496ffe0925e58ac5b063b42fa9d
> <https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=00adacaa8156b496ffe0925e58ac5b063b42fa9d>*
>
> The source artifact to be voted on is:
> *https://repository.apache.org/content/repositories/orgapachemetamodel-1028/org/apache/metamodel/MetaModel/4.6.1/MetaModel-4.6.1-source-release.zip
> <https://repository.apache.org/content/repositories/orgapachemetamodel-1028/org/apache/metamodel/MetaModel/4.6.1/MetaModel-4.6.1-source-release.zip>*
>
> Parent directory (including MD5, SHA1 hashes etc.) of the source is:
> https://repository.apache.org/content/repositories/
> orgapachemetamodel-1028/org/apache/metamodel/MetaModel/4.6.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-1028/
>
> Please vote on releasing this package as Apache MetaModel 4.6.1.
>
> The vote is open for 72 hours.
>
> [ ] +1 Release this package as Apache MetaModel 4.6.1
> [ ] -1 Do not release this package because ...
>
> Thank you in advance for participating.
>
> Regards,
> Kasper Sørensen
>

[VOTE] Apache MetaModel release 4.6.1

[Kasper Sørensen]

Hi All,

Please vote for the release of MetaModel 4.6.1.

The Git tag to be voted on is MetaModel-4.6.1:
*https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=00adacaa8156b496ffe0925e58ac5b063b42fa9d
<https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=00adacaa8156b496ffe0925e58ac5b063b42fa9d>*

The source artifact to be voted on is:
*https://repository.apache.org/content/repositories/orgapachemetamodel-1028/org/apache/metamodel/MetaModel/4.6.1/MetaModel-4.6.1-source-release.zip
<https://repository.apache.org/content/repositories/orgapachemetamodel-1028/org/apache/metamodel/MetaModel/4.6.1/MetaModel-4.6.1-source-release.zip>*

Parent directory (including MD5, SHA1 hashes etc.) of the source is:
https://repository.apache.org/content/repositories/orgapachemetamodel-1028/org/apache/metamodel/MetaModel/4.6.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-1028/

Please vote on releasing this package as Apache MetaModel 4.6.1.

The vote is open for 72 hours.

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

Thank you in advance for participating.

Regards,
Kasper Sørensen

[RESULT] [VOTE] Apache Metamodel Membrane release 0.1

[Kasper Sørensen]

The vote has ended with 3 votes for (all PMC), and no votes against!

Kasper Sørensen
Alberto Rodriguez
Dennis Du Krøger

Thank you to all who voted. I'll continue with the release.
Docker image already available: "apache/metamodel-membrane:0.1" - see
https://hub.docker.com/r/apache/metamodel-membrane/

2017-11-10 9:18 GMT-08:00 Dennis Du Krøger :

> +1
>
>
> On 2017-11-10 18:17, Kasper Sørensen wrote:
>
>> +1
>>
>> Kasper Sørensen
>>
>> On Nov 10, 2017, at 09:08, Alberto Rodriguez  wrote:
>>>
>>> +1
>>>
>>> El 10 nov. 2017 18:00, "Kasper Sørensen" >> >
>>> escribió:
>>>
>>> Hi All,
>>>>
>>>> I am proposing the first release of the Membrane subproject! :-)
>>>>
>>>> Please vote on releasing the following candidate as Apache Metamodel
>>>> Membrane version 0.1.
>>>>
>>>> The Git tag to be voted on is Membrane-parent-0.1:
>>>> https://git-wip-us.apache.org/repos/asf?p=metamodel-
>>>> membrane.git;a=commit;h=00d216baedee805e165dae113f820e554012d452
>>>>
>>>> The source artifact to be voted on is:
>>>> https://repository.apache.org/content/repositories/
>>>> orgapachemetamodel-1027/org/apache/metamodel/membrane/
>>>> Membrane-parent/0.1/Membrane-parent-0.1-source-release.zip
>>>>
>>>> Parent directory (including MD5, SHA1 hashes etc.) of the source is:
>>>> https://repository.apache.org/content/repositories/
>>>> orgapachemetamodel-1027/org/apache/metamodel/membrane/Membra
>>>> ne-parent/0.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-1027/
>>>>
>>>> Please vote on releasing this package as Apache MetaModel Membrane 0.1.
>>>>
>>>> The vote is open for 72 hours.
>>>>
>>>> [ ] +1 Release this package as Apache MetaModel Membrane 0.1
>>>> [ ] -1 Do not release this package because ...
>>>>
>>>> Thank you in advance for participating.
>>>>
>>>>

Re: [VOTE] Apache Metamodel Membrane release 0.1

[Kasper Sørensen]

+1

Kasper Sørensen

> On Nov 10, 2017, at 09:08, Alberto Rodriguez  wrote:
> 
> +1
> 
> El 10 nov. 2017 18:00, "Kasper Sørensen" 
> escribió:
> 
>> Hi All,
>> 
>> I am proposing the first release of the Membrane subproject! :-)
>> 
>> Please vote on releasing the following candidate as Apache Metamodel
>> Membrane version 0.1.
>> 
>> The Git tag to be voted on is Membrane-parent-0.1:
>> https://git-wip-us.apache.org/repos/asf?p=metamodel-
>> membrane.git;a=commit;h=00d216baedee805e165dae113f820e554012d452
>> 
>> The source artifact to be voted on is:
>> https://repository.apache.org/content/repositories/
>> orgapachemetamodel-1027/org/apache/metamodel/membrane/
>> Membrane-parent/0.1/Membrane-parent-0.1-source-release.zip
>> 
>> Parent directory (including MD5, SHA1 hashes etc.) of the source is:
>> https://repository.apache.org/content/repositories/
>> orgapachemetamodel-1027/org/apache/metamodel/membrane/Membrane-parent/0.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-1027/
>> 
>> Please vote on releasing this package as Apache MetaModel Membrane 0.1.
>> 
>> The vote is open for 72 hours.
>> 
>> [ ] +1 Release this package as Apache MetaModel Membrane 0.1
>> [ ] -1 Do not release this package because ...
>> 
>> Thank you in advance for participating.
>> 

[VOTE] Apache Metamodel Membrane release 0.1

[Kasper Sørensen]

Hi All,

I am proposing the first release of the Membrane subproject! :-)

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

The Git tag to be voted on is Membrane-parent-0.1:
https://git-wip-us.apache.org/repos/asf?p=metamodel-membrane.git;a=commit;h=00d216baedee805e165dae113f820e554012d452

The source artifact to be voted on is:
https://repository.apache.org/content/repositories/orgapachemetamodel-1027/org/apache/metamodel/membrane/Membrane-parent/0.1/Membrane-parent-0.1-source-release.zip

Parent directory (including MD5, SHA1 hashes etc.) of the source is:
https://repository.apache.org/content/repositories/orgapachemetamodel-1027/org/apache/metamodel/membrane/Membrane-parent/0.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-1027/

Please vote on releasing this package as Apache MetaModel Membrane 0.1.

The vote is open for 72 hours.

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

Thank you in advance for participating.

Re: MetaModel 5.0.0 announcement, website, twitter. Your turn :-)

[Kasper Sørensen]

Related to upgrade path - I also went through that last night in one of the
bigger projects that depend on MetaModel - DataCleaner. Maybe for someone's
interest to see what kind of updates where needed
https://github.com/datacleaner/DataCleaner/pull/1765 (most of those changes
are trivial, but some require a bit of tweaking).

2017-11-09 11:29 GMT-08:00 Kasper Sørensen :

> There! I had not promoted my staged change to the actual website. Thanks
> for letting me know.
>
> http://metamodel.apache.org should be fine now.
>
> 2017-11-09 11:27 GMT-08:00 Kasper Sørensen  >:
>
>> What! Hmm that's weird, I updated it last night. Must have not pushed the
>> update properly. I'll revisit it.
>>
>> 2017-11-09 5:35 GMT-08:00 Jörg Unbehauen > zig.de>:
>>
>>> Hi,
>>>
>>> great news and many thanks for managing the process. I finally got rid
>>> of the snapshot/RC dependency in my project.
>>>
>>> Just one thing: The website is still points to the old version in: news,
>>> downloads and javadocs.
>>>
>>>
>>> Best, Jörg
>>>
>>>
>>>
>>> Am 09.11.17 um 06:52 schrieb Kasper Sørensen:
>>>
>>> Hi all,
>>>>
>>>> I've updated our website ...
>>>> http://metamodel.apache.org/
>>>>
>>>> ... and Twitter ...
>>>> https://twitter.com/ApacheMetaModel/status/928500067702468609
>>>>
>>>> I hope you will help share the news - MetaModel 5.0.0 is available! :-)
>>>>
>>>> Best regards,
>>>> Kasper
>>>>
>>>>
>>>
>>
>

Re: MetaModel 5.0.0 announcement, website, twitter. Your turn :-)

[Kasper Sørensen]

There! I had not promoted my staged change to the actual website. Thanks
for letting me know.

http://metamodel.apache.org should be fine now.

2017-11-09 11:27 GMT-08:00 Kasper Sørensen :

> What! Hmm that's weird, I updated it last night. Must have not pushed the
> update properly. I'll revisit it.
>
> 2017-11-09 5:35 GMT-08:00 Jörg Unbehauen  leipzig.de>:
>
>> Hi,
>>
>> great news and many thanks for managing the process. I finally got rid of
>> the snapshot/RC dependency in my project.
>>
>> Just one thing: The website is still points to the old version in: news,
>> downloads and javadocs.
>>
>>
>> Best, Jörg
>>
>>
>>
>> Am 09.11.17 um 06:52 schrieb Kasper Sørensen:
>>
>> Hi all,
>>>
>>> I've updated our website ...
>>> http://metamodel.apache.org/
>>>
>>> ... and Twitter ...
>>> https://twitter.com/ApacheMetaModel/status/928500067702468609
>>>
>>> I hope you will help share the news - MetaModel 5.0.0 is available! :-)
>>>
>>> Best regards,
>>> Kasper
>>>
>>>
>>
>

Re: MetaModel 5.0.0 announcement, website, twitter. Your turn :-)

[Kasper Sørensen]

What! Hmm that's weird, I updated it last night. Must have not pushed the
update properly. I'll revisit it.

2017-11-09 5:35 GMT-08:00 Jörg Unbehauen <
unbeha...@informatik.uni-leipzig.de>:

> Hi,
>
> great news and many thanks for managing the process. I finally got rid of
> the snapshot/RC dependency in my project.
>
> Just one thing: The website is still points to the old version in: news,
> downloads and javadocs.
>
>
> Best, Jörg
>
>
>
> Am 09.11.17 um 06:52 schrieb Kasper Sørensen:
>
> Hi all,
>>
>> I've updated our website ...
>> http://metamodel.apache.org/
>>
>> ... and Twitter ...
>> https://twitter.com/ApacheMetaModel/status/928500067702468609
>>
>> I hope you will help share the news - MetaModel 5.0.0 is available! :-)
>>
>> Best regards,
>> Kasper
>>
>>
>

MetaModel 5.0.0 announcement, website, twitter. Your turn :-)

[Kasper Sørensen]

Hi all,

I've updated our website ...
http://metamodel.apache.org/

... and Twitter ...
https://twitter.com/ApacheMetaModel/status/928500067702468609

I hope you will help share the news - MetaModel 5.0.0 is available! :-)

Best regards,
Kasper

[RESULT] [VOTE] Apache MetaModel release 5.0.0

[Kasper Sørensen]

Hi everyone,

I'm happy to be able to tell that the VOTE for releasing Apache MetaModel
5.0.0 has passed with 4 votes (3 binding).

Kasper Sørensen *
David Krause
Alberto Rodriguez *
Dennis Du Krøger *

* - indicates PMC

We also had one -1 vote from Jörg Unbehauen due to the change
(METAMODEL-1165) between the latest RC version and this final 5.0.0
version. However, it was decided that this change is desired and the timing
of the change with this version is appropriate. Thank you however for
voicing your concerns, Jörg.

Thank you to everyone who participated.

I will continue the release process to get the files available for download
asap and update the website probably tomorrow.

Best regards,
Kasper Sørensen


2017-11-03 22:02 GMT-07:00 Kasper Sørensen :

> Hi All,
>
> I suggest releasing MetaModel 5.0.0! Please vote on the following ... This
> is the candidate: Apache Metamodel version 5.0.0.
>
> The Git tag to be voted on is MetaModel-5.0.0:
> https://git-wip-us.apache.org/repos/asf?p=metamodel.git;a=commit;h=
> 2275bab719a3f2d316c49659caa2178a6cc61553
>
> The source artifact to be voted on is:
> http://repository.apache.org/content/repositories/
> orgapachemetamodel-1026/org/apache/metamodel/MetaModel/5.
> 0.0/MetaModel-5.0.0-source-release.zip
>
> Parent directory (including MD5, SHA1 hashes etc.) of the source is:
> http://repository.apache.org/content/repositories/
> orgapachemetamodel-1026/org/apache/metamodel/MetaModel/5.0.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-1026
>
> Please vote on releasing this package as Apache MetaModel 5.0.0.
>
> The vote is open for 72 hours.
>
> [ ] +1 Release this package as Apache MetaModel 5.0.0
> [ ] -1 Do not release this package because ...
>
> Thank you in advance for participating.
>
> Regards,
> Kasper Sørensen
>

Re: [VOTE] Apache MetaModel release 5.0.0

[Kasper Sørensen]

Normally if I'm upgrading a project that I depend on from e.g. 4.x to 5.x,
then I would expect differences and do some testing to make sure everything
in the upgrade fits my bill. But you do have a point of course.

I say we extent the vote for another 24 hours to see if any other PMC
members have anything to add about this concern. I am myself fully OK with
the impact of METAMODEL-1165, and prefer not to hold up the release.

2017-11-06 14:11 GMT-08:00 :

> Hi Kasper,
>
> this feature should be released in 5.0.0 (i am @tomatophantastico on
> github), just the schedule is quite tight.
>
> When i build my project against master (thanks for the great work btw.), i
> had to do some adjustments (i.e. filter tables & dealing with other table
> types) that i did not considered before.
> As this change is not reflected in an API change and affects only a subset
> of datacontexts, this might slip unnoticed and cause confusion afterwards.
>
>
> As i have no knowledge about the other projects using metamodel, this can
> be either an issue, or not.
>
>
> Best, Jörg
>
>
>
>
> Quoting Kasper Sørensen :
>
> Hi Jörg,
>>
>> Thank you for the feedback. But the way I see it there are two
>> counter-arguments to what you're saying ...
>>
>> (1) Being a major release (5.0.0), changing behavior is warranted and
>> clearly signalled, and the time is right to do so now, not in any other
>> kind of release.
>> (2) There is a system property available (metamodel.alias.default.table)
>> which allows one to turn off the feature.
>>
>> Best regards,
>> Kasper
>>
>> 2017-11-06 10:00 GMT-08:00 Jörg Unbehauen <
>> unbeha...@informatik.uni-leipzig.de>:
>>
>> -1
>>>
>>> Sorry for being late, but while i really like METAMODEL-1165 and
>>> appreciate having it shipped with MM 5.0, it changes the behavior without
>>> an API change, so unsuspecting users might run into trouble.
>>>
>>> I suggest to either create an other RC, or turn it off by default.
>>>
>>>
>>>
>>> Best, Jörg
>>>
>>>
>>> Am 06.11.17 um 07:59 schrieb Alberto Rodriguez:
>>>
>>> +1
>>>
>>>>
>>>> 2017-11-06 7:53 GMT+01:00 David Krause :
>>>>
>>>> +1
>>>>
>>>>>
>>>>> Freundliche Grüße
>>>>> David
>>>>>
>>>>>
>>>>>
>>>
>
>
>

Re: [VOTE] Apache MetaModel release 5.0.0

[Kasper Sørensen]

Hi Jörg,

Thank you for the feedback. But the way I see it there are two
counter-arguments to what you're saying ...

(1) Being a major release (5.0.0), changing behavior is warranted and
clearly signalled, and the time is right to do so now, not in any other
kind of release.
(2) There is a system property available (metamodel.alias.default.table)
which allows one to turn off the feature.

Best regards,
Kasper

2017-11-06 10:00 GMT-08:00 Jörg Unbehauen <
unbeha...@informatik.uni-leipzig.de>:

> -1
>
> Sorry for being late, but while i really like METAMODEL-1165 and
> appreciate having it shipped with MM 5.0, it changes the behavior without
> an API change, so unsuspecting users might run into trouble.
>
> I suggest to either create an other RC, or turn it off by default.
>
>
>
> Best, Jörg
>
>
> Am 06.11.17 um 07:59 schrieb Alberto Rodriguez:
>
> +1
>>
>> 2017-11-06 7:53 GMT+01:00 David Krause :
>>
>> +1
>>>
>>> Freundliche Grüße
>>> David
>>>
>>>
>