cancel
Showing results for 
Search instead for 
Did you mean: 

What is the performance impact of changing dataSkippingNumIndexedCols from 32 to 16?

Thor
New Contributor III

I already improved a lot the performances of our ETL (x20 !) but I still want to know where I can improve performances. I seems that tables stats and column indexing slow down a bit writings so I want to decrease dataSkippingNumIndexedCols to match the small columns subset on which filters are actually applied, and columns with low distinct values. I wonder if it's worth doing that because it requires development work and columns order is imposed.

The documentation says it is worth doing that if your columns contain textual information for example because indexing is inefficient.

0 REPLIES 0
Welcome to Databricks Community: Lets learn, network and celebrate together

Join our fast-growing data practitioner and expert community of 80K+ members, ready to discover, help and collaborate together while making meaningful connections. 

Click here to register and join today! 

Engage in exciting technical discussions, join a group with your peers and meet our Featured Members.