Thanks for testing Michael! I just tried testing using docker on a VM
with a lot of RAM and was not able to reproduce the issue. The Phoenix
image I am using is boostport/hbase-phoenix-all-in-one:2.0-5.0.
I am going to cancel the vote and roll a new RC as I neglected to update
the dockerfile so that Go modules work correctly. This meant that if
tests are executed using docker-compose, they will not run correctly. My
apologies for the oversight.
I will release a rc1 for voting soon.
Francis
On 31/08/2018 4:14 AM, Michael Mior wrote:
Yeah, I assumed it probably wasn't an Avatica issue. I maintain my +1.
--
Michael Mior
mm...@apache.org
Le jeu. 30 août 2018 à 11:54, Josh Elser <els...@apache.org> a écrit :
That looks like an issue with Phoenix+Tephra rather than with the Go
driver. The latest release of Tephra (going through IPMC vote now)
should be fixing that.
Essentially, Tephra had an issue where it was trying to get a random
port and then bind it in two separate steps. Sometimes, some other
process would come along and bind that port before Tephra would, and
then the Tephra service wouldn't start (and you'd get that message).
On 8/30/18 11:41 AM, Michael Mior wrote:
Thanks Francis. I thought I recalled Docker being an option but I missed
in
the documentation. I get the failure message below. Other than that,
tests
pass.
calcite-avatica-go_1 | --- FAIL: TestPhoenixOptimisticConcurrency
(46.12s)
calcite-avatica-go_1 | driver_test.go:95: error on exec CREATE TABLE
test15356434203761149952 (
calcite-avatica-go_1 | id INTEGER PRIMARY KEY, calcite-avatica-go_1 | msg
VARCHAR,
calcite-avatica-go_1 | version INTEGER
calcite-avatica-go_1 | ) TRANSACTIONAL=true: An error was encountered
while
processing your request: RuntimeException:
org.apache.phoenix.shaded.org.apache.thrift.TException: Unable to
discover
transaction service. -> TException: Unable to discover transaction
service
--
Michael Mior
mm...@apache.org
Le mer. 29 août 2018 à 20:44, Francis Chuang <francischu...@apache.org>
a
écrit :
Hey Michael,
If you have docker and docker-compose installed on your machine, you can
run: "docker-compose up --build" from the root of the directory. This
will automatically run all tests (around 5 minutes).
Francis
On 30/08/2018 9:55 AM, Michael Mior wrote:
+1 (binding)
Checked hash and signature and compiled. Did not run tests since I
don't
currently have Avatica set up on my new dev box.
--
Michael Mior
mm...@apache.org
Le mer. 29 août 2018 à 19:22, Francis Chuang <francischu...@apache.org
a
écrit :
Hi all,
I have created a release for Apache Calcite Avatica Go 3.1.0, release
candidate 0.
The release notes are available here:
https://github.com/apache/calcite-avatica-go/blob/master/site/go_history.md
The commit to be voted on:
http://git-wip-us.apache.org/repos/asf/calcite-avatica-go/commit/d328101ff81f0dc51db8dc5c62b4205a4cf0a48d
The hash is d328101ff81f0dc51db8dc5c62b4205a4cf0a48d
The artifacts to be voted on are located here:
https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-avatica-go-3.1.0-rc0/
The hashes of the artifacts are as follows:
src.tar.gz.sha256 497418D1 A017C97F 121CFD21 6DB1FE6B F0D536F6
CB32570C
232D59D0 B479CFA7
Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/francischuang.asc
Instructions for running the test suite is located here:
https://github.com/apache/calcite-avatica-go/blob/master/site/develop/avatica-go.md#testing
Please vote on releasing this package as Apache Calcite Avatica Go
3.1.0.
The vote is open for the next 72 hours and passes if a majority of
at least three +1 PMC votes are cast.
[ ] +1 Release this package as Apache Calcite Avatica Go 3.0.0
[ ] 0 I don't feel strongly about it, but I'm okay with the release
[ ] -1 Do not release this package because...
Here is my vote:
+1 (binding)
Francis
