Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Removed TaskID from types.HistoryTaskV2Attributes #4876

Conversation

vytautas-karpavicius
Copy link
Contributor

What changed?
Removed TaskID field from types.HistoryTaskV2Attributes

Why?
Not actually used anywhere. Instead we have another SourceTaskID field which is set on types.ReplicationTask that is actually used. It caught my attention as this was set to suspicious value in TaskAckManager:

    TaskID:              task.FirstEventID,

After checking, it looks like do not care about this field in the other side of replication stack.

How did you test it?
Existing tests.

Potential risks

Release notes

Documentation Changes

@coveralls
Copy link

coveralls commented Jun 23, 2022

Pull Request Test Coverage Report for Build 0181a407-18e2-405f-b988-fb295dcbf189

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 70 unchanged lines in 14 files lost coverage.
  • Overall coverage decreased (-0.04%) to 57.959%

Files with Coverage Reduction New Missed Lines %
common/persistence/nosql/nosqlplugin/cassandra/domain.go 1 66.09%
common/persistence/nosql/nosqlDomainStore.go 2 69.04%
common/task/weightedRoundRobinTaskScheduler.go 2 89.12%
service/matching/matcher.go 2 91.46%
common/persistence/nosql/nosqlplugin/cassandra/db.go 3 62.5%
service/history/task/task.go 3 77.06%
service/history/task/transfer_standby_task_executor.go 3 89.32%
service/history/task/fetcher.go 4 91.28%
common/cache/domainCache.go 5 88.48%
common/persistence/nosql/utils.go 5 0%
Totals Coverage Status
Change from base Build 01819355-fe3c-47c3-8fc2-a1bc91ddc928: -0.04%
Covered Lines: 83912
Relevant Lines: 144778

💛 - Coveralls

@vytautas-karpavicius vytautas-karpavicius marked this pull request as ready for review June 23, 2022 12:49
@vytautas-karpavicius vytautas-karpavicius requested a review from a team June 23, 2022 12:50
@davidporter-id-au
Copy link
Contributor

Is there a corresponding IDL change being made? I'm not super familiar with this type, sorry

@Groxx
Copy link
Contributor

Groxx commented Jun 24, 2022

yeah, should probably be marked as deprecated at the very least.

and I assume(?) this is server-side only? or do we have to worry about old clients / old servers during an upgrade?

@vytautas-karpavicius
Copy link
Contributor Author

yeah, should probably be marked as deprecated at the very least.

Yeah, good idea: uber/cadence-idl#113

and I assume(?) this is server-side only? or do we have to worry about old clients / old servers during an upgrade?

It is server side only. Specifically part of replication stack.

@vytautas-karpavicius vytautas-karpavicius merged commit 83aa193 into uber:master Jun 27, 2022
@vytautas-karpavicius vytautas-karpavicius deleted the replication-history-no-task-id branch June 27, 2022 08:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants