Showing results for 
Search instead for 
Did you mean: 
Get Started Discussions
Start your journey with Databricks by joining discussions on getting started guides, tutorials, and introductory topics. Connect with beginners and experts alike to kickstart your Databricks experience.
Showing results for 
Search instead for 
Did you mean: 

Optimal Strategies for downloading large query results with Databricks API

New Contributor

Hi everyone,

I'm currently facing an issue with handling a large amount of data using the Databricks API. Specifically, I have a query that returns a significant volume of data, sometimes resulting in over 200 chunks.

My initial approach was to retrieve the external_link for each chunk within a loop and then download the .csv file containing the data. However, I've encountered a bottleneck where obtaining the external link alone takes a considerable amount of time, leading to many files expiring before they can be downloaded.

I'm wondering if anyone has found an optimal strategy or method for dealing with this problem. For instance, is it feasible to generate and retrieve all the links at once and then download the files in parallel?

Any insights or suggestions would be greatly appreciated.


Community Manager
Community Manager
Hi @rafal_walisko, Handling large volumes of data using the Databricks API can indeed be challenging, especially when dealing with numerous chunks.
Let’s explore some strategies that might help you optimize your approach:
  1. Rate Limits and Parallelization:

  2. Partitioning and Clustering:

  3. Batch Processing:

    • Consider batching your requests. Instead of fetching all external links at once, break them down into smaller batches and retrieve links for each batch sequentially.
    • This approach can help avoid overloading the system and reduce the risk of files expiring before they can be downloaded.
  4. Caching and Memoization:

    • If your query results are relatively stable over time, consider caching the external links. Cache the links locally or in a distributed storage system (e.g., Databricks File System, Azure Blob Storage).
    • Memoization (caching intermediate results) can save time by avoiding redundant API calls. When a link is requested, check if it’s already cached before making a new API call.
  5. Monitoring and Error Handling:

    • Implement robust error handling mechanisms. Monitor the status of your API requests and handle any failures gracefully.
    • Keep track of the expiration time for each link. If a link is about to expire, prioritize downloading it promptly.

Good luck! 😊

If you’d like more detailed examples or have additional questions, feel free to ask 213

Join 100K+ Data Experts: Register Now & Grow with Us!

Excited to expand your horizons with us? Click here to Register and begin your journey to success!

Already a member? Login and join your local regional user group! If there isn’t one near you, fill out this form and we’ll create one for you to join!