Bill, Fixed, thank you!
Regards, Jose On Tue, 9 Apr 2019 at 15:55, Bill Bejeck <b...@confluent.io> wrote: > Jose, > > I can see you listed as a contributor, can you try logging out and logging > back in? > > Thanks > Bill > > On Tue, Apr 9, 2019 at 7:27 AM Jose Lopez <joseariaslo...@gmail.com> > wrote: > > > Bill, > > > > Could you please double check? It seems I cannot assign the issue to me > > yet. > > > > Regards, > > Jose > > > > On Mon, 8 Apr 2019 at 23:24, Bill Bejeck <b...@confluent.io> wrote: > > > > > Jose, > > > > > > You're all set. I look forward to your PR. > > > > > > Thanks, > > > Bill > > > > > > On Mon, Apr 8, 2019 at 4:59 PM Jose Lopez <joseariaslo...@gmail.com> > > > wrote: > > > > > > > Bill, > > > > > > > > Thank you again for your help. > > > > > > > > I am happy to give it a try. My Jira username is JoseLopez, could you > > > > please get me added as a contributor? > > > > > > > > Regards, > > > > Jose > > > > > > > > On Mon, 8 Apr 2019 at 18:28, Bill Bejeck <b...@confluent.io> wrote: > > > > > > > > > Jose, > > > > > > > > > > If you'd like to take a swing at fixing this, by all means, assign > > the > > > > Jira > > > > > ticket to yourself and submit a PR. > > > > > > > > > > If you don't have an Apache Jira account, sign up for one and list > > your > > > > > jira userid here and I'll get you added as a contributor. > > > > > > > > > > Thanks, > > > > > Bill > > > > > > > > > > On Mon, Apr 8, 2019 at 11:52 AM Jose Lopez < > joseariaslo...@gmail.com > > > > > > > > wrote: > > > > > > > > > > > Thank you for the prompt response, Bill. > > > > > > > > > > > > Do you have an estimated date as to when this could be fixed? Are > > you > > > > > open > > > > > > to new developers / collaborators? > > > > > > > > > > > > Regards, > > > > > > Jose > > > > > > > > > > > > On Mon, 8 Apr 2019 at 17:06, Bill Bejeck <b...@confluent.io> > > wrote: > > > > > > > > > > > > > Jose, > > > > > > > > > > > > > > Thanks for reporting this we have created this Jira > > > > > > > https://issues.apache.org/jira/browse/KAFKA-8199 for tracking > > the > > > > > issue. > > > > > > > > > > > > > > -Bill > > > > > > > > > > > > > > On Mon, Apr 8, 2019 at 5:49 AM Jose Lopez < > > > joseariaslo...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > > > > > My topology is: > > > > > > > > > > > > > > > > stream -> groupByKey -> windowedBy -> count -> suppress -> > > > groupBy > > > > -> > > > > > > > > aggregate -> toStream > > > > > > > > > > > > > > > > When I *groupBy* after *suppress*, the following exception is > > > > thrown: > > > > > > > > > > > > > > > > java.lang.ClassCastException: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > org.apache.kafka.streams.kstream.internals.KTableImpl$$Lambda$15/1208825205 > > > > > > > > cannot be cast to > > > > > > > > > > > org.apache.kafka.streams.kstream.internals.KTableProcessorSupplier > > > > > > > > > > > > > > > > It happens because suppress returns a KtableImpl with a > > > > > > > > KTableSuppressProcessor. Then groupBy, when > > > > > > > > executes enableSendingOldValues(), it casts it to > > > > > > > KTableProcessorSupplier, > > > > > > > > and therefore the ClassCastException. > > > > > > > > > > > > > > > > Is this a bug? Am I missing something? > > > > > > > > > > > > > > > > Thank you in advance for your help. > > > > > > > > > > > > > > > > Regards, > > > > > > > > Jose > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
