Hi Jon, Yes, you're right. I had a typo in that example, sorry about that! So I'm able to access the tiles DBs using this methodology, but I'm running into issues when the data size gets moderately large (small enough that spark should normally be able to handle it easily). Example below: * [Notebook to Show Issues With Tiles DB Workaround](https://dbc-caf9527b-e073.cloud.databricks.com/#notebook/149941/command/150014) I'm able to work around it for now by limiting my columns, but this could become a limiting issue sooner rather then later (a number of things related to Ridgeline like snippets data are contained in Tiles). We might want to address this more long term with * [1522364](https://bugzilla.mozilla.org/show_bug.cgi?id=1522364) Will also add note in that bug! Thank you!
Bug 1272388 Comment 22 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Hi Jon, Yes, you're right. I had a typo in that example, sorry about that! So I'm able to access the tiles DBs using this methodology, but I'm running into issues when the data size gets moderately large (small enough that spark should normally be able to handle it easily). Example below: * [Notebook to Show Issues With Tiles DB Workaround](https://dbc-caf9527b-e073.cloud.databricks.com/#notebook/149941/command/150014) I'm able to work around it for now by limiting my columns, but this could become a limiting issue sooner rather then later (a number of things related to Ridgeline like snippets data are contained in Tiles). We might need a long term solution that gives Databricks direct access to the database like we do with the regular Telemetry data Thank you!