-
Notifications
You must be signed in to change notification settings - Fork 46
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
Databus Throttling Changes #847
base: main
Are you sure you want to change the base?
Conversation
1. /UpdateParameterStore 2. /QueueExecutionAttributes/<queue_type>/<queue_name>
* PD-257044-changes-for-databus * duplicated kafka and ssm util packages in emo sor module * removed redundant dependencies
* PD-257044-changes-for-databus * duplicated kafka and ssm util packages in emo sor module * removed redundant dependencies * additional changes * additional changes * additional changes * removed unneccessary dependencies
This reverts commit 62dc31e.
quality/integration/src/test/java/test/integration/auth/TableRoleManagerDAOTest.java
Show resolved
Hide resolved
queue-api/src/main/java/com/bazaarvoice/emodb/queue/api/DedupQueueService.java
Show resolved
Hide resolved
queue-api/src/main/java/com/bazaarvoice/emodb/queue/api/QueueService.java
Show resolved
Hide resolved
queue/src/main/java/com/bazaarvoice/emodb/queue/core/stepfn/StepFunctionService.java
Show resolved
Hide resolved
queue/src/main/java/com/bazaarvoice/emodb/queue/core/stepfn/StepFunctionService.java
Outdated
Show resolved
Hide resolved
queue/src/test/java/com/bazaarvoice/emodb/queue/core/stepfn/StepFunctionServiceTest.java
Show resolved
Hide resolved
web/src/main/java/com/bazaarvoice/emodb/web/resources/queue/QueueResource1.java
Outdated
Show resolved
Hide resolved
web/src/main/java/com/bazaarvoice/emodb/web/resources/sor/DataStoreResource1.java
Show resolved
Hide resolved
sor/src/main/java/com/bazaarvoice/emodb/sor/core/DefaultDataStore.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one potential blocking issue
@@ -41,6 +41,9 @@ Subscription getSubscription(String ownerId, String subscription) | |||
long getEventCount(String ownerId, String subscription) | |||
throws UnauthorizedSubscriptionException; | |||
|
|||
public long getMasterEventCountUncached(String ownerId) | |||
throws UnauthorizedSubscriptionException;; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
throws UnauthorizedSubscriptionException;; | |
throws UnauthorizedSubscriptionException; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed.
// Check if queueType is "dedupq" and prepend "D" to execution name if true | ||
String executionName = (queueType.equalsIgnoreCase("dedupq") ? "D_" : "") + queueName + "_" + timestamp; | ||
|
||
String executionName = (queueType.equalsIgnoreCase("dedupq") ? "D_" : "") + queueName + "_" + timestamp;; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
String executionName = (queueType.equalsIgnoreCase("dedupq") ? "D_" : "") + queueName + "_" + timestamp;; | |
String executionName = (queueType.equalsIgnoreCase("dedupq") ? "D_" : "") + queueName + "_" + timestamp; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed. :)
if(getDataThrottlerValue()) | ||
_kafkaProducerService.sendMessages(MASTER_FANOUT_TOPIC, updateRefs, "update"); | ||
else | ||
_eventWriterRegistry.getDatabusWriter().writeEvents(updateRefs); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
issue(blocker): this writeEvents
function is called twice (line 760 and line 764) - I don't think that's desirable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This line got duplicated as part of rebasing. Thanks for noticing this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
Github Issue
1234
What Are We Doing Here?
Here is where you should describe the problem you are solving as it relates to the Github Issue referred above, adding any fine
details on the solution that might otherwise not be recognizable for someone
unfamiliar with the changes. Add some pictures if it helps.
How to Test and Verify
Risk
Level
Low
,Medium
, orHigh
. Give an indication of what you think is the level of change introduced by this PR.High
means a massive change to a core functionality.Low
means a really minor change that shouldn't have any regression effect.Required Testing
Smoke
,Regression
, orManual
. (All changes except documentation need smoketesting at a minimum).
Risk Summary
Add one or a few complete sentences about the possible risks or concerns for
this change.
Code Review Checklist
Tests are included. If not, make sure you leave us a line or two for the reason.
Pulled down the PR and performed verification of at least being able to
build and run.
Well documented, including updates to any necessary markdown files. When
we inevitably come back to this code it will only take hours to figure out, not
days.
Consistent/Clear/Thoughtful? We are better with this code. We also aren't
a victim of rampaging consistency, and should be using this course of action.
We don't have coding standards out yet for this project, so please make sure to address any feedback regarding STYLE so the codebase remains consistent.
PR has a valid summary, and a good description.