Page 1 of 1

User inserted sort does not fulfill the sort requirements

Posted: Wed Aug 31, 2016 11:24 pm
by wuruima
Aggregator_49: When checking operator: User inserted sort "Sort_300" does not fulfill the sort requirements of the downstream operator "APT_SortedGroup2Operator in Aggregator_49"

I encounter this warning..
in the job, i use a sort before Aggregator.

in the sort, i partition with 13 columns and do sort for these 13 columns.

in Aggregator, i use same as partition, and group the 13 columns to sum output.

i am not sure why shows this warning. does the Aggregator must have partition setting in the stage ?

Re: Aggregator_49: When checking operator: User inserted sor

Posted: Wed Aug 31, 2016 11:27 pm
by wuruima
my colleague told me i should not use Hash to partition in the Sort stage. i am going to try another partition type

Re: Aggregator_49: When checking operator: User inserted sor

Posted: Wed Aug 31, 2016 11:51 pm
by wuruima
i found this in the forum
manoj wrote:Before join stage use sort stage and try this..
I think it may hapen because of memory issue..
Inline sort handle less volume of data.
So is that possible because of too big volumn of data?

in the sort stage i need to sort 9 million data. and i set 1000 M in the sort stage.

Posted: Thu Sep 01, 2016 11:08 pm
by jerome_rajan
Did you check if the order of the keys in which you're sorting is the same as the order of your grouping keys in the aggregator?

Posted: Fri Sep 02, 2016 4:08 am
by ray.wurlod
Try using an explicit Sort stage. You can allocate more memory to the sort.

Posted: Mon Sep 05, 2016 2:32 am
by ArndW
This error is typical when your aggregation (or join) after the sort uses different keys than the sort. If you aggregate on 1 field then you need to sort on that 1 field (and not 2 or 3 keys).