Page 1 of 1

change active partition (v8.1.1)

Posted: Wed Sep 27, 2017 5:29 pm
by theDataGuy
I have a large table partitioned by year which I am constantly trickle-loading data into for the current year, 2017, and therefore always need the current year to be the active partition. But if I attempt to backload data for a year that doesn't currently exist in the partition (2014, for example), then the active partition changes to the "newest" year of data loaded, 2014. This eventually causes problems like lengthy mergeouts, high ROS container count, etc.

My question is, does anyone know a way to force a change in active partition key on a partitioned table? In this case, I want to change it back to current year. Or maybe have a better solution that I haven't thought of?

Thanks.

Re: change active partition (v8.1.1)

Posted: Mon Oct 02, 2017 6:29 pm
by JimKnicely
Hii,

This is a current feature request that is coming soon! I'll update this thread when I find out which of the upcoming releases will have it!

Thanks!

Re: change active partition (v8.1.1)

Posted: Thu Sep 27, 2018 2:33 pm
by BobRis
Hi Jim, was this feature implemented yet? I'm considering starting using the new version and if this feature is in, I'm sold.

Re: change active partition (v8.1.1)

Posted: Thu Sep 27, 2018 4:46 pm
by JimKnicely
Hi,

You can now set the Active Partition Count at the table level.

See:
https://www.vertica.com/docs/9.1.x/HTML ... itions.htm

From the doc:
Note: For tables partitioned by non-temporal attributes, set its active partition count to reflect the number of partitions that are subject to a high level of activity—for example, frequent loads or queries.

Re: change active partition (v8.1.1)

Posted: Fri Nov 16, 2018 12:23 pm
by Ghenn
JimKnicely wrote:
Thu Sep 27, 2018 4:46 pm
Hi,

You can now set the Active Partition Count at the table level.

See:
https://www.vertica.com/docs/9.1.x/HTML ... itions.htm

From the doc:
Note: For tables partitioned by non-temporal attributes, set its active partition count to reflect the number of partitions that are subject to a high level of activity—for example, frequent loads or queries.
Thanks for sharing!