[jira] [Created] (CALCITE-5129) Exception thrown writing to a closed stream with SPNEGO authentication at DEBUG

Josh Elser created CALCITE-5129: --- Summary: Exception thrown writing to a closed stream with SPNEGO authentication at DEBUG Key: CALCITE-5129 URL: https://issues.apache.org/jira/browse/CALCITE-5129

[jira] [Created] (CALCITE-5082) Ensure client_reference updated on site for user-facing properties

Josh Elser created CALCITE-5082: --- Summary: Ensure client_reference updated on site for user-facing properties Key: CALCITE-5082 URL: https://issues.apache.org/jira/browse/CALCITE-5082 Project: Calcite

Re: Automatic maven snapshot releases

(top-posting to avoid extending the "how" divergence) Looks great and thanks for your care to avoid advertising them as "releases". Only thing I was going to mention was about whether or not there's a minimally "acceptable" test suite which can reliably run against master before the new job

Re: [VOTE] Release apache-calcite-avatica-1.20.0 (release candidate 0) (second vote)

(sorry for the belated..) +1 (binding) * xsums/sigs are good * Can build from source * CALCITE-4395 a non-blocker, agreed * Git commit looks to be in order On 12/12/21 9:45 PM, Julian Hyde wrote: Hi all, Yesterday I started a vote for Apache Calcite Avatica 1.20.0, release candidate 0, and

[jira] [Created] (CALCITE-4933) Release avatica 1.20

Josh Elser created CALCITE-4933: --- Summary: Release avatica 1.20 Key: CALCITE-4933 URL: https://issues.apache.org/jira/browse/CALCITE-4933 Project: Calcite Issue Type: Task Reporter

Re: [DISCUSS] Do we need a Avatica release before Calcite 1.29.0 release?

CALCITE-4152 is a big performance improvement to Avatica with SPNEGO/Kerberos, but not at all about correctness/datatypes that Calcite needs. I'd agree with Julian. On 12/8/21 7:03 PM, Julian Hyde wrote: Probably not. * 4cf769f8e - (HEAD -> master, origin/master, origin/HEAD) Disable Travis

Re: [DISCUSS] JIRA vs GitHub Issues

Thanks for your reply, Vladimir. On 11/29/21 4:44 PM, Vladimir Sitnikov wrote: Do you think Calcite has something unique in the release process that makes GitHub infeasible? Nope, just calling attention that we want releases to be "easy" to make and anyone should be able to make them (not

Re: [DISCUSS] JIRA vs GitHub Issues

-0 on migrating to GH issues. I'd strongly warn against making a change without a clear and documented plan for issue tagging into a release and how the release process would change. I do think that we need to have a single place to manage issues and that Github could have less friction

Re: (CALCITE-4121) Passing connection properties from URL to OpenConnectionRequest.

Thanks for sending a note, Laksh! I'll take a look at your PR and update Jira now. On 11/17/21 3:51 PM, Laksh Singla wrote: Hi, In continuation of my above mail, I have recently raised a PR for the fix ( https://github.com/apache/calcite-avatica/pull/162). Can I also be assigned to the related

Re: DISCUSS: merge calcite-avatica and calcite repositories

Java 17 is not a priority to me. And, there were few changes in Avatica over the time range in question, so there is no benefit to having releases "for free". Most likely, having additional releases for Avatica would have created _more_ work for me downstream through my employer and Phoenix's

Re: DISCUSS: merge calcite-avatica and calcite repositories

On 11/10/21 3:48 PM, Vladimir Sitnikov wrote: Josh>If we identify these problems, we can think Josh>through (from the beginning) if combining repositories is the only Josh>solution or just one possible solution (and weigh the pros and cons for Josh>each). I am sure I did explain the pain

Re: DISCUSS: merge calcite-avatica and calcite repositories

On 11/10/21 3:48 PM, Vladimir Sitnikov wrote: Josh>I have no objections to combining these two repositories together. Why don't we just merge the repositories and move on then? This was in reference to merging calcite-avatica and calcite-avatica-go together. I thought this would be apparent

Re: DISCUSS: merge calcite-avatica and calcite repositories

Are you still advocating this change, Vladimir? If this is something you want to continue discussing (I'm not sure if your comment about "[I won't contribute to Avatica]" is saying that you don't want to discuss this anymore), could we try to refocus this on some specific technical problems

Re: DISCUSS: merge calcite-avatica and calcite repositories

These repositories are separate because they have separate release schedules. Those who were working on calcite.git typically do not want to be bothered with changes to calcite-avatica.git, and vice versa. Further, there are downstream users of Avatica directly (without Calcite) who would be

Re: [DISCUSS] Add extra check for Avatica to run tests with different timezone

Having had to debug test failures for projects which previously did (simple) randomized testing, I am also not a fan of randomization. If there is a way to deterministically re-run a specific configuration, this goes a long way. I am more worried about debt in maintaining the complexity of a

Re: [VOTE] Release apache-calcite-avatica-1.18.0 (release candidate 0)

+1 (binding) * xsums/sigs work (after the `curl -L` stuff) * No binary files noticed in src release * Can build and run tests in src tarball On 4/7/21 7:33 PM, Francis Chuang wrote: Hi all, I have created a build for Apache Calcite Avatica 1.18.0, release candidate 0. Thanks to everyone who

Re: [VOTE] Release apache-calcite-avatica-1.18.0 (release candidate 0)

/04/2021 4:14 am, Josh Elser wrote: Uh, I'm confused too and seeing the same thing that Julian saw. The key 635665E0 does not exist in the https://www.apache.org/dist/calcite/KEYS. What is in the KEYS file is 3A970AB7. I don't see this key in pgp.mit.edu when I search, either. I can't seem

Re: [VOTE] Release apache-calcite-avatica-1.18.0 (release candidate 0)

Uh, I'm confused too and seeing the same thing that Julian saw. The key 635665E0 does not exist in the https://www.apache.org/dist/calcite/KEYS. What is in the KEYS file is 3A970AB7. I don't see this key in pgp.mit.edu when I search, either. I can't seem to find a server which responds to

Re: [DISCUSS] Towards Avatica 1.18.0

No, I wouldn't wait around for #132. When I left this off, I was debugging some JVM internals to understand why stuff didn't work :) Thanks for asking! I'll try to find some time to help on the other PR's you mentioned. On 2/15/21 4:54 PM, Francis Chuang wrote: Hey Everyone, I am planning

Re: [DISCUSSION] Rename master branch to main

+1 change it. On 7/28/20 1:43 PM, Julian Hyde wrote: I am in favor of renaming ‘master’ to ‘main’. To most people it doesn’t make any difference. To some, such as potential members currently outside the community, it makes the project more welcoming. Very little effort or disruption is

Re: [DISCUSS] Towards Calcite-Avatica 1.17.0

Always a good idea. I'll add this to my list and see if I can help get any committed. It's been a while since I've looked at the list. On 4/8/20 7:59 PM, Francis Chuang wrote: The last avatica release was in December last year. From activity on our mailing lists and the Calcite repository,

Re: [DISCUSS] New Apache Calcite Chair

+1 On 11/21/19 4:48 PM, Francis Chuang wrote: Hey everyone, It's Calcite's tradition to rotate the chair every year. When we had the State of the Project discussion [1] a month ago, there was some consensus towards nominating Stamatis Zampetakis as our next chair. Stamatis has been a

Re: Avatica + GitHub Actions + Windows = AvaticaSpnegoTest - Principal: HTTP/stratum.antpool....@example.com is not known

It's strange that you see this on Windows. Everything should be using localhost in the tests. Maybe that means it's something specific to Windows? I don't know enough to say if that's a reasonable guess or not. The principal looked up stems from the hostname you issue a request to. e.g. if

Re: Contribution permission request

Looks like someone has already added you. Happy contributing. On 11/12/19 3:52 AM, Amir Gajst wrote: Hi Calcite community, My name is Amir Gajst and I'm a developer at Sisense, a BI company. I’d like to contribute to the community, could you please give me the necessary permission? My JIRA

Re: Custom filters on AbstractAvaticaHandler

Hi Som, There are some examples in the unit tests of wiring up HTTP basic and digest authentication via the provided Jetty implementations. These aren't super useful in the real world (because our authentication database is rarely a flat file). There is a fine line between things we can cleanly

Re: Avatica + GitHub Actions + Windows = AvaticaSpnegoTest - Principal: HTTP/stratum.antpool....@example.com is not known

Yeah, the expectation is that all of the tests are using localhost (to specifically avoid issues around trying to pull the FQDN and relying on the developer to have specific setups). On Mon, Nov 11, 2019 at 3:38 PM Kevin Risden wrote: > > > > > 2019-11-10 21:29:30,443 [pool-1-thread-2] ERROR -

Re: [DISCUSS] Towards Avatica 1.16.0

I'll try to get CALCITE-3384 in. Will take a look through the reste here. A couple catch my eye. On 10/9/19 7:26 PM, Francis Chuang wrote: Hey everyone, It's been around 5 months since the last Avatica release. There's been a couple of commits to the code-base since and I'd like to use this

Re: [VOTE] Calcite logo selection

My vote is for 5B I do like the font from 2c more than in 5b, but I like the Gem from 5b quite a lot :) On 6/28/19 9:28 AM, Michael Mior wrote: Based on the previous thread[0], many have weighed in on their preference. There were two clear front runners which we will now vote on. The vote

Re: [DISCUSS] Automated website builds

+1 On 6/4/19 8:43 AM, Michael Mior wrote: I see no reason not to test this out. I'd say go for it! Thanks Francis :) -- Michael Mior mm...@apache.org Le lun. 3 juin 2019 à 21:04, Francis Chuang a écrit : A few months ago, I raised the possibility to automating our website builds, so that we

[jira] [Created] (CALCITE-3090) Update repository URL

Josh Elser created CALCITE-3090: --- Summary: Update repository URL Key: CALCITE-3090 URL: https://issues.apache.org/jira/browse/CALCITE-3090 Project: Calcite Issue Type: Task

Re: Clean up JIRA tickets

Yes, please check the "don't send emails" button in the future :) Thanks for cleaning them up, Hongze! On 4/29/19 12:11 PM, Kevin Risden wrote: You can do this as a bulk transition to avoid emailing everyone of the change. If you select "Tools" -> "Bulk change". Kevin Risden On Mon, Apr 29,

Re: [DISCUSS] Automated website builds for Calcite projects

Yep to all of the below: Jenkins is self-service and we have the ability to automate this stuff. FWIW, HBase has some automation around auto-publishing website content that you could look at https://builds.apache.org/job/hbase_generate_website/ Some more info: Jenkins has the ability to run

Re: CalciteRemoteDriverTest vs avatica.MetaImpl vs avatica.server.Main thread safety

The Meta implementation inside of the Avatica server is a singleton, so yes the implementation must be threadsafe as the server will dispatch multiple user request threads to it. The Meta implementation is largely (by virtue of the wire API) stateless. I think the expectation should be that

Re: Breaking change in Avatica-Go when handling null and empty strings for Apache Phoenix

Nice write up, Francis. Do we have a corner of the Avatica website for the Go-driver yet which you could use to memorialize this? Thinking that it might be more readily found than via mailing list archives. On 1/6/19 10:38 PM, Francis Chuang wrote: This is a heads up regarding a breaking

Re: Avatica CI test failures

Actually, I think filtering in the version is a good idea. I should have thought of that one on my own :P. Thanks for the suggestion, Vladimir! Looks like the Dockerhub stuff is still WIP (at least, that issue is still open). I'm not sure what combination of plugins would be best to do this

Re: Avatica CI test failures

! I'll try to get this fixed today. On 21/11/2018 3:57 am, Josh Elser wrote: Wait, back up a second? Francis -- did you break every other build just to try to fix CALCITE-2385? We should not have had to be making changes to CI just to make this work... On 11/19/18 4:04 PM, Francis Chuang

Re: Avatica CI test failures

Wait, back up a second? Francis -- did you break every other build just to try to fix CALCITE-2385? We should not have had to be making changes to CI just to make this work... On 11/19/18 4:04 PM, Francis Chuang wrote: Thanks for organizing that, Michael! Kevin: Currently, all builds will

Re: Avatica CI test failures

I think a detail that was dropped here is that this only affects a `deploy`, not a normal dev build. Re-reading the context on CALCITE-2385 reminded me about what exactly Francis was trying to do. This shouldn't being affecting the average person, just those deploying SNAPSHOTs by hand. There

[jira] [Created] (CALCITE-2650) Create a URL property for controlling autocommit in Avatica

Josh Elser created CALCITE-2650: --- Summary: Create a URL property for controlling autocommit in Avatica Key: CALCITE-2650 URL: https://issues.apache.org/jira/browse/CALCITE-2650 Project: Calcite

Re: [DISCUSS] Where do we draw the line?

Let's not mince words about what this was: it was public shaming and bullying. Looking at that thread you linked: Zoltan was trying to describe why he thought this was not a big problem. I can't say well enough whether he is right or not (that's beside the point). It was completely

Re: [DISCUSS] Dropping old Guava support

On 10/15/18 12:25 PM, Julian Hyde wrote: What if we switch things around: instead of depending on the older on in the POMs, we switch to the newer one and do release testing around the older ones that folks have an interest in supporting? If a certain module needs a specific version of Guava

Re: [DISCUSS] Dropping old Guava support

I’m not sure we need to disable it working with older versions. Julian On Oct 12, 2018, at 12:41 PM, Josh Elser wrote: Hi, Guava [11,24.1.1) is marked as being vulnerable via https://nvd.nist.gov/vuln/detail/CVE-2018-10237 Avatica currently depends on Guava 14.x and Calcite on 19.

[DISCUSS] Dropping old Guava support

Hi, Guava [11,24.1.1) is marked as being vulnerable via https://nvd.nist.gov/vuln/detail/CVE-2018-10237 Avatica currently depends on Guava 14.x and Calcite on 19.0. I'd like to start a discussion about how we ensure "safe" hygiene in our dependencies while still ensuring compatibility

Re: Avatica or Calcite or mine fault?

* from filters where name = ?" *run through avatica jdbc implementation is resulting NPE in Common.AvaticaParameter AvaticaParameter.toProto(). On Wed, Oct 3, 2018 at 12:46 AM Josh Elser wrote: re: nulls on className, that's how Protobuf itself works. You can't set null for

Re: Avatica or Calcite or mine fault?

re: nulls on className, that's how Protobuf itself works. You can't set null for an attribute. What is the circumstance where you would have a null className on an AvaticaParameter? We could proactively check in the constructor to AvaticaParameter that you don't provide null arguments, but

Re: [VOTE] Release calcite-avatica-go-3.2.0 (release candidate 0)

+1 (binding) On 9/11/18 5:17 AM, Francis Chuang wrote: Hi all, I have created a release for Apache Calcite Avatica Go 3.2.0, release candidate 0. The release notes are available here: https://github.com/apache/calcite-avatica-go/blob/master/site/_docs/go_history.md The commit to be voted

Re: Publish Drill Calcite project artifacts to Apache maven repository

Maven central is made up of a number of "Trusted" Maven repositories. This includes the ASF and OSSRH Maven repositories. Many other organizations run "mirrors" of central. The ASF Maven repo is published to by ASF projects who have gone through the ASF release process. OSSRH allows any

Re: [DISCUSS] Towards calcite-avatica-go-3.1.1

e that 3.1.0 should not be used. Is there anything else that needs to be done? I'd also like some opinions as to whether the tarballs should be renamed to apache-calcite-avatica-go-x.x.x-src.tar.gz from apache-calcite-avatica-go-src-x.x.x.tar.gz. Francis On 11/09/2018 6:15 AM, Josh Elser

Re: [DISCUSS] Towards calcite-avatica-go-3.1.1

+1 to Kevin's concern about 3.1.1 going out with a "don't use 3.1.0" if I'm understanding this all correctly. Admittedly, I'm a bit dense and haven't spent enough time understanding the problem. (Maybe just skip the 3.1.0 announcement if that hasn't gone out yet too) I trust you to be doing

Re: [VOTE] [CALCITE-490] Remove "End File.java" comments from the end of files

-0 I don't see this as a burden as you do, but don't feel strongly either way. On 9/10/18 4:49 AM, Vladimir Sitnikov wrote: Hi, Could we have a vote on coding style regarding "// End File.java" in Calcite source files? "//End..." comments clutter Git history, they consume screen space, and

Re: [VOTE] Release calcite-avatica-go-3.1.0 (release candidate 2)

+1 (binding) * xsums/sigs OK * Can "build" from source * Ran tests successfully * L look OK * Checked packages in Gopkg.toml are permissively licensed * Spot-checked files for license headers (this would be nice to automate in a script) On 9/5/18 4:05 PM, Francis Chuang wrote: Hi all, I

Re: Calcite-Master Jenkins is cluttered with download progress

On 8/31/18 4:50 PM, Vladimir Sitnikov wrote: FWIW, as long as you have an account on builds.a.o, you can edit the I've account there, and I do not see "edit" button. I have "build now", but not edit for some reason. Vladimir Curious. I have no idea why I have more karma than you do :)

Re: Calcite-Master Jenkins is cluttered with download progress

Doing it now. FWIW, as long as you have an account on builds.a.o, you can edit the Jenkins job yourself (actually, anyone's jobs ;)). I can't remember if you need to ask for an account or if your committer credentials are sufficient. On 8/31/18 4:09 PM, Vladimir Sitnikov wrote: Hi,

Re: [VOTE] Release calcite-avatica-go-3.1.0 (release candidate 0)

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

Re: [DISCUSS] Towards Avatica-Go 3.1.0

Sounds good! Will try to take it for a spin. On 8/28/18 7:05 PM, Francis Chuang wrote: Hi all, I'd like to start a vote for Avatica-Go 3.1.0 over the next few days. Some key things I'd like to address in this release: - Go 1.11 was released a few days ago and now includes support for

Re: Maven wrapper

ce files), which is problematic for an open source project. Julian On Jan 2, 2018, at 3:31 PM, Josh Elser wrote: +1 to the simplicity. But, to Vladimir's issues (thx btw), maybe we can solve some of those pain-points another way? I've seen some projects (notably, those with compilation of C/C

Re: [DISCUSS] Avatica - how efficient is our protocol?

I remember when I was doing some old benchmarks, I had to build some custom logic to get writes happening at a decent speed (some basic batching and avoiding deserializing things when I could). I'm sure there is much more we can do here, especially around our HTTP transport. My impression is

Re: Arrow Flight

Thanks for the heads-up, Julian. Subscribing. I don't really grok how Arrow would be used with Avatica now (I struggle with how Arrow would be used in place of Protobuf, period), but I should make the time to figure that out. On 8/16/18 1:27 PM, Julian Hyde wrote: There's a discussion on

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

: Totally make sense. The only inconvenience is that every user has to repeat the same work by setting up the sticky sessions. -Jiandan On Aug 9, 2018, at 1:08 PM, Josh Elser wrote: The decision of avoiding "routing logic" in the client was that other systems can do a better job th

Re: [DISCUSS] Vetoing commits

First off, thanks for staying engaged with this conversation, Vladimir. I know this stuff is uncomfortable to talk through. On 8/10/18 1:34 PM, Vladimir Sitnikov wrote: Josh>That doesn't mean you can stop CALCITE-2438 from happening meanwhile Of course I can't. Ok, good. Just making sure :)

Re: JMH dependency vs licensing

Yep, concur on these points. My understanding on them all. On 8/10/18 12:33 PM, Julian Hyde wrote: That’s my understanding as well. I thought we’d settled this a while ago. (I can’t find a URL to prove it.) Julian On Aug 10, 2018, at 7:58 AM, Enrico Olivelli wrote: I think it is fine to

Re: [DISCUSS] Vetoing commits

(I'll come around to your reply to my original, Vladimir. Need lots more time than I have today to address all of that.) I want to address one specific point here that I find troubling: A veto is not something you can levy and then say you're "[checked out]". There is no "high ground" here.

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

y too long? -Jiandan On Aug 9, 2018, at 8:43 AM, Josh Elser wrote: 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 Avat

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

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: Flaky test: RelMetadataTest#testPullUpPredicatesForExprsItr (was Re: Calcite-Master - Build # 325 - Still Failing)

n; but its waiting on feedback/approval/etc :) cheers, Zoltan On 9 July 2018 23:11:37 CEST, Josh Elser wrote: Based on the comment in the test case, the test has a timeout because it previously took 15+minutes. With a timeout of 20seconds, it's passing maybe 50% of the time on my local mac

Flaky test: RelMetadataTest#testPullUpPredicatesForExprsItr (was Re: Calcite-Master - Build # 325 - Still Failing)

Based on the comment in the test case, the test has a timeout because it previously took 15+minutes. With a timeout of 20seconds, it's passing maybe 50% of the time on my local machine. Goes to reason that we're seeing the same on the builds.a.o machine. Any complaints in bumping the

Re: Calcite-Avatica-Master - Build # 81 - Still Failing

This seems to just be an issue with some cached class files. I just tweaked the Jenkins job to clean the repo which will hopefully help. On 6/24/18 8:02 PM, Apache Jenkins Server wrote: The Apache Jenkins build system has built Calcite-Avatica-Master (build #81) Status: Still Failing Check

Re: [DISCUSS] Towards Avatica 1.12.0

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

Check those commit messages please!

I'm noticing some recent commits on Avatica where we have no lineage on what JIRA issue the change was for. Please make sure you have the "[CALCITE-]" included in the commit message when we're not dealing with something trivial. No need to ACK this, take responsibility, or anything of the

Re: Reviewers

I'd request that Avatica remains with me as the core owner. It's low-volume enough that it helps me filter some of the rest of the "noise" :) On 5/22/18 1:09 PM, Julian Hyde wrote: It gets assigned to me because I am owner of the “core” component in JIRA. Should we remove owners from all

Re: [ANNOUNCE] Apache Calcite Avatica Go 3.0.0 released

+1 Sorry I didn't have the cycles to be more hands on, but great work making it happen, Francis! On 4/27/18 10:48 PM, Kevin Risden wrote: Awesome work Francis! Kevin Risden On Thu, Apr 26, 2018 at 7:09 PM, Francis Chuang wrote: The Apache Calcite team is

Re: Calcite-Avatica-Master - Build # 54 - Failure

Wonderful!! Thanks for picking this up and fixing it :) On 4/29/18 12:07 PM, Kevin Risden wrote: Fixed build. Issue was with javadoc from CALCITE-2272 Passing build. https://builds.apache.org/job/Calcite-Avatica-Master/56/ Kevin Risden On Sun, Apr 29, 2018 at 10:18 AM, Kevin Risden

Re: calcite-avatica-go git commit: Update release script to also produce a zip archive

I think tar.gz or tar.xz are both good options and see them fairly equally (not sure if maven-assembly-plugin supports xz, but would be surprised if it didn't). bz2 is just "slow" in my mind, but I suppose we're not really producing very large artifacts so it wouldn't be a pain. I am good

Re: [ANNOUNCE] New committer: Kevin Risden

Congrats, Kevin! Keep up the good work :) On 4/25/18 12:36 PM, Julian Hyde wrote: Apache Calcite's Project Management Committee (PMC) has invited Kevin Risden to become a committer, and we are pleased to announce that he has accepted. Kevin has been active in the Calcite community for some

Re: [VOTE] Release calcite-avatica-go-3.0.0 (release candidate 1)

+1 (binding) * xsums+sigs OK * KEYS updated and signing key is published * No binary files in src release * License headers on relevant files * LICENSE is OK * NOTICE is OK Good work, Francis! On 4/22/18 8:05 PM, Francis Chuang wrote: Hi all, I have created a release for Apache Calcite

-jdk10 for Calcite on Jenkins (Re: Calcite-Master - Build # 246 - Still Failing)

I've disabled JDK10 builds for Calcite as these appear to be broken around maven-surefire-plugin. https://builds.apache.org/job/Calcite-Master/247/jdk=JDK%2010%20(latest),label_exp=ubuntu&&!cloud-slave&&!H31/console Trying to get the matrix job up and healthy again for Calcite. On 4/9/18 2:18

Re: two avatica bugs

Hi Victor, I don't understand the first bug you are trying to describe. Please try to create a unit test which shows what you are seeing which is broken. The second does not surprise me -- I don't recall ever seeing the CLOB datatype implemented. Same for BLOB. You are very welcome to

Re: Calcite-Avatica-Master - Build # 44 - Still Failing

I've just made the corresponding changes to the Calcite-Master job, too. On 3/13/18 6:06 PM, Josh Elser wrote: PS: fixed these. The configurations weren't running on the desired set of nodes. Most of the times the failures were due to tests failing on Windows. I've also swapped the JDK

Re: Calcite-Avatica-Master - Build # 44 - Still Failing

PS: fixed these. The configurations weren't running on the desired set of nodes. Most of the times the failures were due to tests failing on Windows. I've also swapped the JDK testing matrix from [7, 8, 9] to [8, 9, 10ea]. On 3/12/18 5:33 PM, Apache Jenkins Server wrote: The Apache Jenkins

Re: [VOTE] Release apache-calcite-avatica-1.11.0 (release candidate 0)

+1 (binding) * src-release looks good * Ran sqlline against a docker-image HSQLDB (still cool :D) * Compiled and ran Apache Phoenix tests against 1.11.0 successfully * Ran all tests for Avatica successfully. Created CALCITE-2207 to make our build a little more obvious in what we support for

[jira] [Created] (CALCITE-2207) Enforce Java version via maven-enforcer-plugin

Josh Elser created CALCITE-2207: --- Summary: Enforce Java version via maven-enforcer-plugin Key: CALCITE-2207 URL: https://issues.apache.org/jira/browse/CALCITE-2207 Project: Calcite Issue Type

Re: [VOTE] Release apache-calcite-avatica-1.11.0 (release candidate 0)

It's on my list to check out today ;) I think I have another day, still, but I definitely intend and want to VOTE. On 3/7/18 11:08 AM, Michael Mior wrote: I hope we can get another PMC member to test this soon so we can get this release out!

Re: Setting up Calcite development with Eclipse

I've chased these down a few times on Avatica and other projects. In general, you shouldn't have to invoke the eclipse:eclipse mojo directly to import to modern versions of Eclipse. You should just be able to import it as a Maven project. If that fails, it's something we can/should fix in

Re: dependencies and licensing

re: #3, it's been hashed out many times (here in Calcite and elsewhere in the ASF). The result of which is that there is misleading licensing information, but this dependency is of no concern. On 1/29/18 10:00 AM, Michael Mior wrote: 1. Since we don't publish the dependencies HTML, fixing it

Re: JDK updates for CI

Nope. As long as you have a Jenkins account, you should be able to edit the job. It's the wild-west (so don't go changing other folks' jobs :P). If you need a Jenkins account, that would be a request to INFRA in some form or another. On 1/10/18 1:54 PM, Michael Mior wrote: How do we go

Re: [DISCUSS] Draft board report

+1 Maybe include the last Avatica release too? (1.10.0 on 2017/05/29) On 12/31/17 5:39 PM, Michael Mior wrote: See below a draft of the board report for Jan. 17. I borrowed heavily from past reports and the release notes but I think the necessary points are covered. If there's any activity I'm

Re: Maven wrapper

Well put, all. I think I would be -1 on such a change without better/specific reasons as to what is broken/bad. Multiple versions of Maven can be installed side-by-side (and we don't have esoteric requirements). As such, I don't see the need for such a change. On 12/31/17 2:27 AM, Julian

[jira] [Created] (CALCITE-2086) HTTP/413 in certain circumstances due to large Authorization headers

Josh Elser created CALCITE-2086: --- Summary: HTTP/413 in certain circumstances due to large Authorization headers Key: CALCITE-2086 URL: https://issues.apache.org/jira/browse/CALCITE-2086 Project

Re: JIRA Github integration

I'm confused, we definitely have GH+JIRA integration enabled (at least, in part) already. See https://issues.apache.org/jira/browse/CALCITE-1922 for an example. Our commit message "structure" is at odds with the integration, though ([CALCITE-1234] would not link them, you have to change the

Re: query about avatica odbc

ailure and in the process I almost scrutinized my environment. The bridge is monstrous approach to start with but just out of curiosity, has anyone every succeeded plugging avatica jdbc in such odbc-jdbc bridge? On 4 December 2017 at 06:24, Josh Elser <els...@apache.org> wrote: Hi Victor, An ODBC driver

Re: query about avatica odbc

Hi Victor, An ODBC driver for Avatica would be a great addition to the project, but I am not aware of anyone who has volunteered to take on this development effort. On 12/1/17 9:03 PM, victor wrote: Hi, calcite development team: we now use calcite for some databases development ,

[jira] [Created] (CALCITE-2073) Allow disabling of protobuf generation

Josh Elser created CALCITE-2073: --- Summary: Allow disabling of protobuf generation Key: CALCITE-2073 URL: https://issues.apache.org/jira/browse/CALCITE-2073 Project: Calcite Issue Type: Task

Re: Apache Zeppelin with Calcite JDBC adapters

​(). Later throws an explicit ​ UnsupportedOperationException ​. E.g. ​ @Override public void commit(ConnectionHandle ch) { throw new UnsupportedOperationException(); } On 22 November 2017 at 17:11, Josh Elser <els...@apache.org> wrote: Hey Christian, Thanks for sharing this. Sounds cool

Re: Apache Zeppelin with Calcite JDBC adapters

Hey Christian, Thanks for sharing this. Sounds cool. I'm curious what you mean when you say that the Avatica connection doesn't support commit. This was implemented in CALCITE-767. Also, is there a reason that Zeppelin needs a property to control autoCommit and can't use the

Re: [DISCUSS] The state of the project - 2017

On 11/6/17 12:00 PM, Jesus Camacho Rodriguez wrote: I am not involved in the Avatica effort, but it has been great to see Avatica continue maturing, moving into its own repository and following with its own release cadence. Josh, Julian, if you want to add a few lines about the state of

Re: Introductions - contributing database research and development expertise where needed

Hi Edmon, Nice to meet you and welcome to the community! I don't have enough context to throw some well-bounded problems at you (I tend to do most of my work on Avatica rather than Calcite directly), but I thought it would be nice to say hello anyways :) Your aspirations and ambition sound

[jira] [Created] (CALCITE-2022) ConnectionConfigImplTest failing on Jenkins

Josh Elser created CALCITE-2022: --- Summary: ConnectionConfigImplTest failing on Jenkins Key: CALCITE-2022 URL: https://issues.apache.org/jira/browse/CALCITE-2022 Project: Calcite Issue Type

[jira] [Created] (CALCITE-2017) Automatic Kerberos login fails on IBM Java

Josh Elser created CALCITE-2017: --- Summary: Automatic Kerberos login fails on IBM Java Key: CALCITE-2017 URL: https://issues.apache.org/jira/browse/CALCITE-2017 Project: Calcite Issue Type: Bug

Re: Quetsion of CalciteConnectionProperty default value.

I can't imagine a reason why it is important to be set to that value. The lack of other comment from folks further makes this likely. Please change it if you see fit. On 10/11/17 11:17 PM, Miki Shingo wrote: To whom it may concern, I have one question about the setting default value of

  1   2   3   4   >