in the CALCITE
project while I'm at it.
[1]
https://github.com/apache/calcite/blob/master/avatica/core/src/main/java/org/apache/calcite/avatica/remote/TypedValue.java#L480
F21 wrote:
Sure thing! In the mean time, can you answer my question regarding
whether setting the type to JAVA_SQL_TIMESTAMP
MITIVE_FOO and FOO (there are a few variants of this).
The difference between Long and BigInteger would be the resulting Java
type created for the value (a Long or a BigInteger). Sorry if this is
cyclic logic :)
Yes, the JAVA_* types are used to support the array of
date/time/datetime data types.
F21
in TypedValue is serialized into that message (as it
isn't necessarily obvious how the code expects it).
Want to file a JIRA issue and assign it to me?
F21 wrote:
Hey Josh,
That was a great explanation, thanks! And yes, I am using protobufs. :)
So in the case of a date time, should I set
(as it
isn't necessarily obvious how the code expects it).
Want to file a JIRA issue and assign it to me?
F21 wrote:
Hey Josh,
That was a great explanation, thanks! And yes, I am using protobufs. :)
So in the case of a date time, should I set the Rep to
JAVA_SQL_TIMESTAMP and set
The protobuf documentation for avatica says we can send a map along with
the connection id when using an OpenConnectionRequest:
https://calcite.apache.org/docs/avatica_protobuf_reference.html#openconnectionrequest
Is there a list of keys that can go into the map? Perhaps this should be
better
tions (see
PhoenixRuntime.java).
Thanks,
James
[1]
https://docs.oracle.com/javase/7/docs/api/java/sql/DriverManager.html#getConnection(java.lang.String,%20java.util.Properties)
On Mon, Apr 11, 2016 at 10:46 PM, F21 <f21.gro...@gmail.com> wrote:
The protobuf documentation for avatica says
I need to send some TypedValues to the avatica server (phoenix query
server) when executing a statement.
According to
https://calcite.apache.org/docs/avatica_protobuf_reference.html#typedvalue,
I need to set a Type for each value. I noticed that the list of Reps
here
://phoenix.apache.org/transactions.html and let us know if
it doesn't answer your questions.
Thanks,
James
On Sat, Mar 26, 2016 at 10:00 PM, F21 <f21.gro...@gmail.com> wrote:
Hi guys,
As I posted on the Phoenix list a few days ago, I am working on a golang
client for the phoenix query service (whic
through either a commit or
rollback.
On Sat, Mar 26, 2016 at 11:08 PM, F21<f21.gro...@gmail.com> wrote:
Hi James,
Thanks for the quick reply. The docs does talk about how to use
transactions with phoenix, but doesn't seem to answer my questions
regarding implementing transactions for a p
by
the server operates. If it's not returning the offset for the current
"batch" of results, that's an accidental omission (but a client can
easily track the offset, which would explain how the omission happened
in the first place).
F21 wrote:
Hey Josh,
Thanks for your examples, those
wCount=100) => Frame[200-250, done=true].
Does that make sense?
F21 wrote:
Ah, makes sense. Also,should the offset be incremented on a per frame or
a per row basis? Regarding the offsets being 0, I opened CALCITE-1181,
so hopefully we can get that sorted.
On 4/04/2016 11:57 PM, Josh Elser wr
As mentioned on the list, I am currently working on a golang
client/driver for avatica using protobufs for serialization.
I've got all datatypes working, except for BINARY and VARBINARY.
For my test table looks like this:
CREATE TABLE test (int INTEGER PRIMARY KEY, bin BINARY(20), varbin
quot;formal" part of Avatica!
Congrats and great work on what you have done already!
F21 wrote:
That would be really great! I think that would help make a lot of
Phoenix drivers currently available to support avatica generically. It
would also reduce the burden of driver maintainers mainta
Hi all,
I have just open sourced a golang driver for Phoenix and Avatica.
The code is licensed using the Apache 2 License and is available here:
https://github.com/Boostport/avatica
Contributions are very welcomed :)
Cheers,
Francis
On 13/05/2016 5:30 PM, Julian Hyde wrote:
Avatica’s ErrorResponse currently has the same information as JDBC (String
sqlState, int errorCode, String errorMessage). I don’t think it’s wise to add
an errorName field, because it would be difficult to propagate it with a JDBC
SQLException.
If
I recently found more time to work on the golang driver for
avatica/phoenix query server.
One of the things I want to do is to be able to trap transactional
conflicts. Here's one of them:
exceptions:"java.lang.RuntimeException: java.sql.SQLException: ERROR 523
(42900): Transaction aborted
ava test case, maybe help track down your issue.
F21 wrote:
I also tried casting the data to a string and setting it to StringValue
and the Rep type to STRING.
This works when I store and retrieve strings from the binary column, but
doesn't work correctly if I try to store something like a small ima
":{"columns":[{"ordinal":0,"autoIncrement":false,"caseSensitive":false,"searchable":true,"currency":false,"nullable":1,"signed":true,"displaySize":11,"label":"ID","columnName":"
ordinal":0,"autoIncrement":false,"caseSensitive":false,"searchable":true,"currency":false,"nullable":1,"signed":true,"displaySize":11,"label":"ID","columnName":"ID","schemaName"
interesting. I'm not sure why base64 encoding it by hand
makes any difference for you. Avatica isn't going to be making any
differentiation in the types of bytes that you send. Bytes are bytes
are bytes as far as we care.
F21 wrote:
Just reporting back my experiments:
1. Using JSON: I set
I have now created a repo on github containing all the binary protobuf
requests and responses to insert binary data into a VARBINARY column.
The repo is available here: https://github.com/F21/avatica-binary-protobufs
The file 8-request is of most interest because that's the one where we
base64 encoding it by hand
makes any difference for you. Avatica isn't going to be making any
differentiation in the types of bytes that you send. Bytes are bytes
are bytes as far as we care.
F21 wrote:
Just reporting back my experiments:
1. Using JSON: I set the serialization of the query server
when I query the binary column, it comes back correctly as raw
bytes in the bytes_values.
Let me know if you want me to open an issue regarding this on JIRA :)
Here's a gist containing the java source code and decoded protocol
buffers for the java and golang requests:
https://gist.github.c
:
BytesValue sounds right. I’m not sure why it isn’t working for you.
On Apr 14, 2016, at 6:34 AM, F21 <f21.gro...@gmail.com> wrote:
As mentioned on the list, I am currently working on a golang client/driver for
avatica using protobufs for serialization.
I've got all datatypes working,
this
be a problem with phoenix? However, it does work correct when the binary
data is base64 encoded and JSON serialization rather than protobufs are
used.
On 19/04/2016 9:12 AM, Josh Elser wrote:
F21 wrote:
Hey Josh and Julian,
Thanks for your input regarding this. I also spent ho
attribute, I
(unnecessarily) changed the previous semantics :)
F21 wrote:
I tried setting it to -1 and it appears to return unlimited rows. Maybe
this is not a bug, but just needs to be better documented?
On 22/08/2016 11:59 AM, Josh Elser wrote:
Hrm, that sounds like a bug. The defaul
(an unlimited number
of values for the statement).
Mind filing a bug?
F21 wrote:
Hi Josh,
Thanks! That clears things up. I noticed that if I explicitly set
max_rows_total to 0, it returns 0 rows, which is different from omitting
max_rows_total.
Is this the expected behavior? Is it possible
Hey guys,
I am in the process of upgrading the go (golang) avatica driver to
support Calcite/Avatica 1.8.0.
I noticed that the protobuf definitions deprecated max_row_count in
favor of max_rows_total.
I also noticed that if I do not include max_rows_total in a Prepare or
PrepareAndExecute
check for the old value and the absence of the new value).
max_rows_total defaults to 0 which is directly set on the JDBC
Statement object. The value of 0 is special in that it means there is
no limit on the number of results returned by that Statement (this
query).
F21 wrote:
Hey guys,
I am
Hey everyone,
Thanks for inviting me to become a committer. I am currently running my
own startup Boostport. We build tools to allow people to run, grow and
automate their businesses.
I am currently using Phoenix (and by extension Calcite + Avatica) to
implement data storage for some of our
If you want to talk to Calcite from .NET, the best way would be to use
the Avatica server. It is an HTTP server that allows you to talk to the
calcite backend using protobufs or JSON.
Here's a .NET client that talks to the Avatica server, but is currently
targeted towards Apache Phoenix
).
Julian Hyde wrote:
Good idea. I’ve logged
https://issues.apache.org/jira/browse/CALCITE-1412<https://issues.apache.org/jira/browse/CALCITE-1412>.
On Oct 4, 2016, at 4:49 PM, F21<f21.gro...@gmail.com> wrote:
Also, you can check out the builds/runs here:
https://app.wercker.com/F21/
each time.
Compare to travis, wercker is also much faster, tests take about 9
minutes to run compared to the 25ish minutes with travis.
Would you be interested in moving the CI over to wercker? You can check
out my branch here: https://github.com/F21/calcite/tree/use-wercker
(.travis.yml
Also, you can check out the builds/runs here:
https://app.wercker.com/F21/calcite/runs
The failures earlier were due to me adjusting the wercker config.
On 5/10/2016 3:08 AM, Julian Hyde wrote:
Francis,
Try removing the depth argument when you do 'git clone'.
Julian
On Oct 3, 2016, at 21
ce for now. Maybe we’ll split source
code repositories at some point. Because the code is all managed by
Apache’s IP governance, any option we choose would be fairly
straightforward.
Julian
On May 17, 2016, at 8:11 PM, F21<f21.gro...@gmail.com> wrote:
Thanks for opening the issue on JIRA,
Hi guys,
I discovered a universal sql CLI client written in golang:
https://github.com/knq/usql
The author has added support using my Avatica golang driver
(github.com/Boostport/avatica). The client has no dependencies and
compiles down to a single binary. This makes it easy to start
Hi all,
Go 1.8 was released recently and the database/sql package saw a lot of
new features. I just tagged the v1.3.0 release for the Go Avatica
driver[0] which ships all of these new features.
The full list of changes in the database/sql package is available here:
I am investigating HA support for the Go Avatica driver.
Let's assume a scenario where we have multiple Avatica servers behind a
load balancer and do not want to use sticky sessions.
Currently, these are some of the questions I have:
1. A connection with an id "123" opened. A server handles
In CALCITE-1353, the first_frame_max_size was changed from a uint64 to
int32 because the value can be negative.
The change to the protobuf definitions can be seen here:
https://github.com/apache/calcite-avatica/blob/master/core/src/main/protobuf/requests.proto#L132
I've been making some
I have a bug report for the Go Avatica driver where someone executed an
`UPSERT` statement and caused the driver to crash. See
https://github.com/Boostport/avatica/issues/34
The driver crashed, because we tried to read
`ResultSetResponse.Signature` and it was null as the statement was an
assuming the Java Kerberos
library would find the cached ticket and set up the appropriate HTTP
requests.
Cheers,
Francis
On 11/07/2017 12:49 AM, Josh Elser wrote:
Hey Francis,
On 7/10/17 7:09 AM, F21 wrote:
Follow up questions:
- According to the client reference for the principal parameter [0
Recently, I came across a maintained pure-go kerberos client and server [0].
I am now in the process of adding SPNEGO authentication to the Go
avatica client [1].
For the implementation, the plan is to make it as close to the official
(java) client's implementation as possible. For SPNEGO,
logins?
- There is also an option for the user to perform the login themselves.
In this case, how does the Java client pass the Kerberos ticket to the
Avatica server?
[0] https://calcite.apache.org/avatica/docs/client_reference.html#principal
On 10/07/2017 3:57 PM, F21 wrote:
Recently, I came
Thanks for the pointers, Josh :)
I'll post back to the list when a release has been tagged.
On 11/07/2017 11:38 AM, Josh Elser wrote:
On Jul 10, 2017 20:18, "F21" <f21.gro...@gmail.com> wrote:
Hey Josh,
Thanks for clearing things up. In Go, it is not idiomatic for a database
Hi all,
I just tagged v2.0.0 for the Go database/sql driver. This will be the
only supported version for Avatica 1.10.0 and Phoenix 4.11.0 on-wards
due to the backwards-incompatible change to fix CALCITE-1353 . For older
versions of Avatica and Phoenix, please use the v1.x.x series. For this
On Jul 18, 2017, at 10:15 PM, James Taylor <jamestay...@apache.org> wrote:
Awesome work, Francis! Would be great to get this into Avatica & Phoenix if
you're interested.
-- Forwarded message ------
From: F21 <f21.gro...@gmail.com>
Date: Tue, Jul 18, 2017 at 9:37 PM
Su
correctness. Whether or not
you provide the first_frame_max_size as id=3 or id=5, the server will
parse the number accordingly and (should *wink*) do the right thing.
I am fairly positive I wrote some unit tests around this code.
On 7/17/17 5:57 AM, F21 wrote:
In CALCITE-1353
Hey Josh,
Thanks for the clarification!
Francis
On 20/07/2017 4:30 AM, Josh Elser wrote:
On 7/17/17 8:04 AM, F21 wrote:
I am investigating HA support for the Go Avatica driver.
Let's assume a scenario where we have multiple Avatica servers behind
a load balancer and do not want to use
emove this ambiguity :)
To answer your question, no, there will be no Signature for
INSERT/UPSERT operations (any operation which returns a number of rows
affected instead of a ResultSet). For SQL which generate a ResultSet
(some rows of data), the Signature would "always" be provided.
On
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/1
WIP: Initial import of the avatica-go client
cc @joshelser @julianhyde
Todo:
- [x] Switch imports from github.com/Boostport/avatica to
github.com/apache/calcite-avatica-go
Hey guys,
I recently received a request to add authentication to the Go Avatica
driver.
I am currently investigating ways to implement this. One of the
limitations of the Go database/sql package is that all configuration
options need to be passed in through the connection string (DSN). For
that the Avatica server can see it?
Francis
On 20/05/2017 12:53 AM, Josh Elser wrote:
F21 wrote:
Just realized the proposed design does not take into account the
situation where someone wants to do HTTP Basic or Digest auth against
avatica, and then pass a separate username/password pair
I have implemented HTTP authentication for the Go driver and want to
test it against avatica to check that it works correctly.
I believe that avatica has a TCK toolkit that contains a built in
database backend using HSQLDB. However the repo on docker hub appears to
be empty:
Here's my update for avatica-go:
I am currently still accepting PRs and pushing fixes to the original
boostport/avatica repository as there is not a release for Avatica-Go
yet. Changes to boostport/avatica are currently cherry-picked into
Avatica-Go.
In regards to the work done on
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/7
Fix execute response with empty result set
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Boostport/calcite-avatica-go
fix-execute
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/5
Merge upstream updates
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Boostport/calcite-avatica-go
merge-upstream-updates
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/6
Bump gokrb5 client to v2
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Boostport/calcite-avatica-go
update-from-upstream
Hi Victor,
Are you using Avatica with HSQLDB? CLOB is current unsupported by
Avatica. Please see CALCITE-1957[0] to track this issue. Contributions
are very welcomed, if you are able to contribute this feature! :)
Cheers,
Francis
On 10/12/2017 7:13 PM, victor wrote:
Hi, calcite development
Github user F21 commented on the issue:
https://github.com/apache/calcite-avatica-go/pull/24
@kenshaw Thanks! I'll merge it when the test turns green. As the project is
now part of the Apache Foundation, I will need to start a vote on the mailing
list in order to tag a release. How
Github user F21 commented on the issue:
https://github.com/apache/calcite-avatica-go/pull/24
@kenshaw, thanks that looks great! As you're not a committer of Apache
Calcite, can you please include your name in parenthesis at the end of the
commit message?
---
Github user F21 commented on the issue:
https://github.com/apache/calcite-avatica-go/pull/24
Thanks for the heads up, I'll make sure to include the `v` in the tag for
the next release. As the fix is not super urgent, I'll wait for a few more
commits before starting a vote
Github user F21 commented on the issue:
https://github.com/apache/calcite-avatica-go/pull/24
@kenshaw Thanks, this is a good idea! As this project is now part of the
Apache Calcite project and the change is not trivial, can you please do the
following:
- Open an issue in JIRA
Github user F21 commented on the issue:
https://github.com/apache/calcite-avatica-go/pull/24
@kenshaw Can you use `(` instead of `[`? Sorry for being picky, but these
are the standards being set by Apache Calcite.
---
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/8
Bump dependencies
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Boostport/calcite-avatica-go bump-deps
Alternatively you can review
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/25
[CALCITE-2372] Add Phoenix 4.14.0 for testing and turn travis.yml into a
build matrix
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/27
[CALCITE-2335] Add support for Go modules and test against Go 1.11
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Boostport/calcite
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/28
[CALCITE-2335] Set module version to v3
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Boostport/calcite-avatica-go
fix-go-module
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/29
[CALCITE-2500] Test against Avatica 1.12.0 and Phoenix 5.0.0
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Boostport/calcite-avatica
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/26
[CALCITE-2493] Update dependencies
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Boostport/calcite-avatica-go
update-dependencies
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/32
[CALCITE-2547] Update dependencies
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Boostport/calcite-avatica-go
update-dependencies
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/30
[CALCITE-2545] Fix import self-referential import paths to point to v3 of
calcite-avatica-go
You can merge this pull request into a Git repository by running:
$ git pull https
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/31
[CALCITE-2544] Replace golang.org/x/net/context with stdlib context
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Boostport/calcite
I am wrapping up some things today and plan to test Avatica Go against
the latest version of Avatica.
I think we'll be able to make a release by the end of the week.
I am happy to be the release manager for this one.
The latest version of Avatica is 2.3.1 under Boostport/avatica, I think
we
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/19
Fix readme
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Boostport/calcite-avatica-go fix-readme
Alternatively you can review
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/22
Check files for Apache license header in make-release-artifacts script
cc @julianhyde
One quick question:
In cb2d4cb4596d5850bd0eb10c9c7697b679aabc2d, the script
Github user F21 commented on a diff in the pull request:
https://github.com/apache/calcite-avatica-go/pull/12#discussion_r181600746
--- Diff: .travis.yml ---
@@ -0,0 +1,54 @@
+# Configuration file for Travis continuous integration.
+# See https://travis-ci.org/apache
Github user F21 commented on a diff in the pull request:
https://github.com/apache/calcite-avatica-go/pull/12#discussion_r181600756
--- Diff: .travis.yml ---
@@ -0,0 +1,54 @@
+# Configuration file for Travis continuous integration.
+# See https://travis-ci.org/apache
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/13
Add HSQLDB support and move phoenix support into an adapter
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Boostport/calcite-avatica-go
Github user F21 commented on a diff in the pull request:
https://github.com/apache/calcite-avatica-go/pull/13#discussion_r181619896
--- Diff: phoenix/phoenix.go ---
@@ -1,82 +1,105 @@
-/*
- * Licensed to the Apache Software Foundation (ASF) under one or more
7cb9e5367@%3Cdev.calcite.apache.org%3E>
On Apr 9, 2018, at 3:26 PM, F21 <f21.gro...@gmail.com> wrote:
I am wrapping up some things today and plan to test Avatica Go against the
latest version of Avatica.
I think we'll be able to make a release by the end of the week.
I am happy to be t
Github user F21 commented on a diff in the pull request:
https://github.com/apache/calcite-avatica-go/pull/12#discussion_r181611670
--- Diff: .travis.yml ---
@@ -0,0 +1,54 @@
+# Configuration file for Travis continuous integration.
+# See https://travis-ci.org/apache
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/14
Clean up readme and remove wercker
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Boostport/calcite-avatica-go clean-up
Alternatively
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/21
Replace gopher.png with Calcite logo and uncomment HSQLDB transaction tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Boostport
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/23
Test against Go 1.9
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Boostport/calcite-avatica-go go-1.9
Alternatively you can review
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/18
Fix link in release history
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Boostport/calcite-avatica-go fix-link
Alternatively you can
Github user F21 commented on a diff in the pull request:
https://github.com/apache/calcite-avatica-go/pull/15#discussion_r181917109
--- Diff: make-release-artifacts.sh ---
@@ -0,0 +1,26 @@
+# Clean dist directory
+rm -rf dist
+mkdir -p dist
+
+# Get new tags
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/16
Remove go-cleanhttp
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Boostport/calcite-avatica-go remove-cleanhttp
Alternatively you can
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/15
Add script to generate release artifacts
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Boostport/calcite-avatica-go
release-artifacts
Github user F21 closed the pull request at:
https://github.com/apache/calcite-avatica-go/pull/16
---
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/17
Update dependencies
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Boostport/calcite-avatica-go update-deps
Alternatively you can
Github user F21 commented on a diff in the pull request:
https://github.com/apache/calcite-avatica-go/pull/15#discussion_r181917310
--- Diff: make-release-artifacts.sh ---
@@ -0,0 +1,26 @@
+# Clean dist directory
+rm -rf dist
+mkdir -p dist
+
+# Get new tags
Github user F21 closed the pull request at:
https://github.com/apache/calcite-avatica-go/pull/17
---
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/20
Documentation fixes
This PR contains fixes to the documentation and website of
calcite-avatica-go as they are identified during the voting process.
You can merge this pull request
Hey everyone,
I am happy to take ownership of the Go avatica client. I am currently
quite busy, but I hope to test it against the latest version of avatica
released a couple of weeks ago and see if we can make a release for it.
Francis
On 28/03/2018 6:27 AM, Shuyi Chen wrote:
Hi Julian and
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/9
Update dependencies
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/calcite-avatica-go bump-deps
Alternatively you can review
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/10
Bump Go to 1.10 and format code
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/calcite-avatica-go bump-go
Alternatively you can
Also would like to see
https://issues.apache.org/jira/projects/CALCITE/issues/CALCITE-1951
worked on.
Francis
On 28/02/2018 9:34 AM, Julian Hyde wrote:
OK, new thread just for the Avatica release. What’s left to do before 1.11?
What can we accomplish before Monday?
There are 20 open JIRA
Do you guys think you can work on
https://issues.apache.org/jira/projects/CALCITE/issues/CALCITE-2013 ?
I tried bumping HSQLDB in the pom.xml a few months ago, but there were a
few failing tests. Bumping HSQLDB will solve a bunch of issues I saw
when testing avatica-go against avatica with
98 matches
Mail list logo
