Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: split geo and zset families #4421

Merged
merged 2 commits into from
Jan 8, 2025
Merged

chore: split geo and zset families #4421

merged 2 commits into from
Jan 8, 2025

Conversation

kostasrim
Copy link
Contributor

@kostasrim kostasrim commented Jan 7, 2025

I was longing for this change for some time now and I grabbed the opportunity since I already worked on #4420

  • Split geo family from zset family

I am not sure how I could reduce the size of the PR.

There are no functional changes only a refactor.

TODO for separate PR

  • Split zset family test to reflect the changes here
  • Maybe move the common functions from ZSetFamily:: to a separate file

@kostasrim kostasrim self-assigned this Jan 7, 2025
@kostasrim kostasrim requested review from adiholden and romange January 7, 2025 15:31
class GeoFamily {
public:
static void Register(CommandRegistry* registry);
using SinkReplyBuilder = facade::SinkReplyBuilder;
Copy link
Collaborator

Choose a reason for hiding this comment

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

I do not think you need it here, nor its declaration at line 12.

using SinkReplyBuilder = facade::SinkReplyBuilder;
template <typename T> using OpResult = facade::OpResult<T>;

static void ZAddGeneric(std::string_view key, const ZParams& zparams, ScoredMemberSpan memb_sp,
Copy link
Collaborator

Choose a reason for hiding this comment

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

what's the reason for exposing ZAddGeneric here?

Copy link
Collaborator

Choose a reason for hiding this comment

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

ah, i see.
please add a comment that it's being used in geo_family.cc code.

Copy link
Collaborator

@romange romange left a comment

Choose a reason for hiding this comment

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

lgtm

@kostasrim kostasrim merged commit 739bee5 into main Jan 8, 2025
9 checks passed
@kostasrim kostasrim deleted the kpr4 branch January 8, 2025 08:46
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