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

Adding native support to query azure data explorer #24818

Closed
toshetah opened this issue Jan 17, 2019 · 3 comments
Closed

Adding native support to query azure data explorer #24818

toshetah opened this issue Jan 17, 2019 · 3 comments
Labels
API Design IO Data IO issues that don't fit into a more specific label Needs Discussion Requires discussion from core team before further action

Comments

@toshetah
Copy link

Hello,

My name is Tomer, and I am a developer working at Microsoft.
I am part of Azure Data Explorer, and maintaining our python packages.
We have many customers that are using pandas, and we were thinking of how to ease their usage.
We would like to expose/contribute something similar to the following:

import pandas as pd
pd.read_azure_data_explorer("query", con=connection_string)

I think that adding the ability to read Azure Data Explorer directly into pandas could potentially help many of our customers who are accustomed to pandas.
I would like to hear what do you guys think about that.

Thanks,
Tomer

@jschendel
Copy link
Member

I suspect this would be more appropriate as a separate package, similar to pandas-gbq (xref #15347). Then, if we were to add this as a top-level pd.read_azure_data_explorer, it would just be implemented as a wrapper around the package, e.g. io/gbq.py.

@jschendel jschendel added IO Data IO issues that don't fit into a more specific label API Design Needs Discussion Requires discussion from core team before further action labels Jan 17, 2019
@TomAugspurger
Copy link
Contributor

TomAugspurger commented Jan 17, 2019 via email

@WillAyd
Copy link
Member

WillAyd commented Jan 21, 2019

Thanks for the request! I'd also lean towards this being in a separate package and given the other feedback I am going to close this.

If you end up building the package let us know and can point to it from the ecosystem docs. Can certainly reach out with questions as well on the mailing list or Gitter

@WillAyd WillAyd closed this as completed Jan 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API Design IO Data IO issues that don't fit into a more specific label Needs Discussion Requires discussion from core team before further action
Projects
None yet
Development

No branches or pull requests

4 participants