Re: StreamsConfig.DEFAULT_PRODUCTION_EXCEPTION_HANDLER_CLASS_CONFIG
You can find the release plan for 2.0 here:
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=80448820
Beside, as Matthias mentioned you can still work around it as of now by
hard-coding the string values in your app:
props.put("default.deserialization.exception.handler", ...)
Guozhang
On Fri, Jun 1, 2018 at 4:03 AM, Sumit Baurai
wrote:
> Thanks Guozhang !!
>
> Any idea when would that be?
>
> *Sumit*
>
> On 31 May 2018 at 16:48, Guozhang Wang wrote:
>
> > Hello Sumit,
> >
> > We are going to release 2.0 soon which should contain this fix:
> > https://issues.apache.org/jira/browse/KAFKA-6825
> >
> > I'm going to cherry-pick it into 1.1 as well so that for the coming
> bug-fix
> > release 1.1.1 it will also contain this.
> >
> >
> > Guozhang
> >
> > On Thu, May 31, 2018 at 5:48 AM, Sumit Baurai >
> > wrote:
> >
> > > Hi,
> > >
> > > I am trying to use the default production exception handler. I am
> > managing
> > > all my dependencies using Maven. Following are the co-ordinates that I
> am
> > > using :
> > >
> > >
> > > org.apache.kafka
> > > kafka-streams
> > > 1.1.0
> > >
> > >
> > > org.apache.kafka
> > > kafka-clients
> > > 1.1.0
> > >
> > >
> > > My Problem is that I am not able to use the property :
> > > StreamsConfig.DEFAULT_PRODUCTION_EXCEPTION_HANDLER_CLASS_CONFIG
> > > because this has been declared as "private".
> > >
> > > Upon going through the apache commit archives, I can see that this is
> > > resolved in the latest code base on github, but the jars on maven
> > > repositories are still not up to date.
> > >
> > > How can I overcome this limitation and use the latest codebase.
> > >
> > >
> > >
> > >
> > >
> > > *Sumit Baurai*Senior Consultant
> > > Architecture & Implementation
> > >
> > > +31 6 41 90 06 11 <+316%2041%2090%2006%2011>
> > > sumit.bau...@devoteam.com
> > >
> >
> >
> >
> > --
> > -- Guozhang
> >
>
--
-- Guozhang
Re: StreamsConfig.DEFAULT_PRODUCTION_EXCEPTION_HANDLER_CLASS_CONFIG
Thanks Guozhang !! Any idea when would that be? *Sumit* On 31 May 2018 at 16:48, Guozhang Wang wrote: > Hello Sumit, > > We are going to release 2.0 soon which should contain this fix: > https://issues.apache.org/jira/browse/KAFKA-6825 > > I'm going to cherry-pick it into 1.1 as well so that for the coming bug-fix > release 1.1.1 it will also contain this. > > > Guozhang > > On Thu, May 31, 2018 at 5:48 AM, Sumit Baurai > wrote: > > > Hi, > > > > I am trying to use the default production exception handler. I am > managing > > all my dependencies using Maven. Following are the co-ordinates that I am > > using : > > > > > > org.apache.kafka > > kafka-streams > > 1.1.0 > > > > > > org.apache.kafka > > kafka-clients > > 1.1.0 > > > > > > My Problem is that I am not able to use the property : > > StreamsConfig.DEFAULT_PRODUCTION_EXCEPTION_HANDLER_CLASS_CONFIG > > because this has been declared as "private". > > > > Upon going through the apache commit archives, I can see that this is > > resolved in the latest code base on github, but the jars on maven > > repositories are still not up to date. > > > > How can I overcome this limitation and use the latest codebase. > > > > > > > > > > > > *Sumit Baurai*Senior Consultant > > Architecture & Implementation > > > > +31 6 41 90 06 11 <+316%2041%2090%2006%2011> > > sumit.bau...@devoteam.com > > > > > > -- > -- Guozhang >
Re: StreamsConfig.DEFAULT_PRODUCTION_EXCEPTION_HANDLER_CLASS_CONFIG
As a workaround, you can specify the config just as a string directly:
props.put("default.deserialization.exception.handler", ...)
-Matthias
On 5/31/18 7:48 AM, Guozhang Wang wrote:
> Hello Sumit,
>
> We are going to release 2.0 soon which should contain this fix:
> https://issues.apache.org/jira/browse/KAFKA-6825
>
> I'm going to cherry-pick it into 1.1 as well so that for the coming bug-fix
> release 1.1.1 it will also contain this.
>
>
> Guozhang
>
> On Thu, May 31, 2018 at 5:48 AM, Sumit Baurai
> wrote:
>
>> Hi,
>>
>> I am trying to use the default production exception handler. I am managing
>> all my dependencies using Maven. Following are the co-ordinates that I am
>> using :
>>
>>
>> org.apache.kafka
>> kafka-streams
>> 1.1.0
>>
>>
>> org.apache.kafka
>> kafka-clients
>> 1.1.0
>>
>>
>> My Problem is that I am not able to use the property :
>> StreamsConfig.DEFAULT_PRODUCTION_EXCEPTION_HANDLER_CLASS_CONFIG
>> because this has been declared as "private".
>>
>> Upon going through the apache commit archives, I can see that this is
>> resolved in the latest code base on github, but the jars on maven
>> repositories are still not up to date.
>>
>> How can I overcome this limitation and use the latest codebase.
>>
>>
>>
>>
>>
>> *Sumit Baurai*Senior Consultant
>> Architecture & Implementation
>>
>> +31 6 41 90 06 11 <+316%2041%2090%2006%2011>
>> sumit.bau...@devoteam.com
>>
>
>
>
signature.asc
Description: OpenPGP digital signature
StreamsConfig.DEFAULT_PRODUCTION_EXCEPTION_HANDLER_CLASS_CONFIG
Hi, I am trying to use the default production exception handler. I am managing all my dependencies using Maven. Following are the co-ordinates that I am using : org.apache.kafka kafka-streams 1.1.0 org.apache.kafka kafka-clients 1.1.0 My Problem is that I am not able to use the property : StreamsConfig.DEFAULT_PRODUCTION_EXCEPTION_HANDLER_CLASS_CONFIG because this has been declared as "private". Upon going through the apache commit archives, I can see that this is resolved in the latest code base on github, but the jars on maven repositories are still not up to date. How can I overcome this limitation and use the latest codebase. *Sumit Baurai*Senior Consultant Architecture & Implementation +31 6 41 90 06 11 <+316%2041%2090%2006%2011> sumit.bau...@devoteam.com
