You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Oleksandr Bondarenko (Jira)" <ji...@apache.org> on 2020/09/02 20:25:00 UTC
[jira] [Assigned] (KAFKA-10409) Refactor Kafka Streams RocksDb
iterators
[ https://issues.apache.org/jira/browse/KAFKA-10409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleksandr Bondarenko reassigned KAFKA-10409:
--------------------------------------------
Assignee: Oleksandr Bondarenko
> Refactor Kafka Streams RocksDb iterators
> -----------------------------------------
>
> Key: KAFKA-10409
> URL: https://issues.apache.org/jira/browse/KAFKA-10409
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Jorge Esteban Quilcate Otoya
> Assignee: Oleksandr Bondarenko
> Priority: Minor
> Labels: newbie
>
> From [https://github.com/apache/kafka/pull/9137#discussion_r470345513] :
> [~ableegoldman] :
> > Kind of unrelated, but WDYT about renaming {{RocksDBDualCFIterator}} to {{RocksDBDualCFAllIterator}} or something on the side? I feel like these iterators could be cleaned up a bit in general to be more understandable – for example, it's weird that we do the {{iterator#seek}}-ing in the actual {{all()}} method but for range queries we do the seeking inside the iterator constructor.
> and [https://github.com/apache/kafka/pull/9137#discussion_r470361726] :
> > Personally I found the {{RocksDBDualCFIterator}} logic a bit difficult to follow even before the reverse iteration, so it would be nice to have some tests specifically covering reverse iterators over multi-column-family timestamped stores
--
This message was sent by Atlassian Jira
(v8.3.4#803005)