julianhyde commented on pull request #2600: URL: https://github.com/apache/calcite/pull/2600#issuecomment-963271230
Simplest thing is to just support one version of Avatica in Calcite. Which is what we do already. Temporarily turn off the Avatica CI job that runs against Calcite latest. That job is a useful “early warning” but it’s fine if it doesn’t always work. Julian > On Nov 8, 2021, at 04:00, Vladimir Sitnikov ***@***.***> wrote: > > > I'm inclined we should solve this at .iq level or rewrite .iq test to regular JUnit, so can support multiple Avatica versions (e.g. via "contains message1 or message2"). > > Otherwise, it would be the case we support one specific Avatica version only, which questions the split of Calcite and Avatica into different repositories. So we either support at least two Avatica versions, or we should just merge the repositories and stop pretending they are independent libraries. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub, or unsubscribe. > Triage notifications on the go with GitHub Mobile for iOS or Android. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
