Partition gave you addition slice to your data , in Vertica the data is segmented (divided ) a cross the nodes , partition gave addition slice storage capability’s in level of host .
In some case it can improved your query performances . The main used of them is for purging data as Vertica is not so optimized for deletes .
Amount of partitions is limited (up to the maximum amount of ROS containers- 1024) , but in fact it should be much more less , best practices is around 200-300 .
ROS files are manage per partitions , Mergout have different roles with regard to active and none active partitions
Thanks but I wanted to know how the partitioned created in vertica has to do with ROS container and What happens when a new ROS container created from move out has to follow up with partition.
About MoveOut - its in the same game , if your data in the WOS belong to specific partition the MoveOut will create ROS file for this partition and will increases your total ROS file per projection
In Vertica Transactions never update existing ROS files , MoveOut will create new ROS file for allthe 10 different transactions on the 201603 partition .
You can see MoveOut as a process that do WOS Mergout and create singel ROS file as an output .
So You are mentioning that the 1000 records will be moved to One newly created ROS container file.
in that case there will be morethan one ROS file for one partition.
Now the new question in that case is "Will the mergeout merge the 2 ROS files and combine it to one or the multi ROS for one partiotion still persists"
Correct , you can have more than one ROS file in an active partition , for none active partition , you will have only one .
During the life of the partition (the time its in active partition mode) Mergout will try to merge theROS files to minimum amounts ( Its more of the algorithm of the Mergout) , but it not necessarily that you will have only one.