You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After investing work in #124,
and some internal discussions, we agreed to wait with this PR and reconsider changing the API to give better performance for both vanilla python and pandas use cases, and save some difficult trickery to allow parsing kusto type to dataframe:
Final api would look like
# result is of type KustoResultDataSetresult=client.execute(db, query)
# raw json result.tables[0].json()
# iterator with lazy parsing of jsonresult.tables[0].rows()
# dataframe parsing from raw jsonresult.tables[0].to_dataframe()
This will cause some memory pressure, so a best practice would probably be:
# either explicitly access a specific table and drop the reference after conversiondf=client.execute(db, query).primary_results[0].to_dataframe()
# or, parse it alldfs=client.execute(db, query).to_dataframes()
Feel free to add your thoughts, code will be implemented in next couple of weeks.
The text was updated successfully, but these errors were encountered:
After investing work in #124,
and some internal discussions, we agreed to wait with this PR and reconsider changing the API to give better performance for both vanilla python and pandas use cases, and save some difficult trickery to allow parsing kusto type to dataframe:
Final api would look like
This will cause some memory pressure, so a best practice would probably be:
Feel free to add your thoughts, code will be implemented in next couple of weeks.
The text was updated successfully, but these errors were encountered: