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

Drop sharding rule, add relation definitions to dataspace #416

Draft
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

reshke
Copy link
Collaborator

@reshke reshke commented Jan 18, 2024

In this pr we replace current routing logic based on sharding rules with new one, based on dataspaces.

refer
#431

@EinKrebs
Copy link
Collaborator

Consider deprecating sharding rules instead of dropping them

@reshke
Copy link
Collaborator Author

reshke commented Jan 18, 2024

sharding rules dropped from SQL api, however they still present in grpc API and in backend code

@EinKrebs EinKrebs self-requested a review January 18, 2024 12:08
@EinKrebs EinKrebs mentioned this pull request Jan 19, 2024
@@ -192,7 +189,8 @@ func (qr *ProxyQrouter) RouteKeyWithRanges(ctx context.Context, expr lyx.Node, m
spqrlog.Zero.Debug().Str("key", string(meta.params[e.Number-1])).Str("hashed key", string(hashedKey)).Msg("applying hash function on key")

return qr.DeparseKeyWithRangesInternal(ctx, string(hashedKey), meta)
case *lyx.AExprConst:
case *lyx.AExprIConst:
if
Copy link
Collaborator

Choose a reason for hiding this comment

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

Incorrect if

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

yea...
just pushed a bunch of work

@reshke reshke marked this pull request as draft January 19, 2024 12:27
@reshke
Copy link
Collaborator Author

reshke commented Jan 21, 2024

I would like to propose to use only one bound in key range (lower one). To check if given key lays within given keyrange we will only have to check that given key is greater (>=) then KR bound and no other (greater) key range satisfies the same.

@EinKrebs
Copy link
Collaborator

@reshke PR is obsolete, consider closing it

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.

None yet

2 participants