🌟 Community Pulse: Your Weekly Roundup! December 22, 2025 – January 04, 2026

Advika
Community Manager
Community Manager

The calendar changed. The conversations didn’t. 
The year turned somewhere between a solved thread and a new question. 
No pause. No reset – just learning, continuing right where it left off. 
Here’s how it unfolded πŸ‘‡


πŸ”Š  Voices That Moved the Conversation Forward

Featuring members who moved conversations forward with clarity, curiosity, and the confidence to contribute – welcoming a few new names into the callout πŸŽ‰

@Hubert-Dudek   |  @mukul1409   |  @Sanjeeb2024 

+ Top Brickster contributors:

@iyashk-DB   |   @emma_s 

Note: Names are listed in no particular order.


🧠  Community Articles & Partner Blog

From new feature updates to practical walkthroughs and lessons learned, the articles bring a surge of knowledge worth exploringπŸ‘‡


πŸ”  Key Threads & Insights

      Highlights from the DiscussionsπŸ‘‡


βœ…  Problems β†’ Solved

      This is where learning turns into impact πŸ™Œ

  • while loading data from dataframe to spark sql table using .saveAstable() option, not working
  • st_point is disabled or unsupported
  • What are recommended approaches for feature engineering in Databricks ML projects?
  • Calling a function with parameters via Spark ODBC driver
  • Import .py files module does not work on VNET injected workspace

Every solved thread is more than a checkbox – it’s shared knowledge fueling thousands of brains. And it’s all possible because of you. This is what makes the Databricks Community truly special. πŸ™Œ

Wishing you all a very happy 2026 πŸ˜ƒ! May this year supercharge your learning, spark new insights, and take our Community to the next level. πŸ˜Ž

Sanjeeb2024
Contributor III

Thank you @Advika 

Sanjeeb Mohapatra

mukul1409
New Contributor II

Thanks @Advika πŸ˜

Mukul Chauhan