Skip to content

Ability use different consume and produce types for the key and value #175

Closed

Description

@BDeus

I don't think it's possible to use ParallelStreamProcessor with Consumer and Producer that do not share the same KeyType and ValueType.
Can this be considered in the future ?

Activity

  1. astubbs commented on Oct 19, 2021

    @astubbs
    Contributor

    Oh my! Yes! This is a breaking issue for the poll and produce use case. I will look into it with priority. Too much testing with just String types :)

  2. BDeus commented on Jan 31, 2022

    @BDeus
    Author

    Hi,
    i see that you remove the blocker label.
    Do you think the 1.0 version won't break after the implementation of the fix ?

  3. astubbs commented on Feb 1, 2022

    @astubbs
    Contributor

    i see that you remove the blocker label.

    Whoops - mistake :) Still plan on changing this. Will be resuming work on PC this week :)

  4. astubbs commented on Apr 12, 2022

    @astubbs
    Contributor

    Btw, workaround is to use your own instance of a producer to send a result back to Kafka, of any type.

  5. astubbs commented on Apr 12, 2022

    @astubbs
    Contributor

    Or use a more abstract type for your registered serde like a byte serde or string serde and use the serdes manually.

  6. changed the title [-]Ability to use ParallelStreamProcessor with different consume and produce types[/-] [+]Ability use different consume and produce types for the key and value[/+] on Aug 2, 2022
  7. johnbyrnejb commented on Jul 7, 2023

    @johnbyrnejb
    Contributor

    Closing Issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions