Warning - Aggregator Stage

[devidotcom]

I keep getting these warning when using an aggregate stage which is been used to either count the number of rows or calculate the sum of a column.

Warning are:

"Aggr_Count_Execution: When checking operator: When binding output interface field "ACTL_PULL_EXEC_Q" to field "ACTL_PULL_EXEC_Q": Implicit conversion from source type "dfloat" to result type "int32": Possible range/precision limitation."

"Aggr_Count_Loc: When checking operator: When binding output interface field "Count_Bkrm_Loc_Tran_C" to field "Count_Bkrm_Loc_Tran_C": Implicit conversion from source type "dfloat" to result type "int32": Possible range/precision limitation."

"Aggr_Sum_Pull_Q: When checking operator: When binding output interface field "ACTL_PULL_EACH_Q" to field "ACTL_PULL_EACH_Q": Implicit conversion from source type "dfloat" to result type "int32": Possible range/precision limitation."

Is it possible without using the modify stage?

[bchau]

It has been a few months since I've touched DS. From my experience, it is nearly impossible to create "warning free" jobs.

Warnings just give you some valuable information. In this case, it is just telling you that your data may not be accurate after the aggregation due to your target being an integer. If your source data does not include decimals, you should be fine with this warning.

[ray.wurlod]

Not all warnings in parallel job are bad; some - like these - are alerts.

The Aggregator stage performs its calculations so as to generate dfloat results; this eliminates the possibility of arithmetic overflows (at least in our lifetimes).

When you specify a different data type in the output columns, an alert is generated to warn you that converting from dfloat to the smaller data type may result in loss of data.

To eliminate these alerts, you might use the Decimal Output properties in the Aggregator stage; there is a global one and a per-calculated-column override. Or you might use dfloat as the output field's data type and convert it downstream, for example in a Modify stage that also has the NOWARN specification.

Or, of course, you could create a local message handler to demote these alerts to informational severity.

[devidotcom]

Thanks Ray. Will convert these warnings to info.

When we convert warnings to information in development and then move to test server will the warnings yet been seen as information. The same thing to production if the job is moved there from test server.

[pravin1581]

Not all warnings in parallel job are bad; some - like these - are alerts.

The Aggregator stage performs its calculations so as to generate dfloat results; this eliminates the possibility of arithmetic overflows (at least in our lifetimes).

When you specify a different data type in the output columns, an alert is generated to warn you that converting from dfloat to the smaller data type may result in loss of data.

To eliminate these alerts, you might use the Decimal Output properties in the Aggregator stage; there is a global one and a per-calculated-column override. Or you might use dfloat as the output field's data type and convert it downstream, for example in a Modify stage that also has the NOWARN specification.

Or, of course, you could create a local message handler to demote these alerts to informational severity.

Please let me know how to convert the warnings into messages with the message handler.

[ArndW]

Go to the director log for the job. Right click on a line with the warning message and then choose the option "add rule to message handler". In that window, choose to demote instead of suppress the message and click on "add rule".

[kumar_s]

You need to move the file where those message handlers is stored. The files with the extension .msh need to be moved to the new project.
The files like Local.msh / Fred.msh.