You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In io.py we Z ORDER on partitionCols + optimizationCols when useDeltaOpt is True. Since we can partition prune without Z Ordering on partition columns, I believe it makes sense to remove them from the Z Order clause to only optimize on optimizationCols if they are provided.
Is there another advantage to including partition columns within Z ORDER for time series other than data skipping?
The text was updated successfully, but these errors were encountered:
On Mon, Aug 15, 2022 at 11:41 AM Lorin Dawson ***@***.***> wrote:
In io.py we Z ORDER on partitionCols + optimizationCols when useDeltaOpt
is True. Since we can partition prune without Z Ordering on partition
columns, I believe it makes sense to remove them from the Z Order clause to
only optimize on optimizationCols if they are provided.
Is there another advantage to including partition columns within Z ORDER
for time series other than data skipping?
—
Reply to this email directly, view it on GitHub
<#244>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJCRAXABDIJ75JM6UKPSXWLVZJQLLANCNFSM56SUGQBQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
Ricardo Portilla
Industry Vertical Lead - Financial Services, Ph.D
Databricks Inc.
***@***.***
databricks.com
In
io.py
we Z ORDER onpartitionCols + optimizationCols
whenuseDeltaOpt
is True. Since we can partition prune without Z Ordering on partition columns, I believe it makes sense to remove them from the Z Order clause to only optimize onoptimizationCols
if they are provided.Is there another advantage to including partition columns within Z ORDER for time series other than data skipping?
The text was updated successfully, but these errors were encountered: