Mortom123 commented on issue #21069:
URL: https://github.com/apache/pulsar/issues/21069#issuecomment-1696758801

   @shibd thanks a lot. I will try later today using your recommended approach.
   
   On a side note, I would like to point out that the documentation regarding 
connectors does not  contain a section about configuration loading. However It 
recommend checking out kafkasource for more information. 
https://pulsar.apache.org/docs/3.1.x/io-develop/
   
https://github.com/apache/pulsar/blob/master/pulsar-io/kafka/src/main/java/org/apache/pulsar/io/kafka/KafkaAbstractSource.java
   The repo also contains an example configuration:
   
https://github.com/apache/pulsar/blob/master/pulsar-io/kafka/src/main/java/org/apache/pulsar/io/kafka/KafkaSourceConfig.java
   which uses the ObjectMapper for Marshalling.
   To prevent other people from having this issue, some clarification might be 
needed there.
   
   And one last quick question, maybe you know how to proceed. I'm also 
planning to integration test my connectors. The documentation recommends using 
testcontainers and links to:
   
https://github.com/apache/pulsar/tree/master//tests/integration/src/test/java/org/apache/pulsar/tests/integration/io
   The tests there all inherit from some common ancestor, which I would like 
not having to reimplement. Trying to load this test library into my project 
fails, because while the test library itself is present in maven, the parent 
POM of it (tests-parent) is not 
(https://mvnrepository.com/artifact/org.apache.pulsar.tests). Is there a reason 
why the child is available and the parent is not, making the child effectively 
unusable? Or is there another, better way of doing integration tests, without 
having to write everything from scratch? 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to