Consider adding support for TableView #503

Activity

1. onobc

   added

   type: featureA new feature or enhacementA new feature or enhacement

   on Nov 23, 2023
2. onobc

   added this to the Backlog milestone on Jan 17, 2024
3. jonas-grgt commented on Feb 7, 2024

   

   jonas-grgt

   on Feb 7, 2024

   Contributor

   More actions

   One could expose a TableView as a bean as such:

   @Bean
   TableView<User> userTableView(PulsarClient pulsarClient) {
     try {
       return pulsarClient
   	    .newTableView(Schema.AVRO(User.class))
   	    .topic("persistent://public/default/user")
   	    .autoUpdatePartitionsInterval(10, TimeUnit.SECONDS)
   	    .create();
     }
     catch (PulsarClientException e) {
       throw new RuntimeException(e);
     }
   }

   A TableViewFactory like Consumer-and-Producer-Factory could be provided to facilitate in creating TableViews:

   pulsarTableViewFactory.createTableView("persistent://public/default/user", Schema.AVRO(User.class));

   The TableViewFactory could internally rely on Customizers and let them be overridden if specific Customizers are passed in the createTableView method.
4. onobc commented on Feb 7, 2024

   

   onobc

   on Feb 7, 2024

   ContributorAuthor

   More actions

   That sounds like a good approach @jonasgeiregat
5. jonas-grgt commented on Feb 11, 2024

   

   jonas-grgt

   on Feb 11, 2024

   Last edited by jonas-grgt

   Contributor

   More actions

   Contemplated on this a bit more and came up with another design in the line of @PulsarMessage

   @PulsarTableView(topic = "${topic.name}", ...)
   class CustomType {
   }

   This would expose a pulsar TableView<CustomType> as a bean.
6. sharanggupta commented on Oct 15, 2026

   

   sharanggupta

   on Oct 15, 2026

   More actions

   I have opened #1559 for this. It adds the PulsarTableViewFactory discussed above, in the shape of the PulsarReaderFactory: DefaultPulsarTableViewFactory applies the TableViewBuilderCustomizers of its default configuration, then the topic (qualified with the PulsarTopicBuilder when one is set) and the customizers of the call, and wraps a PulsarClientException in a PulsarException. I left the @PulsarTableView annotation out, since the factory is the piece the rest builds on. If it goes in, I can follow up in Spring Boot with the factory bean and spring.pulsar.table-view.* defaults.