Skip to content

Mongo range queries: setup and KVTable implementations#251

Closed
ableegoldman wants to merge 2 commits intomainfrom
MONGO-KV-range-queries-without-partition
Closed

Mongo range queries: setup and KVTable implementations#251
ableegoldman wants to merge 2 commits intomainfrom
MONGO-KV-range-queries-without-partition

Conversation

@ableegoldman
Copy link
Contributor

This PR includes the basic setup for our approach to range queries via client-side filtering based on a partitioner, as well as the implementation for KV stores. The window range queries are in a separate PR since they're a bit more involved.

final Admin admin,
final CollectionCreationOptions collectionCreationOptions
) {
final int numPartitions = numPartitionsForKafkaTopic(admin, changelogTopicName);
Copy link
Contributor

@agavra agavra Feb 27, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

piping the changelog topic name and the admin all the way down here just to get the number of partitions (which is then used to build a partitioner) seems to be leaking a lot of unnecessary information

instead I suggest that we put the partitioner itself in the RemoteTableSpec interface and pass the partitioner directly into this

FWIW this is also closer to your TODO which allows use for a custom partitioner.

@ableegoldman
Copy link
Contributor Author

closing this since it was implemented in #347

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants