Leaving aside the fact that Drill needs a fork of Calcite (I accept the arguments for that, more or less), it’s embarrassing that the fork is poorly documented, poorly named (Calcite has been out of the incubator for almost 2 years, and hasn’t been called Optiq for each longer), and is in a particular company’s repository (thereby creating the impression that contributions from non-employees would not be accepted).
Also, has there been a release? My understanding is that the IP is on shaky ground unless there is a release (not necessarily one under the ASF). What can we do to clean up this situation? Julian > On Jul 17, 2017, at 9:00 AM, Arina Yelchiyeva <[email protected]> > wrote: > > Hi Muhammad, > > Link - https://github.com/mapr/incubator-calcite/tree/DrillCalcite1.4.0 > > Kind regards > Arina > > On Mon, Jul 17, 2017 at 6:52 PM, Muhammad Gelbana <[email protected]> > wrote: > >> Could anyone at least just provide a link for that fork's repository please >> ? >> >> >> >> - Gelbana >> >> On Sat, Jul 1, 2017 at 12:02 AM, Muhammad Gelbana <[email protected]> >> wrote: >> >>> Would someone please list the reasons for which Drill required having a >>> custom Calcite build ? This will help integrating Calcite whenever a >>> release is out. >>> >>> One reason I can assume is that Calcite didn't support unparsing all SQL >>> clauses such as FETCH and OFFSET ? >>> >>> I for my self, very much need to use the latest Calcite version with >> Drill >>> and I'm willing to spend time working on that, if it's possible for my >> poor >>> Drill and Calcite knowledge. >>> >>> - >>> Gelbana >>> >>
