Skip to content

dask-contrib/dask-databricks

View on GitHub ↗Related repositories →

Cluster tools for running Dask on Databricks

active 2023-11-202025-05-20 (UTC)

Complete coverage26,738 / 26,738 hourly files (100%) · 2 absent upstream2023-08-152026-09-02 (UTC)
Events
68
Pushes
2
Pull requests
4
Issues
11
Stars
10
Forks
3

Activity over time

Daily event counts in the loaded window

Line chart, 548 days from 2023-11-20 to 2025-05-20. Pushes: 2 total, peak 1 in a day. Pull requests: 4 total, peak 2 in a day. Issues: 11 total, peak 2 in a day. Comments: 26 total, peak 4 in a day. Stars: 10 total, peak 1 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
jacobtomlinson272415
songhan898003
benrutter7004
Mark-S-Bartlett3002
gdubs892001
skirui-source1001
raybellwaves1000

Recent activity

Latest issues, pull requests and releases

  • Issue comment#42jacobtomlinson2025-01-15 14:35
    Dask worker nodes unable to access files on Databricks Unity Catalog Volume
  • Issue comment#42songhan892025-01-15 09:54
    Dask worker nodes unable to access files on Databricks Unity Catalog Volume
  • Issue comment#42jacobtomlinson2025-01-15 09:44
    Dask worker nodes unable to access files on Databricks Unity Catalog Volume
  • Issue comment#42songhan892025-01-15 06:14
    Dask worker nodes unable to access files on Databricks Unity Catalog Volume
  • Issue comment#42jacobtomlinson2025-01-14 14:57
    Dask worker nodes unable to access files on Databricks Unity Catalog Volume
  • Issue#42songhan892025-01-13 13:58
    Dask worker nodes unable to access files on Databricks Unity Catalog Volume
  • Issue comment#41jacobtomlinson2024-09-26 15:59
    Upgrades to Numpy 2 but Numpy 1.x needed for Databricks
  • Issue comment#41gdubs892024-09-26 15:39
    init script corrupts the cluster
  • Issue comment#41jacobtomlinson2024-09-26 15:03
    init script corrupts the cluster
  • Issue#41gdubs892024-09-26 11:36
    init script corrupts the cluster
  • Issue comment#34benrutter2024-09-18 14:14
    example of read/write parquet using dbfs://
  • Issue comment#39jacobtomlinson2024-06-03 15:30
    Dynamically alter behaviour when on single node cluster
  • Issue#39benrutter2024-06-03 13:23
    Dynamically alter behaviour when on single node cluster
  • Pull request#40jacobtomlinson2024-06-03 11:26
  • Issue comment#40benrutter2024-05-27 13:13
    Raising Environment Error on Single Node Clusters
  • Issue comment#39jacobtomlinson2024-05-23 10:15
    Dynamically alter behaviour when on single node cluster
  • Issue comment#39benrutter2024-05-22 19:28
    Dynamically alter behaviour when on single node cluster
  • Issue comment#39jacobtomlinson2024-05-22 18:33
    Dynamically alter behaviour when on single node cluster
  • Issue#39benrutter2024-05-22 14:55
    Dynamically alter behaviour when on single node cluster
  • Issue#37songhan892024-05-19 15:00
    Dask Dashboard URL not working for Azure Databricks
  • Issue comment#38jacobtomlinson2024-05-15 17:00
    fix: replaced cluster workspace URL with dynamic URL that changes wit…
  • Pull request#38jacobtomlinson2024-05-15 16:57
  • Issue#37songhan892024-05-13 16:12
    Dask Dashboard URL not working for Azure Databricks
  • Issue comment#36songhan892024-05-13 15:20
    Unable to use all nodes/threads setup for Databricks Compute
  • Issue#36songhan892024-05-13 15:20
    Unable to use all nodes/threads setup for Databricks Compute

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 10 stars here means stars gained during the window, not the repo's star count.