Jesus Camacho Rodriguez created CALCITE-1808:
Summary: JaninoRelMetadataProvider loading cache might cause OOM
error
Key: CALCITE-1808
URL: https://issues.apache.org/jira/browse/CALCITE-1808
If you want read consistency in Druid, is there transaction id
(snapshot id) you could use? Then you'll get the same results even if
the result set fails over.
On Fri, May 26, 2017 at 8:37 AM, Josh Elser wrote:
> The Phoenix thin client is 99.9% Avatica :)
>
> The only real
Going off of memory, there is an method you can invoke on the
HttpServer.Builder class (the builder class invoked to create the
Avatica server). I think you would call that method with a path to your
file.
If you're just invoking the StandaloneServer, I think we would just need
to expose
The Phoenix thin client is 99.9% Avatica :)
The only real configuration that comes to mind is specifying the
"jdbc:phoenix:thin" jdbc url prefix
On 5/25/17 7:25 PM, Gian Merlino wrote:
I was thinking that client retries are probably a bad thing, though,
insofar as they are based on offsets
Thanks to everyone who has tested the release candidate and given
their comments and votes.
The tally is as follows.
3 binding +1s:
Julian
Josh
Michael
No 0s, -1s or non-binding votes.
Therefore I am delighted to announce that the proposal to release
Apache Calcite Avatica 1.10.0 has passed.
The Apache Jenkins build system has built Calcite-Avatica-Master (build #19)
Status: Failure
Check console output at
https://builds.apache.org/job/Calcite-Avatica-Master/19/ to view the results.
There isn't anything exposed to "normal" clients that would let them get
read consistency from call to call. Generally we expect people to retry
their operation from the beginning.
Gian
On Fri, May 26, 2017 at 10:05 AM, Julian Hyde wrote:
> If you want read consistency in
Francis Chuang created CALCITE-1809:
---
Summary: Support configuring HTTP Basic and Digest authentication
in the standalone avatica server
Key: CALCITE-1809
URL: https://issues.apache.org/jira/browse/CALCITE-1809