Skip to content
This repository was archived by the owner on May 12, 2021. It is now read-only.

EAGLE-993: add duplicate removal settings in policy definition#926

Closed
qingwen220 wants to merge 16 commits intoapache:masterfrom
qingwen220:EAGLE-993
Closed

EAGLE-993: add duplicate removal settings in policy definition#926
qingwen220 wants to merge 16 commits intoapache:masterfrom
qingwen220:EAGLE-993

Conversation

@qingwen220
Copy link
Contributor

.name("Email")
.type(AlertEmailPublisher.class)
.description("Email alert publisher")
.field("subject")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this intended ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes.

As we already define the email subject in the policy definition. it's a little duplicated. How do you think?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

right, its duplicated, Thanks

WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why remove the License?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My mistake. I will add it back.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay.

// remove the column values for publish plugin match
partition.getColumnValues().clear();
if (!publishPluginMapping.containsKey(partition)) {
if (!publishPluginMapping.containsKey(partition.getPublishId())) {
Copy link

@garrettlish garrettlish Apr 21, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In publisher, we are able to specify the accepted streamId list, here how can we handle dropping the alert which comes from the stream which is NOT defined in accepted streamId list?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for the late reply.

For the alert dropping off of unwanted stream is handled in AlertBoltOutputCollectorWrapper, which are kept as it is.

In this class, i just simplify the coding, which should keeps the original logic. How do you think? @garrettlish

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

u can keep you simplified code, it looks good

if (deduplicatorMap != null && deduplicatorMap.containsKey(event.getPolicyId())) {
List<AlertStreamEvent> eventList = deduplicatorMap.get(event.getPolicyId()).dedup(event);
if (eventList == null || eventList.isEmpty()) {
return;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

missing ack here

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right. Thanks

@garrettlish
Copy link

+1

@asfgit asfgit closed this in 8da0663 May 5, 2017
@qingwen220 qingwen220 deleted the EAGLE-993 branch May 26, 2017 11:44
jhsenjaliya pushed a commit to jhsenjaliya/eagle that referenced this pull request Jul 12, 2017
https://issues.apache.org/jira/browse/EAGLE-993

Author: Zhao, Qingwen <qingwzhao@apache.org>

Closes apache#926 from qingwen220/EAGLE-993.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants