-
Notifications
You must be signed in to change notification settings - Fork 4
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
Feature/195 #205
Feature/195 #205
Conversation
@@ -36,7 +36,7 @@ | |||
private volatile Producers producers; | |||
|
|||
public ProducersManager(KafkaFactory kafkaFactory, KeyTransformer keyTransformer, ValueTransformer valueTransformer, | |||
List<SubscriberConfig> configs, Serializer serializer) { | |||
List<com.epam.lagerta.kafka.config.SubscriberConfig> configs, Serializer serializer) { |
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.
Why fully qualified name?
@@ -41,7 +41,7 @@ | |||
private final ValueTransformer valueTransformer; | |||
private final Serializer serializer; | |||
|
|||
public TransactionalKafkaProducerImpl(SubscriberConfig subscriberConfig, KafkaFactory kafkaFactory, | |||
public TransactionalKafkaProducerImpl(com.epam.lagerta.kafka.config.SubscriberConfig subscriberConfig, KafkaFactory kafkaFactory, |
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.
Why fully qualified name?
private final String gapTopic; | ||
private final Properties producerConfig; | ||
|
||
public SubscriberConfig(String subscriberId, boolean suspendAllowed, String inputTopic, String reconciliationTopic, String gapTopic, Properties producerConfig) { |
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.
Probably better to shift variable type to new line too
<bean id="data-recovery-config" class="com.epam.lagerta.kafka.DataRecoveryConfig" | ||
p:reconciliationTopic="reconciliation"/> | ||
p:reconciliationTopic="recon" | ||
p:gapTopic="reconciliation" |
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.
Maybe rename this topic in tests to not confuse with "recon" one?
@@ -67,10 +67,10 @@ | |||
|
|||
<bean id="reconciler" class="com.epam.lagerta.mocks.ProxyReconciler"> | |||
<constructor-arg> | |||
<!--todo--> |
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.
Empty todo?
@Override | ||
@SuppressWarnings("unchecked") | ||
public Future<RecordMetadata> commitTransaction(long transactionId) { | ||
int partition = 0; |
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.
Why not make this a constant?
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.
It is not my code. It was moved from original class
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.
Can you add a todo here? So it will be then a part of a later ticket oriented on todo cleanup.
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.
added todo and #208
consumer = kafkaFactory.consumer(dataRecoveryConfig.getConsumerConfig()); | ||
private GapFixer() { | ||
producer = kafkaFactory.producer(clusterConfig.getKafkaConfig().getProducerConfig()); | ||
consumer = kafkaFactory.consumer(clusterConfig.getKafkaConfig().getConsumerConfig(GAP_FIX_ID + UUID.randomUUID())); |
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.
Do we need unique gap fix group id for each GapFixer?
fixed #195