[jira] [Commented] (JDO-652) Provision of a typesafe refactor-friendly query capability for JDOQL

2019-03-06 Thread Andy Jefferson (JIRA) 


[ 
https://issues.apache.org/jira/browse/JDO-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16786479#comment-16786479
 ] 

Andy Jefferson commented on JDO-652:


See https://github.com/datanucleus/datanucleus-api-jdo/issues/97

> Provision of a typesafe refactor-friendly query capability for JDOQL
> 
>
> Key: JDO-652
> URL: https://issues.apache.org/jira/browse/JDO-652
> Project: JDO
>  Issue Type: New Feature
>  Components: api, specification, tck
>Reporter: Andy Jefferson
>Assignee: Michael Bouschen
>Priority: Major
> Fix For: JDO 3.2
>
> Attachments: JDO-652-api-ifTheElse.txt, JDO-652-api-patch-Andy.txt, 
> JDO-652-patch4.txt, typesafe.patch, typesafe_manifest.patch
>
>
> There are various querying capabilities of this type around. JPA2 has its 
> Criteria query API. Third party solutions like QueryDSL also exist, in its 
> case providing a JDOQL implementation (as well as JPQL, and HQL). We should 
> seriously consider introducing something along these lines in the JDO2.4 
> timeframe. 
> There is a comparison of JPA Criteria with QueryDSL over at 
> http://source.mysema.com/forum/mvnforum/viewthread_thread,49



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Minutes: JDO TCK Conference Call Wednesday March 6 at 9:30 AM Pacific Standard Time (PST)

2019-03-06 Thread Craig Russell 
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell

Next meeting: Thursday March 14 10:30 AM PDT Daylight Savings Time in US!

Agenda:

1. Moin Wiki is deprecated - closing in 3 months - please migrate to Confluence

Andy suggests dropping the wiki in favor of using a newly designed web site. 
Seems to be a good idea.

AI Craig: ask infra how to use github for sources for our official web 
presence. Perhaps keeping the source for the site in gitbox/github and then 
deploying to db.apache.org/jdo would work. An alternative is to have a 
documentation directory in the repo where we keep information.

2. New JIRA JDO-778 "Adding overloaded methods to JDOQLTypedQuery to create a 
correlated subquery" https://issues.apache.org/jira/browse/JDO-778

There is no way to implement a correlated subquery using relationship fields in 
the from clause with the current implementation of JDOQLTypedQuery. AI Everyone 
please review the proposed API change.

3. JIRA JDO-776 "Exception on Query.close()" 
https://issues.apache.org/jira/browse/JDO-776

Resolved: Not A Problem

4. JDO-770 "Switch from svn to git" 
https://issues.apache.org/jira/browse/JDO-770

Andy suggests using markdown and a simple git repository for the web presence.

Andy notices that github sends commit messages to jdo-dev@. AI Craig: can we 
send commits to jdo-commits@ ?

5. JDO-652 "Provision of a typesafe refactor-friendly query capability for 
JDOQL" https://issues.apache.org/jira/browse/JDO-652

AI All: please review the branch jdo-652

6. Issues with Fix Version JDO-3.2 

7. Release Policy Updates
8. JDO 3.1: Need to go through change lists in JIRA for 3.1 RC1 and 3.1 to 
prepare JCP Change Log
9. Other issues

Action Items from weeks past:
[Jan 10 2019] AI Craig send email to dev to discuss timing of git changeover.
[Jan 18 2018] AI Craig talk to some git/svn Apache experts to get some advice. 
Specifically, how to preserve the svn history, how to manage the web site.
[Oct 30 2015] AI Craig: File a maintenance review with JCP
[Apr 17 2015] AI Craig: Oracle spec page on JDO need to be updated once the JCP 
Maintenance Release for JDO 3.1 is published
[Oct 17 2014] AI Matthew any updates for "Modify specification to address NoSQL 
datastores": https://issues.apache.org/jira/browse/JDO-651?
[Feb 28 2014] AI Everyone: take a look at 
https://issues.apache.org/jira/browse/JDO-712
[Feb 28 2014] AI Everyone: take a look at 
https://issues.apache.org/jira/browse/JDO-625
[Dec 13 2013] AI Craig file a JIRA for java.sql.Blob and java.sql.Clob as 
persistent field types
[Aug 24 2012] AI Craig update the JIRAs JDO-689 JDO-690 and JDO-692 about 
JDOHelper methods. In process.

-- 
Michael Bouschen
akquinet tech@spree GmbH
Bülowstraße 66 • D-10783 Berlin
Tel:   +49 30 235520-33
Fax:  +49 30 217520-12

E-Mail: michael.bousc...@akquinet.de 
Web:   www.akquinet.de 

Geschäftsführung: Martin Weber, Dr. Torsten Fink
Amtsgericht Berlin HRB 86780 • USt.-Id. Nr.: DE 225 964 680

[Facebook]   [XING]
  [G+]
 
[LinkedIn]   [Twitter]


Craig L Russell
Secretary, Apache Software Foundation
c...@apache.org  http://db.apache.org/jdo

[jira] [Resolved] (JDO-776) Exception on Query.close()

2019-03-06 Thread Craig L Russell (JIRA) 


 [ 
https://issues.apache.org/jira/browse/JDO-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Craig L Russell resolved JDO-776.
-
Resolution: Not A Problem

To use try-with-resources the interface needs to implement AutoCloseable which 
throws Exception on the close() method. 

> Exception on Query.close()
> --
>
> Key: JDO-776
> URL: https://issues.apache.org/jira/browse/JDO-776
> Project: JDO
>  Issue Type: Improvement
>  Components: api
>Affects Versions: JDO 3.2
>Reporter: Steve Springett
>Priority: Minor
>
> The Query interface has an exception thrown on the close() method. This 
> prevents elegant use of try-with-resource and requires more complex cases 
> instead, such as try within try, or try-with-resource with catch. In both 
> cases, the code gets rather ugly when using try-with-resource.
>  
> The closeAll() method however, does not throw an exception which allows for 
> simpler, more elegant code. Users should be encouraged to use modern language 
> constructs, but in the case of the Query interface, I prefer not to, and use 
> closeAll instead.
>  
> Propose: Remove the Exception from Query.close(). If an exception is thrown 
> while closing it, ignore it.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (JDO-778) Adding overloaded methods to JDOQLTypedQuery to create a correlated subquery

2019-03-06 Thread Michael Bouschen (JIRA) 


 [ 
https://issues.apache.org/jira/browse/JDO-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen updated JDO-778:
-
Description: 
I propose to add the following overloaded subquery methods to support 
correlated subqueries using a relationship field of the from clause of the 
subquery, e.g.

{{select firstname from org.apache.jdo.tck.pc.company.Employee }}
{{  where this.weeklyhours > }}
{{     (select AVG(e.weeklyhours) from this.department.employees e where 
e.manager == this.manager)}}

{{<{color:#20999d}E{color}> JDOQLTypedSubquery<{color:#20999d}E{color}> 
subquery(CollectionExpression, 
{color:#20999d}E{color}> candidateCollection, String candidateAlias);}}
 {{<{color:#20999d}E{color}> JDOQLTypedSubquery<{color:#20999d}E{color}> 
subquery(ListExpression, {color:#20999d}E{color}> 
candidateList, String candidateAlias);}}
 {{<{color:#20999d}K{color}, {color:#20999d}V{color}> 
JDOQLTypedSubquery> 
subquery(MapExpression, 
{color:#20999d}K{color}, {color:#20999d}V{color}> candidateMap, String 
candidateAlias);}}

  was:
I propose to add the following overloaded subquery methods to support 
correlated subqueries using a relationship field of the from clause of the 
subquery, e.g.

{{select firstname from org.apache.jdo.tck.pc.company.Employee }}
{{ where this.weeklyhours > }}
{{    (select AVG(e.weeklyhours) from this.department.employees e where 
e.manager == this.manager)}}

{{<{color:#20999d}E{color}> JDOQLTypedSubquery<{color:#20999d}E{color}> 
subquery(CollectionExpression, 
{color:#20999d}E{color}> candidateCollection, String candidateAlias);}}
 {{<{color:#20999d}E{color}> JDOQLTypedSubquery<{color:#20999d}E{color}> 
subquery(ListExpression, {color:#20999d}E{color}> 
candidateList, String candidateAlias);}}
 {{<{color:#20999d}K{color}, {color:#20999d}V{color}> 
JDOQLTypedSubquery> 
subquery(MapExpression, 
{color:#20999d}K{color}, {color:#20999d}V{color}> candidateMap, String 
candidateAlias);}}


> Adding overloaded methods to JDOQLTypedQuery to create a correlated subquery 
> -
>
> Key: JDO-778
> URL: https://issues.apache.org/jira/browse/JDO-778
> Project: JDO
>  Issue Type: Improvement
>  Components: api
>Affects Versions: JDO 3.1
>Reporter: Michael Bouschen
>Priority: Critical
> Fix For: JDO 3.2
>
>
> I propose to add the following overloaded subquery methods to support 
> correlated subqueries using a relationship field of the from clause of the 
> subquery, e.g.
> {{select firstname from org.apache.jdo.tck.pc.company.Employee }}
> {{  where this.weeklyhours > }}
> {{     (select AVG(e.weeklyhours) from this.department.employees e where 
> e.manager == this.manager)}}
> {{<{color:#20999d}E{color}> JDOQLTypedSubquery<{color:#20999d}E{color}> 
> subquery(CollectionExpression, 
> {color:#20999d}E{color}> candidateCollection, String candidateAlias);}}
>  {{<{color:#20999d}E{color}> JDOQLTypedSubquery<{color:#20999d}E{color}> 
> subquery(ListExpression, 
> {color:#20999d}E{color}> candidateList, String candidateAlias);}}
>  {{<{color:#20999d}K{color}, {color:#20999d}V{color}> 
> JDOQLTypedSubquery {color:#20999d}V{color}>> subquery(MapExpression {color:#20999d}V{color}>, {color:#20999d}K{color}, {color:#20999d}V{color}> 
> candidateMap, String candidateAlias);}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (JDO-778) Adding overloaded methods to JDOQLTypedQuery to create a correlated subquery

2019-03-06 Thread Michael Bouschen (JIRA) 


 [ 
https://issues.apache.org/jira/browse/JDO-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen updated JDO-778:
-
Description: 
I propose to add the following overloaded subquery methods to support 
correlated subqueries using a relationship field of the from clause of the 
subquery, e.g.

select firstname from org.apache.jdo.tck.pc.company.Employee 
   where this.weeklyhours > 
  (select AVG(e.weeklyhours) from this.department.employees e where 
e.manager == this.manager)

{{<{color:#20999d}E{color}> JDOQLTypedSubquery<{color:#20999d}E{color}> 
subquery(CollectionExpression, 
{color:#20999d}E{color}> candidateCollection, String candidateAlias);}}
 {{<{color:#20999d}E{color}> JDOQLTypedSubquery<{color:#20999d}E{color}> 
subquery(ListExpression, {color:#20999d}E{color}> 
candidateList, String candidateAlias);}}
 {{<{color:#20999d}K{color}, {color:#20999d}V{color}> 
JDOQLTypedSubquery> 
subquery(MapExpression, 
{color:#20999d}K{color}, {color:#20999d}V{color}> candidateMap, String 
candidateAlias);}}

  was:
I propose to add the following overloaded subquery methods to support 
correlated subqueries using a relationship field of the from clause of the 
subquery, e.g.

{{select firstname from org.apache.jdo.tck.pc.company.Employee }}
{{  where this.weeklyhours > }}
{{     (select AVG(e.weeklyhours) from this.department.employees e where 
e.manager == this.manager)}}

{{<{color:#20999d}E{color}> JDOQLTypedSubquery<{color:#20999d}E{color}> 
subquery(CollectionExpression, 
{color:#20999d}E{color}> candidateCollection, String candidateAlias);}}
 {{<{color:#20999d}E{color}> JDOQLTypedSubquery<{color:#20999d}E{color}> 
subquery(ListExpression, {color:#20999d}E{color}> 
candidateList, String candidateAlias);}}
 {{<{color:#20999d}K{color}, {color:#20999d}V{color}> 
JDOQLTypedSubquery> 
subquery(MapExpression, 
{color:#20999d}K{color}, {color:#20999d}V{color}> candidateMap, String 
candidateAlias);}}


> Adding overloaded methods to JDOQLTypedQuery to create a correlated subquery 
> -
>
> Key: JDO-778
> URL: https://issues.apache.org/jira/browse/JDO-778
> Project: JDO
>  Issue Type: Improvement
>  Components: api
>Affects Versions: JDO 3.1
>Reporter: Michael Bouschen
>Priority: Critical
> Fix For: JDO 3.2
>
>
> I propose to add the following overloaded subquery methods to support 
> correlated subqueries using a relationship field of the from clause of the 
> subquery, e.g.
> select firstname from org.apache.jdo.tck.pc.company.Employee 
>    where this.weeklyhours > 
>   (select AVG(e.weeklyhours) from this.department.employees e where 
> e.manager == this.manager)
> {{<{color:#20999d}E{color}> JDOQLTypedSubquery<{color:#20999d}E{color}> 
> subquery(CollectionExpression, 
> {color:#20999d}E{color}> candidateCollection, String candidateAlias);}}
>  {{<{color:#20999d}E{color}> JDOQLTypedSubquery<{color:#20999d}E{color}> 
> subquery(ListExpression, 
> {color:#20999d}E{color}> candidateList, String candidateAlias);}}
>  {{<{color:#20999d}K{color}, {color:#20999d}V{color}> 
> JDOQLTypedSubquery {color:#20999d}V{color}>> subquery(MapExpression {color:#20999d}V{color}>, {color:#20999d}K{color}, {color:#20999d}V{color}> 
> candidateMap, String candidateAlias);}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (JDO-778) Adding overloaded methods to JDOQLTypedQuery to create a correlated subquery

2019-03-06 Thread Michael Bouschen (JIRA) 


 [ 
https://issues.apache.org/jira/browse/JDO-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen updated JDO-778:
-
Description: 
I propose to add the following overloaded subquery methods to support 
correlated subqueries using a relationship field of the from clause of the 
subquery, e.g.

{{select firstname from org.apache.jdo.tck.pc.company.Employee }}
{{ where this.weeklyhours > }}
{{    (select AVG(e.weeklyhours) from this.department.employees e where 
e.manager == this.manager)}}

{{<{color:#20999d}E{color}> JDOQLTypedSubquery<{color:#20999d}E{color}> 
subquery(CollectionExpression, 
{color:#20999d}E{color}> candidateCollection, String candidateAlias);}}
 {{<{color:#20999d}E{color}> JDOQLTypedSubquery<{color:#20999d}E{color}> 
subquery(ListExpression, {color:#20999d}E{color}> 
candidateList, String candidateAlias);}}
 {{<{color:#20999d}K{color}, {color:#20999d}V{color}> 
JDOQLTypedSubquery> 
subquery(MapExpression, 
{color:#20999d}K{color}, {color:#20999d}V{color}> candidateMap, String 
candidateAlias);}}

  was:
I propose to add the following overloaded subquery methods to support 
correlated subqueries using a relationship field of the from clause of the 
subquery, e.g.

select firstname from org.apache.jdo.tck.pc.company.Employee 
where this.weeklyhours > 
   (select AVG(e.weeklyhours) from this.department.employees e where e.manager 
== this.manager)

{{<{color:#20999d}E{color}> JDOQLTypedSubquery<{color:#20999d}E{color}> 
subquery(CollectionExpression, 
{color:#20999d}E{color}> candidateCollection, String candidateAlias);}}
 {{<{color:#20999d}E{color}> JDOQLTypedSubquery<{color:#20999d}E{color}> 
subquery(ListExpression, {color:#20999d}E{color}> 
candidateList, String candidateAlias);}}
 {{<{color:#20999d}K{color}, {color:#20999d}V{color}> 
JDOQLTypedSubquery> 
subquery(MapExpression, 
{color:#20999d}K{color}, {color:#20999d}V{color}> candidateMap, String 
candidateAlias);}}


> Adding overloaded methods to JDOQLTypedQuery to create a correlated subquery 
> -
>
> Key: JDO-778
> URL: https://issues.apache.org/jira/browse/JDO-778
> Project: JDO
>  Issue Type: Improvement
>  Components: api
>Affects Versions: JDO 3.1
>Reporter: Michael Bouschen
>Priority: Critical
> Fix For: JDO 3.2
>
>
> I propose to add the following overloaded subquery methods to support 
> correlated subqueries using a relationship field of the from clause of the 
> subquery, e.g.
> {{select firstname from org.apache.jdo.tck.pc.company.Employee }}
> {{ where this.weeklyhours > }}
> {{    (select AVG(e.weeklyhours) from this.department.employees e where 
> e.manager == this.manager)}}
> {{<{color:#20999d}E{color}> JDOQLTypedSubquery<{color:#20999d}E{color}> 
> subquery(CollectionExpression, 
> {color:#20999d}E{color}> candidateCollection, String candidateAlias);}}
>  {{<{color:#20999d}E{color}> JDOQLTypedSubquery<{color:#20999d}E{color}> 
> subquery(ListExpression, 
> {color:#20999d}E{color}> candidateList, String candidateAlias);}}
>  {{<{color:#20999d}K{color}, {color:#20999d}V{color}> 
> JDOQLTypedSubquery {color:#20999d}V{color}>> subquery(MapExpression {color:#20999d}V{color}>, {color:#20999d}K{color}, {color:#20999d}V{color}> 
> candidateMap, String candidateAlias);}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (JDO-778) Adding overloaded methods to JDOQLTypedQuery to create a correlated subquery

2019-03-06 Thread Michael Bouschen (JIRA) 


 [ 
https://issues.apache.org/jira/browse/JDO-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen updated JDO-778:
-
Description: 
I propose to add the following overloaded subquery methods to support 
correlated subqueries using a relationship field of the from clause of the 
subquery, e.g.

select firstname from org.apache.jdo.tck.pc.company.Employee 
where this.weeklyhours > 
   (select AVG(e.weeklyhours) from this.department.employees e where e.manager 
== this.manager)

{{<{color:#20999d}E{color}> JDOQLTypedSubquery<{color:#20999d}E{color}> 
subquery(CollectionExpression, 
{color:#20999d}E{color}> candidateCollection, String candidateAlias);}}
 {{<{color:#20999d}E{color}> JDOQLTypedSubquery<{color:#20999d}E{color}> 
subquery(ListExpression, {color:#20999d}E{color}> 
candidateList, String candidateAlias);}}
 {{<{color:#20999d}K{color}, {color:#20999d}V{color}> 
JDOQLTypedSubquery> 
subquery(MapExpression, 
{color:#20999d}K{color}, {color:#20999d}V{color}> candidateMap, String 
candidateAlias);}}

  was:
I prosed to add the following overloaded subquery methods to support correlated 
subqueries:

{{<{color:#20999d}E{color}> JDOQLTypedSubquery<{color:#20999d}E{color}> 
subquery(CollectionExpression, 
{color:#20999d}E{color}> candidateCollection, String candidateAlias);}}
{{<{color:#20999d}E{color}> JDOQLTypedSubquery<{color:#20999d}E{color}> 
subquery(ListExpression, {color:#20999d}E{color}> 
candidateList, String candidateAlias);}}
{{<{color:#20999d}K{color}, {color:#20999d}V{color}> 
JDOQLTypedSubquery> 
subquery(MapExpression, 
{color:#20999d}K{color}, {color:#20999d}V{color}> candidateMap, String 
candidateAlias);}}


> Adding overloaded methods to JDOQLTypedQuery to create a correlated subquery 
> -
>
> Key: JDO-778
> URL: https://issues.apache.org/jira/browse/JDO-778
> Project: JDO
>  Issue Type: Improvement
>  Components: api
>Affects Versions: JDO 3.1
>Reporter: Michael Bouschen
>Priority: Critical
> Fix For: JDO 3.2
>
>
> I propose to add the following overloaded subquery methods to support 
> correlated subqueries using a relationship field of the from clause of the 
> subquery, e.g.
> select firstname from org.apache.jdo.tck.pc.company.Employee 
> where this.weeklyhours > 
>    (select AVG(e.weeklyhours) from this.department.employees e where 
> e.manager == this.manager)
> {{<{color:#20999d}E{color}> JDOQLTypedSubquery<{color:#20999d}E{color}> 
> subquery(CollectionExpression, 
> {color:#20999d}E{color}> candidateCollection, String candidateAlias);}}
>  {{<{color:#20999d}E{color}> JDOQLTypedSubquery<{color:#20999d}E{color}> 
> subquery(ListExpression, 
> {color:#20999d}E{color}> candidateList, String candidateAlias);}}
>  {{<{color:#20999d}K{color}, {color:#20999d}V{color}> 
> JDOQLTypedSubquery {color:#20999d}V{color}>> subquery(MapExpression {color:#20999d}V{color}>, {color:#20999d}K{color}, {color:#20999d}V{color}> 
> candidateMap, String candidateAlias);}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (JDO-652) Provision of a typesafe refactor-friendly query capability for JDOQL

2019-03-06 Thread Michael Bouschen (JIRA) 


[ 
https://issues.apache.org/jira/browse/JDO-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16785906#comment-16785906
 ] 

Michael Bouschen commented on JDO-652:
--

@[~andy]:

The tck class SampleQueries include all the sample queries from chapter "14.10 
Examples" of the spec.

I started to implement a JDOQLTypedQuery version of all the sample queries. But 
I ran into issues for three queries:

testQuery15f and testQuery16f both fail with the message "Cannot call 
executeResultList method when query has result unset. Call executeList 
instead.". Both queries try to store the result into a warpper class, but I hve 
no idea how to specify this with an JDOQLTypedQuery. 

testQuery19f uses a correlated subquery and I think we need an API extension 
for this, see JDO-778.

Please take a look at branch JDO-652 on github to see my current version of 
class SampleQueries. Here the link: 
https://github.com/apache/db-jdo/blob/JDO-652/tck/src/main/java/org/apache/jdo/tck/query/api/SampleQueries.java

> Provision of a typesafe refactor-friendly query capability for JDOQL
> 
>
> Key: JDO-652
> URL: https://issues.apache.org/jira/browse/JDO-652
> Project: JDO
>  Issue Type: New Feature
>  Components: api, specification, tck
>Reporter: Andy Jefferson
>Assignee: Michael Bouschen
>Priority: Major
> Fix For: JDO 3.2
>
> Attachments: JDO-652-api-ifTheElse.txt, JDO-652-api-patch-Andy.txt, 
> JDO-652-patch4.txt, typesafe.patch, typesafe_manifest.patch
>
>
> There are various querying capabilities of this type around. JPA2 has its 
> Criteria query API. Third party solutions like QueryDSL also exist, in its 
> case providing a JDOQL implementation (as well as JPQL, and HQL). We should 
> seriously consider introducing something along these lines in the JDO2.4 
> timeframe. 
> There is a comparison of JPA Criteria with QueryDSL over at 
> http://source.mysema.com/forum/mvnforum/viewthread_thread,49



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

4 Apache Events in 2019: DC Roadshow soon; next up Chicago, Las Vegas, and Berlin!

2019-03-06 Thread Rich Bowen 
Dear Apache Enthusiast,

(You’re receiving this because you are subscribed to one or more user
mailing lists for an Apache Software Foundation project.)

TL;DR:
 * Apache Roadshow DC is in 3 weeks. Register now at
https://apachecon.com/usroadshowdc19/
 * Registration for Apache Roadshow Chicago is open.
http://apachecon.com/chiroadshow19
 * The CFP for ApacheCon North America is now open.
https://apachecon.com/acna19
 * Save the date: ApacheCon Europe will be held in Berlin, October 22nd
through 24th.  https://apachecon.com/aceu19


Registration is open for two Apache Roadshows; these are smaller events
with a more focused program and regional community engagement:

Our Roadshow event in Washington DC takes place in under three weeks, on
March 25th. We’ll be hosting a day-long event at the Fairfax campus of
George Mason University. The roadshow is a full day of technical talks
(two tracks) and an open source job fair featuring AWS, Bloomberg, dito,
GridGain, Linode, and Security University. More details about the
program, the job fair, and to register, visit
https://apachecon.com/usroadshowdc19/

Apache Roadshow Chicago will be held May 13-14th at a number of venues
in Chicago’s Logan Square neighborhood. This event will feature sessions
in AdTech, FinTech and Insurance, startups, “Made in Chicago”, Project
Shark Tank (innovations from the Apache Incubator), community diversity,
and more. It’s a great way to learn about various Apache projects “at
work” while playing at a brewery, a beercade, and a neighborhood bar.
Sign up today at https://www.apachecon.com/chiroadshow19/

We’re delighted to announce that the Call for Presentations (CFP) is now
open for ApacheCon North America in Las Vegas, September 9-13th! As the
official conference series of the ASF, ApacheCon North America will
feature over a dozen Apache project summits, including Cassandra,
Cloudstack, Tomcat, Traffic Control, and more. We’re looking for talks
in a wide variety of categories -- anything related to ASF projects and
the Apache development process. The CFP closes at midnight on May 26th.
In addition, the ASF will be celebrating its 20th Anniversary during the
event. For more details and to submit a proposal for the CFP, visit
https://apachecon.com/acna19/ . Registration will be opening soon.

Be sure to mark your calendars for ApacheCon Europe, which will be held
in Berlin, October 22-24th at the KulturBrauerei, a landmark of Berlin's
industrial history. In addition to innovative content from our projects,
we are collaborating with the Open Source Design community
(https://opensourcedesign.net/) to offer a track on design this year.
The CFP and registration will open soon at https://apachecon.com/aceu19/ .

Sponsorship opportunities are available for all events, with details
listed on each event’s site at http://apachecon.com/.

We look forward to seeing you!

Rich, for the ApacheCon Planners
@apachecon