Re: Bindable Baz.bind(DataContext) issue

Dylan>What can I do to see the source code of the method bindable.bind() to change the way of serializing the SQL query into JSON query ? You might find adding -Dcalcite.debug=true entertaining (see https://calcite.apache.org/docs/howto.html#running-tests ) Baz code is generated on the fly, so

[jira] [Created] (CALCITE-2461) Spelling: add misspell check to Travis job

Vladimir Sitnikov created CALCITE-2461: -- Summary: Spelling: add misspell check to Travis job Key: CALCITE-2461 URL: https://issues.apache.org/jira/browse/CALCITE-2461 Project: Calcite

Re: Sqlline release

Let’s wait about a month then. Target the first week in September. (Good to see all these new features Sergey... keep them coming!) Julian > On Aug 7, 2018, at 11:44 AM, Sergey Nuyanzin wrote: > > +1 for release > at the same time I am ok to wait about a month > (I have a few ideas about

Bindable Baz.bind(DataContext) issue

Hello, I'm trying to convert my SQL query in JSON query so elasticsearch can find what I look for. This is what I have : query = "select * FROM user WHERE name='john' LIMIT 10" It must be serialized in JSON for querying in elasticsearch like this : "query": { "bool": { "must": {

[jira] [Created] (CALCITE-2459) Add implementation of From_Base64 to SqlFunctions

vinoyang created CALCITE-2459: - Summary: Add implementation of From_Base64 to SqlFunctions Key: CALCITE-2459 URL: https://issues.apache.org/jira/browse/CALCITE-2459 Project: Calcite Issue Type:

[jira] [Created] (CALCITE-2460) Add implementation of From_Base64 to SqlFunctions

vinoyang created CALCITE-2460: - Summary: Add implementation of From_Base64 to SqlFunctions Key: CALCITE-2460 URL: https://issues.apache.org/jira/browse/CALCITE-2460 Project: Calcite Issue Type:

Re: Bindable Baz.bind(DataContext) issue

Dylan, The query translation is happening in PredicateAnalyzer (called inside ElasticsearchFilter). Any reason why you want match query instead of term

Re: Bindable Baz.bind(DataContext) issue

Thank you Vladimir and Andrei, Well I thought that the query wasn't executed correctly since it gave me no results but I just found out this was another issue... So this is working fine even with an array of terms for filters. But it can be useful later to know where this is done :) Thanks

Re: Bindable Baz.bind(DataContext) issue

You can always execute ES tests in debug mode. They start real elastic instance and it will help you understand what is happening under the hood. On Thu, Aug 9, 2018 at 10:52 AM

Re: Avatica client can not talk to Multiple Avatica Servers issue

Hi Jiandan, Glad you found my write-up on this. One of the original design goals was to *not* implement routing logic in the client. Sticky-sessions is by far the easiest way to implement this. There is some retry logic in the Avatica client to resubmit requests when a server responds that

Re: Avatica client can not talk to Multiple Avatica Servers issue

One important question is: what state is shared among servers? Some pieces of state: connection state, statement state, result set state (parameter values and position in a scroll). It is not unusual for a cluster of servers to use a shared cache for some of the larger / slower-changing pieces

Re: Avatica client can not talk to Multiple Avatica Servers issue

Hi, Josh, Thank you for sharing your experience and the nice writeup in the hortonworks website too. It’s very helpful. I am just curious why “not implement routing logic in the client” was one of the original design goals? Doesn’t it make easier to use Avatica? I agree that the sharing state

[DISCUSS] Vetoing commits

Calcite PMC, For the first time in this project (to my knowledge) a committer has vetoed the commit of another committer. The details of this particular case are here: https://issues.apache.org/jira/browse/CALCITE-2438 I would like the PMC

Re: Avatica client can not talk to Multiple Avatica Servers issue

This was also an issue I considered for the Avatica Go client when working on the last release. I also came to the conclusion that while implementation is not insurmountable, the amount of effort required is not insignificant. If you're able to push this out to a service mesh such as Istio or

JMH dependency vs licensing

Hi, Apache Calcite has `ubenchmark` Maven module for benchmarking purposes, and it depends on org.openjdk.jmh:jmh-core library for that. It turns out jmh-core is GPL licensed (e.g. https://mvnrepository.com/artifact/org.openjdk.jmh/jmh-core ). Here's my question: is there a licensing issue

Re: calcite git commit: tests: add TestUtilTest to CalciteSuite

Vladimir, Please adhere to the convention for commit comments: start with a capital letter. I would only use a component prefix (“tests:”) if it clarifies. Julian > On Aug 9, 2018, at 12:19 PM, vladimirsitni...@apache.org wrote: > > Repository: calcite > Updated Branches: >

Re: [DISCUSS] Vetoing commits

Thanks for raising this Julian. Without weighing on the veto itself, it seems that there was justification provided, so the veto is valid as long as the justification is accepted. I think this is the general principle to be applied when determining the validity of a veto. IMO, this settles (2) and

Calcite-Master - Build # 786 - Still Failing

The Apache Jenkins build system has built Calcite-Master (build #786) Status: Still Failing Check console output at https://builds.apache.org/job/Calcite-Master/786/ to view the results.

Re: JMH dependency vs licensing

My limited understanding is that this is ok since ubenchmark is optional and not required for Calcite to function. See the JIRA below for a similar question from Apache Arrow. https://issues.apache.org/jira/browse/LEGAL-324 -- Michael Mior mm...@apache.org Le jeu. 9 août 2018 à 14:53,

Calcite-Master - Build # 787 - Still Failing

The Apache Jenkins build system has built Calcite-Master (build #787) Status: Still Failing Check console output at https://builds.apache.org/job/Calcite-Master/787/ to view the results.

Re: [DISCUSS] Vetoing commits

Agreed on your take, Michael. Nice summarizing it too. I think the ultimate question to answer is: "Does the -1 on CALCITE-2438 have a valid justification to veto the commit?" Before diving in, I think it's important to touch on why a "valid veto" is poorly defined by the ASF as a whole.

Re: Avatica client can not talk to Multiple Avatica Servers issue

The decision of avoiding "routing logic" in the client was that other systems can do a better job than we can in Avatica. There are other systems which are specifically designed for doing this -- it's a clear architectural boundary that says one Avatica client expects to talk to one Avatica

Re: calcite git commit: tests: add TestUtilTest to CalciteSuite

Julian>Please adhere to the convention for commit comments: start with a capital letter. I would only use a component prefix (“tests:”) if it clarifies. Could you please clarify where the convention is listed? https://calcite.apache.org/develop/#contributing does not clarify "capital letter",