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
Expected Behavior: UniqueCountReducer (and SqsReducer) should return data formatted as a hash.
Current Behavior: unlike other Reducers, the UniqueCountReducer does not return a key-value hash in its data field. The same issue applies to SqsReducer, which returns "dispatched" in data when no other data field or hash is provided.
Consequences: Many pieces of Caesar code assume that a reduction's data will be a hash. As a result: exports fail, views fail, reduction results can't be accessed by rules, etc.
Potential Solution: For UniqueCountReducer, the update could be as simple as adding a key (e.g., count) for the returned value, and return key-value pair as a hash for the reduction's data.
The text was updated successfully, but these errors were encountered:
Expected Behavior: UniqueCountReducer (and SqsReducer) should return
data
formatted as a hash.Current Behavior: unlike other Reducers, the UniqueCountReducer does not return a key-value hash in its
data
field. The same issue applies to SqsReducer, which returns "dispatched" in data when no other data field or hash is provided.Consequences: Many pieces of Caesar code assume that a reduction's
data
will be a hash. As a result: exports fail, views fail, reduction results can't be accessed by rules, etc.Potential Solution: For UniqueCountReducer, the update could be as simple as adding a key (e.g.,
count
) for the returned value, and return key-value pair as a hash for the reduction'sdata
.The text was updated successfully, but these errors were encountered: