Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A strategy for talking about ibis #2

Open
tonyfast opened this issue Mar 30, 2020 · 7 comments
Open

A strategy for talking about ibis #2

tonyfast opened this issue Mar 30, 2020 · 7 comments

Comments

@tonyfast
Copy link
Contributor

@rpekrul I just pushed a few notebooks to the repo that outline 4 posts to round out a few weeks of work.

The progression of posts are:

  1. Using Ibis to write SQL expressions. (This draft is ready for review)
  2. Using Ibis for different databases. (Working on this now)
  3. A Story about adding the OmniSci backend to Ibis.
  4. A Story about Ibis visualization.

I was thinking these topics could be good and I could get feedback or help from @xmnlab and @saulshanabrook on their parts of the work.

@xmnlab
Copy link

xmnlab commented Mar 30, 2020

nice. let me know if I can help in any way. I have some notebooks at https://github.com/Quansight/ivan-sandbox/tree/master/ibis/

also there is a module there that with connection configuration for all backends.

if you have the ibis repo locally you can start and prepare all backends using make init

maybe it could help in your item 2.

I will take a look into your item 2.

@tonyfast
Copy link
Contributor Author

Thanks for the link to these notebooks and the heads up on the backends.

It seems like there is a lot of stuff in ibis i dont want. I don't think it is worthwhile talking about impala or pyspark.

@saulshanabrook
Copy link

saulshanabrook commented Mar 30, 2020

I am reviewing now... Any thoughts on how to make it easier to make suggestions in github? It doesn't let you edit notebook by default.

What if you authored it in markdown? If you need some way of inserting outputs into markdown, I am happy to help prototype how you could author that in jlab!

@saulshanabrook
Copy link

I like all the pieces in the first post, the expressions, the sql, the plots, the DAGs, the dataviews...

I am curious how they could be rearranged. It's a bit hard to trace what comes from where, I think because I am new the the pidgen format.

it almost makes me want tabs on the outputs, so you could switch between sql, data, expression graph, and text, to see all the different ways of understanding an ibis? idk just spitballing

@tonyfast
Copy link
Contributor Author

tonyfast commented Mar 30, 2020

I was going to suggest using the markdown to make comments, but the file is too big. Thinking on it. It would probably make sense to use hugo or something. This was ad hoc and not really formalized. The goal was to get the first draft out quickly.

I dig the tab idea.

@saulshanabrook
Copy link

This was ad hoc and not really formalized. The goal was to get the first draft out quickly.

Yep that makes sense!

@tonyfast
Copy link
Contributor Author

tonyfast commented Apr 6, 2020

@saulshanabrook if you have the time. wanna try the reviewnb service that #5 links to?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants