Hello Bill, am implementing the TimestampExtractor Interface, then using it to consume, like:
*final* KStream<..., ...> events = builder.stream(inputTopicList, Consumed. *with*(keySerde, valueSerde).withTimestampExtractor(*new *OwnTimeExtractor( ...))); Am not setting the default.timestamp.extractor config value. Cheers! -- Jonathan On Wed, Jun 26, 2019 at 3:16 PM Bill Bejeck <b...@confluent.io> wrote: > Hi Jonathan, > > Thanks for reporting this. Which timestamp extractor are you using in the > configs? > > Thanks, > Bill > > On Wed, Jun 26, 2019 at 9:14 AM Jonathan Santilli < > jonathansanti...@gmail.com> wrote: > > > Hello, hope you all are doing well, > > > > am testing the new version 2.3 for Kafka Streams specifically. I have > > noticed that now, the implementation of the method extract from the > > interface org.apache.kafka.streams.processor.TimestampExtractor > > > > *public* *long* extract(ConsumerRecord<Object, Object> record, *long* > > previousTimestamp) > > > > > > is always returning -1 as value. > > > > > > Previous version 2.2.1 was returning the correct value for the record > > partition. > > > > Am aware the interface is market as @InterfaceStability.Evolving and we > > should not rely on the stability/compatibility. Am just wondering if that > > new behavior is intentional or is a bug. > > > > > > Cheers! > > -- > > Santilli Jonathan > > > -- Santilli Jonathan
