[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [DISCUSS] Towards Avatica 1.12.0

Question for Josh and others who have built Avatica releases before:

I am currently building a release using the dry run instructions here:

In particular, there is a command to update AVATICA_VERSION in the dockerhub/Dockerfile file to $version-SNAPSHOT.

I then executed: `mvn -DdryRun=true -DreleaseVersion=1.12.0 -DdevelopmentVersion=1.13.0-SNAPSHOT -Dtag=avatica-1.12.0-rc0 -Papache-release${asf.username} release:prepare`.

This creates a catch-22 situation:
- Maven complains that there are modified files in the repository and fails.
- If I do not update the docker file, maven fails with "Expected Avatica version of 1.12.0-SNAPSHOT but got 1.12.0"

How did you guys build the previous releases using dry-run?

Second question: Am I correct to assume that X2.Y2.Z2 in the command above would be the next version (1.13.0) and X.Y.Z would be the version I am building a release for (1.12.0)?


On 5/06/2018 2:36 AM, Josh Elser wrote:
Yay! Thanks Michael and Julian for helping Francis out :)

On 6/2/18 11:01 PM, Francis Chuang wrote:
Thanks, Michael! I just had a go again and the "Send mail for this update" checkbox is now visible.

On 3/06/2018 12:08 PM, Michael Mior wrote:
I didn't realize you needed to be an administrator for this. Anyway, I just
added you, so you should be set now.
Michael Mior

Le sam. 2 juin 2018 à 21:44, Francis Chuang <francischuang@xxxxxxxxxx> a
écrit :

I just had a look at using the "bulk change" functionality. I chose
"transition" as the operation and "close issue" as the operation type. I can see that I can add a comment for the bulk change, but there is still
no check box for "Send mail for this update". Some googling suggests
that I need to become a project administrator:

Is this something I can request via INFRA or is there a formalized process?


On 3/06/2018 1:37 AM, Julian Hyde wrote:
That checkbox only exists when you are using Jira’s “bulk change”

On Jun 2, 2018, at 03:00, Francis Chuang <francischuang@xxxxxxxxxx>
This is my summary for the week ending 1 June 2018:
- Many thanks to Julian, Josh, Karan, Sergey and Haohui for
contributing, reviewing and merging CALCITE-2022, CALCITE-1884, CALCITE
2303, CALCITE-2284.
- Most of the PRs on Github in my initial list has been resolved,
except the following:
      - CALCITE-2219 (Laurent):
      - CALCITE-2322 (Kevin Minder):
- Additional issue added to list:
      - CALCITE-2350: Cannot shade Avatica with Guava 21.0 or higher (In
progress, Julian)
Are there any other issues people would like to work on for the 1.12
I am updating the release history as we go. See here for the current
Question for Josh: I was reviewing the documentation for publishing a
It says to close all the issues resolved in this release during the
publishing process. In particular, it says to uncheck "send mail for this update" when closing those issues. I just had a look in JIRA and I do not
have this option to not send mail when closing out those issues.

On 29/05/2018 6:37 PM, Francis Chuang wrote:
Avatica 1.11.0 was released on March 6 (more than 3 months ago). We
should discuss the next release (1.12.0).
The current consensus is to have a release in around 2 weeks.

The JIRA tracking the release is CALCITE-2330 [1].

As the release cycle for this would is a bit short, I think it would
be a good idea to focus our efforts on low hanging fruit, bugs and
features/enhancements that won't take a lot of time (unless someone is able
to dedicate significant resources).
Personally, I would love to see the following fixed:

CALCITE-1951 [2]: Avatica with HSQLDB loses fractional seconds. Kevin
and Josh has done some investigation, so I hope this is a relatively simple
fix. Test is here:
CALCITE-2250 [3]: Avatica with HSQLDB hangs when using multiple
transactions. Kevin has done some investigation and the issue is easily
CALCITE-2219 [4]: Acvtica Connection/Statement/ResultSet don't throw
if resource is closed. Work has started:
CALCITE-2333 [5]: Stop releasing ZIPs. Assigned to myself.

Nice to haves:

CALCITE-1049 [7]: SQLException not correctly propagated. This is
preventing clients from taking different actions when they encounter
different SQLExceptions. However, the fix might not be too simple.
I'd also like to use this release to clean up the PRs on Github:

CALCITE-1884 [8]: DateTimeUtils produces incorrect results for days
before Gregorian cutovers. The PR is almost a year old. Can someone please take a look at this so we can merge or close it?
CALCITE-2294 [9]: Allow customization for plugging in new
authentication mechanisms. Is active and will be in this release:
CALCITE-2322 [10]: Add fetch size support to connection URL and JDBC
state. Seems to be implemented, can someone please review?
CALCITE-2303 [11]: Support extraction of microseconds, milliseconds,
epoch, isodow, isoyear and decade. Can someone please review?
Are there any other features or bugs people would like implemented or