Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Clement Escoffier
    @cescoffier
    I can’t remember when it landed. Something like February.
    Ken Finnigan
    @kenfinnigan
    Initially, but we’re changing and amending it still. So it’s not stable yet
    Emily Jiang
    @Emily-Jiang

    Forgot about one feature too: metadata propagation

    It was discussed just before we stopped the calls. We could leave this feauture out for RC1. Which approach did you take eventually to propagate the metadata @cescoffier

    Clement Escoffier
    @cescoffier
    Metadata attached to Messages and propagated from message to message.
    Emily Jiang
    @Emily-Jiang

    Metadata attached to Messages and propagated from message to message.

    I like it. This approach is much simplier than the CDI context approach.

    I linked to this issue #72
    Emily Jiang
    @Emily-Jiang

    SnallRye intends to have a period of at least 6 months before we propose anything to an MP spec for entirely new features and APIs. We need that usage and bake time to ensure the API being proposed is appropriate and usable by developers

    I think it is ok to wait for some time if you want to propose the features from SmallRye. However, for solving dead urgent issues in MP RM, I don't think we have to wait at least 6 months. I hope this is not what you meant. Just thought to check. In my context, I was talking about the issues on MP RM not proactively sync up or promote SmallRye features.

    Ken Finnigan
    @kenfinnigan
    It depends. If the features you want to add to MP RM aren’t implemented anywhere and would be new APIs, then yes they would need to be implemented somewhere for a period of time first
    Emily Jiang
    @Emily-Jiang
    I think for issues, we should look at them case by case. For something we are unsure, we will have to test it out first. My understanding is that before a spec can be released, obviously the apis need to be implemented. IIUC, even for implementation first argument is applicable to new spec proposal not down to the issue level.
    Ken Finnigan
    @kenfinnigan
    Not true. It very much applies to issues that require new APIs to be created
    That’s the whole point. Otherwise we’re creating APIs with no idea if it’s appropriate or not
    Emily Jiang
    @Emily-Jiang
    I think this is the latest conversation on the implementation first discussion (https://groups.google.com/d/msg/microprofile/G5WZvF0wZuY/mBMYN5eEAwAJ).
    Ken Finnigan
    @kenfinnigan
    It's been a discussion that goes in circles.
    We would not want to see anything added to MP Reactive Streams spec that hasn't been proven in an implementation first
    Emily Jiang
    @Emily-Jiang
    eclipse/microprofile-reactive-messaging#100 @cescoffier please take a look which should fix up the javadoc with @Outgoing. Then we are in the position to do a 1.1-RC1
    Clement Escoffier
    @cescoffier
    Done and merged!
    Emily Jiang
    @Emily-Jiang
    thanks @cescoffier !
    Emily Jiang
    @Emily-Jiang
    I am looking to prep for RC1 release of both Reactive Streams operators and Reactive Messaging. For the former, there are a couple of issues needed to be fixed prior to the RC1 (Jakarta EE8 alignment and dependency scope). There are many untriaged issues. I am wondering whether we need to have a one-off meeting either next week or weekafter to discuss the PRs and decide whether we want do a quick fix or not. Thoughts?
    Clement Escoffier
    @cescoffier
    fine for me. I’ve looked at the issues, some are breaking changes.
    Emily Jiang
    @Emily-Jiang
    Thanks @cescoffier ! I'll create a doodle poll and post here to find a convenient slot.
    Clement Escoffier
    @cescoffier
    great!
    Emily Jiang
    @Emily-Jiang
    @cescoffier
    Clement Escoffier
    @cescoffier
    @Emily-Jiang Wrong week unfortunately, I’m in PTO from Wed to Fri and can’t on tuesday. Also, Julien Ponge (involved in Mutiny) is in PTO this week too. Can you extend it to next week?
    Emily Jiang
    @Emily-Jiang
    @cescoffier Have a relaxing week! I have done a new doodle https://doodle.com/poll/4nf9ta9kpxec54xn for the following week.
    Clement Escoffier
    @cescoffier
    Thanks @Emily-Jiang !
    Ken Finnigan
    @kenfinnigan
    @Emily-Jiang you should advertise the poll on the mailing list to ensure everyone is aware and has an opportunity to respond
    Emily Jiang
    @Emily-Jiang
    will do. Thanks @kenfinnigan!
    Emily Jiang
    @Emily-Jiang
    According to doodle pool, the most popular choice is this Wednesday. I have created the slot on MicroProfile Calendar https://calendar.google.com/calendar/embed?src=gbnbc373ga40n0tvbl88nkc3r4%40group.calendar.google.com @cescoffier
    Emily Jiang
    @Emily-Jiang
    MP Reactive call is in 30mins. See you there
    Clement Escoffier
    @cescoffier
    @Emily-Jiang do we have a call today? I’ve nothing in the calendar
    But I’m available
    Emily Jiang
    @Emily-Jiang
    nope. How about having a call next week to go through the issues and milestone so that RC1 release can be started? Is it ok @cescoffier ?
    Clement Escoffier
    @cescoffier
    Should be fine, please send an invite
    Emily Jiang
    @Emily-Jiang
    I'll add to the MP calendar
    Emily Jiang
    @Emily-Jiang
    @cescoffier meeting time
    Andrew Rouse
    @Azquelt
    I have a few PRs on the operators repo which were opened a while ago. I think they're all small things which should be easy to check: #149 #152 #153
    Jacopo Rota
    @r00ta
    Hi! I have a quick question: I see that if a topic does not exist, the consumer does not automatically create it (only the producer does it). If this behaviour is by design, what is the reason behind that?
    Clement Escoffier
    @cescoffier
    It depends on the connector. I believe you refer to kafka. In this case it depends on the kafka broker config. In real deployment the topics must be created beforehand. The smallrye kafka connector indicates an unhealthy state (readiness check) in this case.
    Jacopo Rota
    @r00ta
    Hi @cescoffier , thanks for the fast response. Yes I'm refering to kafka, and I'm facing exactly what you pointed out. I'm not 100% sure, but until few months ago also the consumer was creating the topic right?
    Clement Escoffier
    @cescoffier
    Nope. It always depended on the broker config: If the broker automatically creates the topic or not.
    Jacopo Rota
    @r00ta
    Understood, thank you very much!
    Emily Jiang
    @Emily-Jiang
    @cescoffier we need to release a new version of MP RM and RSO to depend on Config 2.0. Right?
    Clement Escoffier
    @cescoffier
    @Emily-Jiang oh yes…
    but I will start working on 2 new feature we can (finally) put in the spec
    namely, nack and metadata propagation
    Emily Jiang
    @Emily-Jiang
    okay
    Emily Jiang
    @Emily-Jiang
    With the successful release of 2.0-RC1 for RM and RSO, according to what @cescoffier said, SmallRye RM passed all TCKs. we can stage RM 2.0 and RSO 2.0 and kick off the release process. Any other thoughts?