Hi Chris,
Thanks for your feedback!
1. Yes, it will be context-dependent. I have added rules and scenarios to
the nested notation to cover the happy path and edge cases. In short,
backticks will be not be considered as part of the field name when they are
wrapping a field name: first backtick at
Hi all,
I'd like to start a discussion thread on KIP-864: Add End-To-End Latency
Metrics to Connectors.
This KIP aims to improve the metrics available on Source and Sink
Connectors to measure end-to-end latency, including source and sink record
conversion time, and sink record e2e latency
Jorge Esteban Quilcate Otoya created KAFKA-14191:
Summary: Add end-to-end latency metrics to Connectors
Key: KAFKA-14191
URL: https://issues.apache.org/jira/browse/KAFKA-14191
Project
have worked nicely for them.
>
> Regards,
> Robert
>
> On Fri, Aug 12, 2022 at 10:01 AM Jorge Esteban Quilcate Otoya <
> quilcate.jo...@gmail.com> wrote:
>
> > Thanks Robert! And sorry for the late reply.
> >
> > That's a great catch and will require the current pro
such as root.`child.with.dot`. See Jsonata syntax for example:
> http://docs.jsonata.org/simple
>
> Robert
>
> On Wed, Jun 29, 2022 at 3:34 AM Jorge Esteban Quilcate Otoya <
> quilcate.jo...@gmail.com> wrote:
>
> > Thanks Chris! I have updated the KIP to include thi
Congratulations, Sophie!
On Tue, 2 Aug 2022, 23:26 Colin McCabe, wrote:
> Congratulations!
>
> best,
> Colin
>
>
> On Tue, Aug 2, 2022, at 12:09, Matthew Benedict de Detrich wrote:
> > Congratulations Sophie!
> >
> > --
> > Matthew de Detrich
> > Aiven Deutschland GmbH
> > Immanuelkirchstraße
Congratulations Chris!
On Mon, 25 Jul 2022 at 20:27, Robin Moffatt
wrote:
> Congrats Chris!
>
>
> --
>
> Robin Moffatt | Principal Developer Advocate | ro...@confluent.io | @rmoff
>
>
> On Mon, 25 Jul 2022 at 17:26, Mickael Maison wrote:
>
> > Hi all,
> >
> > The PMC for Apache Kafka has
>
> > I'll bump the vote thread as well to see if there's agreement on adding
> > this feature to Connect.
> >
> > Cheers,
> > Jorge.
> >
> > On Wed, 15 Jun 2022 at 23:02, Jorge Esteban Quilcate Otoya <
> > quilcate.jo...@gmail.com> wrote:
&g
and it looks good to me.
> >
> > I’m +1 (binding)
> >
> > Thanks,
> > John
> >
> > On Thu, Apr 21, 2022, at 09:10, Chris Egerton wrote:
> > > This is a worthwhile addition to the SMTs that ship out of the box with
> > > Kafka Connect. +1 non-binding
get delayed as a result.
>>
>> I'd be really curious to hear from Joshua and Tom on this front, though.
>> Is
>> it acceptable to move more incrementally here and settle on the syntax
>> version property as our means of introducing new features, or is it
>> prefe
le to implement things monolithically and try to get everything (or
> at least, as much as possible) right the first time?
>
> Thanks again for your continued effort on this KIP!
>
> Cheers,
>
> Chris
>
> On Wed, Jun 8, 2022 at 5:41 PM Jorge Esteban Quilcate Otoya <
>
an important part
> of Joshua's KIP and his feedback on this KIP; I think it's worth pursuing
> if we can.
>
My understanding from Joshua's feedback is that by including support for
deep-scan, we are already covering the recursive functionality. Though, I
may be missing something.
>
y-handed, is to
> change it to "field.syntax.version" with permitted values of "V1" (default,
> equivalent to "field.style = plain") and "V2" (equivalent to "field.style =
> nested"). This would leave us room in the future to make further chan
ath and have different escaping rules.
> An
> > > > alternative would be to come up with a parallel set of config names
> > (e.g.
> > > > as well as "field" an SMT might support "path") which were defined to
> > > > always take paths, thus av
Hi all,
I'd like to start a vote on KIP-821:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-821%3A+Connect+Transforms+support+for+nested+structures
Thanks,
Jorge
ine when it's in separate lines in the editor.
Hopefully, it's fixed now.
>
> Thanks again for working through this, and congratulations on a
> well-written KIP!
>
> Cheers,
>
> Chris
>
> On Tue, Apr 19, 2022 at 2:06 PM Jorge Esteban Quilcate Otoya <
> quilcate.
"on.missing.parent" and "on.existing.field"
> as the new property names for InsertField.
> - Why is the "on_existing_field" (or "on.existing.field") property only
> applied when the field style is nested? Couldn't it be useful for
> non-nested field
Yet another quick FYI.
While implementing KIP-820, we found that `api.MockProcessorContext` was
missing these new methods as well.
We added the new method to the new `api.MockProcessorContext` via
https://issues.apache.org/jira/browse/KAFKA-13654.
Please let us know if there are any concerns.
I
Jorge Esteban Quilcate Otoya created KAFKA-13822:
Summary: Update Kafka Streams Adjust Thread Count tests to new
Processor API
Key: KAFKA-13822
URL: https://issues.apache.org/jira/browse/KAFKA
Jorge Esteban Quilcate Otoya created KAFKA-13821:
Summary: Update Kafka Streams demo to new Processor API
Key: KAFKA-13821
URL: https://issues.apache.org/jira/browse/KAFKA-13821
be if any of the field elements
> specified with InsertField already exist in the record value? Will we just
> overwrite them? What's the behavior of InsertField today under similar
> circumstances?
>
The current behavior is to overwrite the value.
>
> Cheers,
>
> Chris
&
h maps as well.
> Can we update it to reflect this?
>
> References:
>
> [1] - https://stackoverflow.com/a/17808731
> [2] -
>
> https://github.com/apache/kafka/blob/7243facb8d69a7252e6b9556b5eaee13e41bab7f/connect/api/src/main/java/org/apache/kafka/connect/transforms/Transfor
s that involve, for
> example, a
> > > combination of the Flatten and Cast SMTs) is pretty high. I think this
> > > should be an opt-in feature, at least until the next major release. One
> > way
> > > we could accomplish this is by introducing a new "field.st
ecord` as
> value.
> >> - Extend `Record` to:
> >>- Implement `RecordMetadata` to expose `topic`, `partition`, and
> `offset`
> >> - Use `Headers` abstraction introduce on this KIP instead of core one
> >>
> >> KIP:
> >>
> https://c
lso include `final String...
> > stateStoreNames`.
> > >> And in javadocs explains that if users want to connect state stores to
> > this
> > >> processor, they could use the `connectState` API instead.
> > >>
> > >> Otherwise, I'm +1.
> >
[
https://issues.apache.org/jira/browse/KAFKA-13742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jorge Esteban Quilcate Otoya resolved KAFKA-13742.
--
Resolution: Not A Problem
Given that I got a better
[
https://issues.apache.org/jira/browse/KAFKA-13744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jorge Esteban Quilcate Otoya resolved KAFKA-13744.
--
Resolution: Not A Problem
> Quota metric t
FixedKeyProcessorContext
> - FixedKeyRecord
>
>
> -Matthias
>
>
> On 3/10/22 3:15 PM, Jorge Esteban Quilcate Otoya wrote:
> > Thanks all!
> >
> > I agree with Matthias and Jon on going forward with the new
> > `FixedKeyRecord` approach.
> > The KI
Jorge Esteban Quilcate Otoya created KAFKA-13744:
Summary: Quota metric tags are inconsistent
Key: KAFKA-13744
URL: https://issues.apache.org/jira/browse/KAFKA-13744
Project: Kafka
Jorge Esteban Quilcate Otoya created KAFKA-13742:
Summary: Quota byte-rate/request metrics are loaded only when at
least one quota is register
Key: KAFKA-13742
URL: https://issues.apache.org/jira
emind" (instead of say "enforce", since we cannot
> > really do it) users the semantics of "processValue". Personally I felt
> that
> > adding the new set of APIs for that purpose only is a bit overkill, and
> > hence was leaning towards just the runtime validati
nstraint.
>
> As I said, with this proposal, the devil is in the details,
> so if anyone thinks the API can be simplified, I suggest you
> check out the branch and try out your proposal. I'd be very
> happy to have a simplier solution, but I'm also pretty sure
> this complexity is
ngly prefer compile
> time checks and I am happy to extend the API surface area to achieve it
> -- however, I won't be surprised if others don't like this idea...
>
>
>
> -Matthias
>
> On 2/27/22 6:20 AM, Jorge Esteban Quilcate Otoya wrote:
> > Thanks, Guozhang.
> &g
like the `field.style` configuration flag approach.
Thanks for pointing out the `recursive` approach. Will add `nested` at the
moment, let's check the demand for `recursive` to consider it as part of
this or another KIP.
I have added the following on the KIP:
```
Future KIPs could extend this su
for those who
> mistakenly change the key, I think that enforcing everyone to `setValue`
> may incur more costs..
>
> Guozhang
>
> On Fri, Feb 25, 2022 at 12:54 PM Jorge Esteban Quilcate Otoya <
> quilcate.jo...@gmail.com> wrote:
>
> > Hi all,
> >
> > Appreciate
reciate
> Matthias
> > > > > extending the offer, but if Jorge doesn’t want to redesign the dsl
> right
> > > > > now, we’re better off just accepting the work he’s willing to do.
> > > > >
> > > > > Specifically, this KIP is quite a
eturn to have a single consolidated
> > ProcessorSupplier programming interface (i.e. we would eventually
> > deprecate ValueTransformerWithKeySupplier).
> >
> > On Wed, Feb 16, 2022 at 10:57 AM Jorge Esteban Quilcate Otoya <
> > quilcate.jo...@gmail.com> wrote:
>
fic comments, but I just wanted to mention I like the
> direction of
> >>> the KIP. My team is a big user of "transform" methods because of the
> >>> ability to chain them, and I have always found the terminology
> challenging
> >>> to
Hi all,
I'd like to start a vote on KIP-634 which proposes extending support for
Headers and Record Metadata in Kafka Streams
https://cwiki.apache.org/confluence/display/KAFKA/KIP-634%3A+Complementary+support+for+headers+and+record+metadata+in+Kafka+Streams+DSL
Thanks,
Jorge
Hi all,
I'd like to start a vote on KIP-820 which proposes extending KStream to use
the new Processor API
https://cwiki.apache.org/confluence/display/KAFKA/KIP-820%3A+Extend+KStream+process+with+new+Processor+API
Thanks,
Jorge
about just deprecating the KStream methods and not the
> > > Transform* interfaces is that you can keep your proposal just scoped to
> > > KStream and not have any consequences for the rest of the DSL.
> > >
> > > Thanks again,
> > > John
> >
ting the KStream methods and not the
> Transform* interfaces is that you can keep your proposal just scoped to
> KStream and not have any consequences for the rest of the DSL.
>
> Thanks again,
> John
>
> On Fri, Feb 11, 2022, at 06:43, Jorge Esteban Quilcate Otoya wrote:
> > Thanks, Jo
!
On Thu, 10 Feb 2022 at 13:15, Jorge Esteban Quilcate Otoya <
quilcate.jo...@gmail.com> wrote:
> > What do you think about instead adding topic and
> partition to Record?
>
> This is a very interesting idea. Forgot to consider this addition from
> KIP-478.
>
> `Reco
o the existing
> > > > transformers, by the way, that are also forbidden to forward
> > > > anything during punctuation.
> > > >
> > > > For what it's worth, I think this is the best tradeoff.
> > > >
> > > > The only alternative
t` have to be a public API? It seems to
> me
> > > > that this can be completely abstracted away from user interfaces as
> an
> > > > internal class, and we call the `setKey` before calling
> > user-instantiated
> > > > `process` function, and then in
> (or if we're using a default serde from the config), will
> Streams automatically wrap it downstream of the record-
> mapping operator?
>
> Otherwise, your proposal looks good to me!
>
> Thanks,
> -John
>
> On Tue, 2022-02-08 at 18:06 +, Jorge Esteban Quilcate
> Ot
Congratulations Luke!
On Thu, 10 Feb 2022 at 09:20, Bruno Cadonna wrote:
> Congrats, Luke! Very well deserved!
>
> Best,
> Bruno
>
> On 10.02.22 09:20, Manikumar wrote:
> > Congrats Luke!
> >
> > On Thu, Feb 10, 2022 at 1:36 PM Mickael Maison >
> > wrote:
> >
> >> Congratulations Luke!
> >>
>
Jorge Esteban Quilcate Otoya created KAFKA-13662:
Summary: Migrate DeserializationExceptionHandler to latest
ProcessorContext API
Key: KAFKA-13662
URL: https://issues.apache.org/jira/browse/KAFKA
more efficient.
> I'm not sure how much overhead it may incur to check if the key did not
> change: if it is just a reference equality check maybe it's okay. What's
> your take on this?
>
>
> Guozhang
>
> On Tue, Feb 8, 2022 at 5:17 AM Jorge Esteban Quilcate Otoya <
> quilc
Hi Dev team,
I'd like to start a new discussion thread on Kafka Connect KIP-821:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-821%3A+Connect+Transforms+support+for+nested+structures
This KIP is aimed to include support for nested structures on the existing
SMTs — where this make sense.
Jorge Esteban Quilcate Otoya created KAFKA-13656:
Summary: Connect Transforms support for nested structures
Key: KAFKA-13656
URL: https://issues.apache.org/jira/browse/KAFKA-13656
/pull/10265/files for both
Processors backing changes on the KStream API.
- It is proposing to still extend `To` class for backwards compatibility.
Looking forward to your feedback.
Regards,
Jorge.
On Thu, 4 Mar 2021 at 18:38, Jorge Esteban Quilcate Otoya <
quilcate.jo...@gmail.com> wrote:
Hi Dev team,
I'd like to start a new discussion thread on Kafka Streams KIP-820:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-820%3A+Extend+KStream+process+with+new+Processor+API
This KIP is aimed to extend the current `KStream#process` API to return
output values that could be chained
Jorge Esteban Quilcate Otoya created KAFKA-13654:
Summary: Extend KStream process with new Processor API
Key: KAFKA-13654
URL: https://issues.apache.org/jira/browse/KAFKA-13654
Project
[
https://issues.apache.org/jira/browse/KAFKA-13117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jorge Esteban Quilcate Otoya resolved KAFKA-13117.
--
Resolution: Fixed
[https://github.com/apache/kafka/pull/11481
[
https://issues.apache.org/jira/browse/KAFKA-10543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jorge Esteban Quilcate Otoya resolved KAFKA-10543.
--
Resolution: Fixed
https://github.com/apache/kafka/pull/11412
Jorge Esteban Quilcate Otoya created KAFKA-13429:
Summary: Update gitignore to include new modules
Key: KAFKA-13429
URL: https://issues.apache.org/jira/browse/KAFKA-13429
Project
[
https://issues.apache.org/jira/browse/KAFKA-10540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jorge Esteban Quilcate Otoya resolved KAFKA-10540.
--
Resolution: Fixed
https://github.com/apache/kafka/pull/11315
[
https://issues.apache.org/jira/browse/KAFKA-10539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jorge Esteban Quilcate Otoya resolved KAFKA-10539.
--
Resolution: Fixed
https://github.com/apache/kafka/pull/11356
[
https://issues.apache.org/jira/browse/KAFKA-10544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jorge Esteban Quilcate Otoya resolved KAFKA-10544.
--
Resolution: Fixed
https://github.com/apache/kafka/pull/11316
[
https://issues.apache.org/jira/browse/KAFKA-10542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jorge Esteban Quilcate Otoya resolved KAFKA-10542.
--
Resolution: Fixed
https://github.com/apache/kafka/pull/11099
[
https://issues.apache.org/jira/browse/KAFKA-13201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jorge Esteban Quilcate Otoya resolved KAFKA-13201.
--
Resolution: Fixed
https://github.com/apache/kafka/pull/11213
Jorge Esteban Quilcate Otoya created KAFKA-13201:
Summary: Convert KTable suppress to new PAPI
Key: KAFKA-13201
URL: https://issues.apache.org/jira/browse/KAFKA-13201
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-10541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jorge Esteban Quilcate Otoya resolved KAFKA-10541.
--
Fix Version/s: 3.0.0
Assignee: John Roesler
[
https://issues.apache.org/jira/browse/KAFKA-10537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jorge Esteban Quilcate Otoya resolved KAFKA-10537.
--
Resolution: Fixed
https://github.com/apache/kafka/pull/10381
[
https://issues.apache.org/jira/browse/KAFKA-10538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jorge Esteban Quilcate Otoya resolved KAFKA-10538.
--
Resolution: Fixed
https://github.com/apache/kafka/pull/10381
Hi everyone,
Hope you are all well and safe.
I'd like to propose the following KIP:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-756%3A+Move+StreamsResetter+tool+outside+of+core
The goal is to move `StreamsResetter` tool outside of `core` module, and
allow Kafka Streams users to access
[
https://issues.apache.org/jira/browse/KAFKA-12536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jorge Esteban Quilcate Otoya resolved KAFKA-12536.
--
Fix Version/s: 3.0.0
Resolution: Fixed
> Add Inst
[
https://issues.apache.org/jira/browse/KAFKA-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jorge Esteban Quilcate Otoya resolved KAFKA-10434.
--
Resolution: Fixed
> Remove deprecated methods on WindowSt
[
https://issues.apache.org/jira/browse/KAFKA-12451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jorge Esteban Quilcate Otoya resolved KAFKA-12451.
--
Fix Version/s: 3.0.0
Resolution: Fixed
https
[
https://issues.apache.org/jira/browse/KAFKA-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jorge Esteban Quilcate Otoya resolved KAFKA-12450.
--
Fix Version/s: 3.0.0
Resolution: Fixed
> Rem
+1
Thanks Matthias!
On Thu, 15 Apr 2021, 20:48 Israel Ekpo, wrote:
> Makes perfect sense to me
>
> +1 as well.
>
> Thanks Matthias.
>
>
> On Thu, Apr 15, 2021 at 2:41 PM Guozhang Wang wrote:
>
> > +1 as well. Thanks!
> >
> > On Wed, Apr 14, 2021 at 4:30 PM Bill Bejeck wrote:
> >
> > > Thanks
[
https://issues.apache.org/jira/browse/KAFKA-12533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jorge Esteban Quilcate Otoya resolved KAFKA-12533.
--
Resolution: Duplicate
> Migrate KStream stateless operat
[
https://issues.apache.org/jira/browse/KAFKA-12532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jorge Esteban Quilcate Otoya resolved KAFKA-12532.
--
Resolution: Duplicate
> Migrate Stream operators to
Jorge Esteban Quilcate Otoya created KAFKA-12536:
Summary: Add Instant-based methods to ReadOnlySessionStore
Key: KAFKA-12536
URL: https://issues.apache.org/jira/browse/KAFKA-12536
Jorge Esteban Quilcate Otoya created KAFKA-12533:
Summary: Migrate KStream stateless operators to new Processor API
Key: KAFKA-12533
URL: https://issues.apache.org/jira/browse/KAFKA-12533
Jorge Esteban Quilcate Otoya created KAFKA-12532:
Summary: Migrate Stream operators to new Processor API
Key: KAFKA-12532
URL: https://issues.apache.org/jira/browse/KAFKA-12532
Project
gt;
> > > I’m +1 (binding)
> > >
> > > -John
> > >
> > > On Mon, Sep 21, 2020, at 12:35, Sophie Blee-Goldman wrote:
> > >> Thanks for pointing out the vote in the discussion thread, this email
> > >> somehow skipped my inbox ¯\_(ツ
Jorge Esteban Quilcate Otoya created KAFKA-12450:
Summary: Remove deprecated methods from ReadOnlyWindowStore
Key: KAFKA-12450
URL: https://issues.apache.org/jira/browse/KAFKA-12450
Jorge Esteban Quilcate Otoya created KAFKA-12451:
Summary: Remove deprecation annotation on long-based read
operations in WindowStore
Key: KAFKA-12451
URL: https://issues.apache.org/jira/browse
Jorge Esteban Quilcate Otoya created KAFKA-12449:
Summary: Remove deprecated WindowStore#put
Key: KAFKA-12449
URL: https://issues.apache.org/jira/browse/KAFKA-12449
Project: Kafka
+Streams+DSL
Looking forward to your feedback,
Cheers and stay safe,
Jorge.
On Thu, Oct 29, 2020 at 12:33 AM Jorge Esteban Quilcate Otoya <
quilcate.jo...@gmail.com> wrote:
> Thanks Sophie! Haven't followed KIP-478 but sounds great.
> I'll be happy to help on that migration to
Jorge Esteban Quilcate Otoya created KAFKA-12287:
Summary: Add WARN logging on consumer-groups when reset-offsets by
timestamp or duration can't find an offset and defaults to latest.
Key: KAFKA-12287
Hi all,
My 2c:
Pros of "Produce":
- Same as Kafka Protocol "ProduceRequest" and simple enough
"producer#produce()"; though consumer also differ between "FetchRequest"
and "consumer#poll".
- As reference, other libraries also use "produce", e.g.:
librdkafka-derived libraries:
all
> DSL operators
> to the new PAPI before adding header support for those operators. But that
> definitely
> sounds achievable here
>
> On Wed, Oct 28, 2020 at 11:10 AM Jorge Esteban Quilcate Otoya <
> quilcate.jo...@gmail.com> wrote:
>
> > Hi Matt
an `Iterable` similar to `ProducerRecord`)? We could either
> add it to your KIP or do a new KIP just for the PAPI.
>
> Thoughts?
>
>
> -Matthias
>
> On 7/16/20 4:05 PM, Jorge Esteban Quilcate Otoya wrote:
> > Hi everyone,
> >
> > Bumping this thread to c
Congratulations Sophie!! So well deserved.
On Mon, Oct 19, 2020 at 6:31 PM Bill Bejeck wrote:
> Congratulations Sophie!
>
> -Bill
>
> On Mon, Oct 19, 2020 at 12:49 PM Leah Thomas wrote:
>
> > Congrats Sophie!
> >
> > On Mon, Oct 19, 2020 at 11:41 AM Matthias J. Sax
> wrote:
> >
> > > Hi all,
reviewed the KIP, and it looks good to
> me.
>
> Thanks,
> John
>
> On Tue, Sep 1, 2020, at 12:35, Jorge Esteban Quilcate Otoya wrote:
> > Thanks Sophie!
> >
> > > one nit: you missed updating the startTime long to Instant in both
> > appearances of t
m +1 (binding) for doing this in
> 3.0.
>
> Thanks,
> -John
>
> On Mon, 2020-09-07 at 12:18 +0100, Jorge Esteban Quilcate
> Otoya wrote:
> > Hi everyone,
> >
> > I'd like to start a thread to vote for KIP-667 and fix deprecation notes
> on
> > ReadOnlyWindowSt
Hi everyone,
I'd like to start a thread to vote for KIP-667 and fix deprecation notes on
ReadOnlyWindowStore:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-667%3A+Remove+deprecated+methods+from+ReadOnlyWindowStore
Discussion thread:
Hi everyone,
I'd like to start a thread to vote for KIP-666 and align instant-based
operations on Interactive Query APIs between Window and Session stores:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-666%3A+Add+Instant-based+methods+to+ReadOnlySessionStore
Discussion thread:
Jorge Esteban Quilcate Otoya created KAFKA-10459:
Summary: Document IQ APIs where order does not hold between stores
Key: KAFKA-10459
URL: https://issues.apache.org/jira/browse/KAFKA-10459
WindowStore methods, and provide a default
> implementation
> on the SessionStore interface which then just calls the corresponding
> long-based method.
> WDYT?
>
> -Sophie
>
> On Fri, Aug 28, 2020 at 11:31 AM Jorge Esteban Quilcate Otoya <
> quilcate.jo...@gmai
Hi everyone,
I'd like to discuss the following proposal to align IQ Session Store API
with the Window Store one.
https://cwiki.apache.org/confluence/display/KAFKA/KIP-666%3A+Add+Instant-based+methods+to+ReadOnlySessionStore
Looking forward to your feedback.
Cheers,
Jorge.
Hi everyone,
I'd like to propose these changes to the Window Store API.
https://cwiki.apache.org/confluence/display/KAFKA/KIP-667%3A+Remove+deprecated+methods+from+ReadOnlyWindowStore
As these changes involve removing deprecated methods, this KIP is targeting
the next major release v3.0.
Jorge Esteban Quilcate Otoya created KAFKA-10445:
Summary: Align IQ SessionStore API with Instant-based methods as
ReadOnlyWindowStore
Key: KAFKA-10445
URL: https://issues.apache.org/jira/browse
Jorge Esteban Quilcate Otoya created KAFKA-10434:
Summary: Remove deprecated methods on WindowStore
Key: KAFKA-10434
URL: https://issues.apache.org/jira/browse/KAFKA-10434
Project
Jorge Esteban Quilcate Otoya created KAFKA-10409:
Summary: Refactor Kafka Streams RocksDb iterators
Key: KAFKA-10409
URL: https://issues.apache.org/jira/browse/KAFKA-10409
Project
+1 (non-binding).
Thanks John!
On Wed, Jul 29, 2020 at 3:00 PM Navinder Brar
wrote:
> +1 (non-binding). Thanks John, looks good to me.
>
> ~NavinderOn Wednesday, 29 July, 2020, 04:32:25 am IST, John Thomas <
> johnthote...@live.com> wrote:
>
> Hello everyone,
>
> I'd like to kick-off a
Thanks Leah!
This will be a great addition.
+1 (non-binding)
Very happy that KIP-617 is being used already :D
Cheers,
Jorge.
On Wed, Jul 29, 2020 at 2:28 PM John Roesler wrote:
> Thanks for the awesome KIP, Leah,
>
> I’m +1 (binding)
>
> Thanks,
> John
>
> On Tue, Jul 28, 2020, at 19:10,
101 - 200 of 297 matches
Mail list logo
