Re: [JmsIO] => Pull Request to fix message acknowledgement issue

2022-09-26 Thread BALLADA Vincent via dev
De : Luke Cwik Date : jeudi, 8 septembre 2022 à 19:17 À : BALLADA Vincent Cc : dev@beam.apache.org Objet : Re: [JmsIO] => Pull Request to fix message acknowledgement issue [vwP6KQExYeP8ewASUVORK5CYII=] [EXT] Could we have more than one active checkpoint per reader instance? Yes. Read

Re: [JmsIO] => Pull Request to fix message acknowledgement issue

2022-09-08 Thread BALLADA Vincent
all the checkpoint marks to be finalized. What do you think? On Mon, Aug 29, 2022 at 10:06 PM Jean-Baptiste Onofré mailto:j...@nanthrax.net>> wrote: Hi Vincent, thanks, I will take a look (as original JmsIO author ;)). Regards JB On Mon, Aug 29, 2022 at 6:43 PM BALLADA Vincent mailto:vin

[JmsIO] => Pull Request to fix message acknowledgement issue

2022-08-29 Thread BALLADA Vincent
Hi all, Here is a PR related to the following issue (Runner acknowledges messages on closed session): https://github.com/apache/beam/issues/20814 And here is a documentation explaining the fix: https://docs.google.com/document/d/19HiNPoJeIlzCFyWGdlw7WEFutceL2AmN_5Z0Vmi1s-I/edit?usp=sharing And

Re: [Proposal] => JMSIO dynamic topic publishing

2022-02-24 Thread BALLADA Vincent
Thu, Feb 24, 2022 at 3:42 PM BALLADA Vincent wrote: > > Hi Jean François > > > > Please to hear of the author of JmsIO . > > Many thanks for your suggestion. > > JmsRecord is used at read time, in most use cases we will use a mapper to > provide an obj

Re: [Proposal] => JMSIO dynamic topic publishing

2022-02-24 Thread BALLADA Vincent
ing explicit) but defining the destination on the JmsRecord. If the JmsRecord contains the destination (that could be "dynamic"), we use it, overriding the destination provided on the IO configuration. Thoughts ? Regards JB NB: I'm the original author of JmsIO ;) On Fri, Feb 18, 2022 at 7:

[Proposal] => JMSIO dynamic topic publishing

2022-02-18 Thread BALLADA Vincent
Hi all Here is a proposal to implement the ability to publish on dynamic topics with JMSIO: https://docs.google.com/document/d/1IY4_e5g1g71XvTLL4slHRyVfX7ByiwjD_de3WGsBQXg/edit?usp=sharing There is also a JIRA issue: https://issues.apache.org/jira/browse/BEAM-13608 Best regards Vincent

Re: [Proposal] => JmsIO auto scaling feature

2021-09-07 Thread BALLADA Vincent
interface. I will proceed with the pull request then. Best regards. Vincent BALLADA On 2021/07/19 16:26:09, BALLADA Vincent mailto:v...@renault.com>> wrote: > Thanks, I enabled comment access.> > > De : Luke Cwik mailto:lc...@google.com>>> > Date : lundi, 19 j

Re: [Proposal] => JmsIO auto scaling feature

2021-07-19 Thread BALLADA Vincent
Thanks, I enabled comment access. De : Luke Cwik Date : lundi, 19 juillet 2021 à 17:20 À : dev Objet : Re: [Proposal] => JmsIO auto scaling feature Would you enable comment access on your doc? On Mon, Jul 19, 2021 at 6:08 AM BALLADA Vincent mailto:vincent.ball...@renault.com>> wrot

[Proposal] => JmsIO auto scaling feature

2021-07-19 Thread BALLADA Vincent
Hi, I am Vincent from Renault Digital. We are using JmsIO connector within our organization, and we are facing the following issue: A lot of our company dataflow jobs use JmsIO connector, as our message bus widely use AMQP protocol. JmsIO doesn't implement the getSplitBacklogBytes nor

Contributor permission for Beam JIRA tickets

2021-07-19 Thread BALLADA Vincent
Hi, This is Vincent from Renault Digital. We are widely using JmsIO connector with Dataflow runner within our organization, Can someone add me as a contributor for Beam’s JIRA issue tracker? I would like to create/assign tickets for my work. Thanks, Vincent BALLADA Confidential C --