Based on some of the SQL Alchemy documentation, they recommend using the pyodbc-access dialect as a good starting point. (Fairly simple, easy to understand how things play out)
https://bitbucket.org/zzzeek/sqlalchemy-access I am looking through the code, but my time to dedicate to this is limited do to an implementation at work that is finally happening. I will continue to post updates as come across them. As a side, I created a git with a simple dev env for Caravel and pyodbc built in a docker container. This includes the MapR ODBC driver, the unix ODBC, and pyodbc. (And has an example python script showing the connection to drill works). Basically, it's everything except the SQL Alchemy Dialect work, Caravel is working with the test data. (And it's persistent, so when you shut down the container, it actually persists the setup work in caravel, so the next time you start, you can just work again). It's not production ready, but it allows people to play around with things, and shows off using python with Drill via pyodbc, using caravel, and allows folks who may know sql alchemy a starting off point. https://github.com/JohnOmernik/caraveldrill John On Sun, May 15, 2016 at 12:34 AM, Ted Dunning <[email protected]> wrote: > On Sat, May 14, 2016 at 6:31 PM, John Omernik <[email protected]> wrote: > > > Thoughts on approaching writing a dialect for Drill for SQL alchemy? > > Anyone here done that before? > > > > Nobody has. It is moderately involved, but doesn't look complicated ... > just lengthy. > > Neeraja is coordinating efforts on this. >
