Run GPU code from our Docs in seconds through BlazingSQL NotebooksYou can now run BlazingSQL Docs in BlazingSQL Notebooks at the push of a button!blazingcontext.ipynb#.explain()No more copy /paste & hope the environment works, or having to transform a generic, possibly out of date examples to fit your query, just log in and run code. Let’s see a few examples.BlazingContext API — .log()BlazingSQL has an internal log that records events from every node from all queries run. The events include runtime query step execution information, performance timings, errors and warnings.The logs table is called bsql_logs. You can query the logs as if it were any other table, except you use the .log() function, instead of .sql().https://medium.com/media/019a3bf9ef0c702a519c8172daeeab50/hrefSQL Reference — LEFT OUTER JOINCombine rows from two or more tables, based on a related column or columns between them. The LEFT JOIN keyword returns all records from the left table (table_A), and the matched records from the right table (table_B).https://medium.com/media/e12c6b8c567e72614571caa16bbd83c5/hrefThanks to BlazingSQL Notebooks’ UI, you can easily build upon the Docs examples in either RAPIDS Stable or RAPIDS Nightly environments, and save your progress to pick up where you left off.Just go to our docs, pick a section, click to “Open in BlazingSQL Notebooks” and run the code, or simply open up the TABLE_OF_CONTENTS.ipynb.Please Note (Existing Users)If you created a BlazingSQL Notebooks account prior to 29 June 2020, you will need to update your Welcome_to_BlazingSQL_Notebooks repo to download the new Docs Notebooks.To do this, open up a Terminal with Launcher (+), and enter these commands;cd Welcome_to_BlazingSQL_Notebooksgit checkout .git pullgit checkout branch-0.15Continued ReadingWelcome to BlazingSQL NotebooksDistributed SQL with DaskBlazingSQL Docs Example Notebooks was originally published in BlazingSQL on Medium, where people are continuing the conversation by highlighting and responding to this story.