perf : unify the implement of isDuplicate in FIFODelta with client-go version

[NeverRaR]

Isduplicate in FIDODelta in Java client version is not consistent with the current implementation of client-go.
client-go implementation :

current java client implementation :

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: NeverRaR
To complete the pull request process, please assign brendandburns after the PR has been reviewed.
You can assign the PR to them by writing /assign @brendandburns in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: [email protected]

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[k8s-ci-robot]

Welcome @NeverRaR!

It looks like this is your first PR to kubernetes-client/java 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-client/java has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[NeverRaR]

/check-cla

[yue9944882]

thanks for diving into it, the diff between java & golang informer here is introduced by #1259 for protecting potential memory leakage defensively. am not sure if the leakage is fixed yet, but it seems that merging two non-delete notifications will not bring any harm to the system, is it?

[NeverRaR]

thanks for diving into it, the diff between java & golang informer here is introduced by #1259 for protecting potential memory leakage defensively. am not sure if the leakage is fixed yet, but it seems that merging two non-delete notifications will not bring any harm to the system, is it?

if we choose merging two non-delete notifications,it will cause flake introduced in #1780 .Maybe ControllerTest should be further modified.

[yue9944882]

/close

b/c the flakiness is solved by #1793

[k8s-ci-robot]

@yue9944882: Closed this PR.

In response to this:

/close

b/c the flakiness is solved by #1793

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.