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

[draft]feat: refactor Lock and Projection #180

Closed

Conversation

kubeJocker
Copy link
Contributor

@kubeJocker kubeJocker commented Jul 4, 2023

fix #106
fix #108
fix #143

@kubeJocker kubeJocker changed the title feat: refactor Lock and Projection [draft]feat: refactor Lock and Projection Jul 4, 2023
@kubeJocker kubeJocker requested a review from earayu July 5, 2023 01:48
@kubeJocker kubeJocker marked this pull request as ready for review July 7, 2023 02:07
@kubeJocker kubeJocker force-pushed the feature/refactor-Lock-and-Projection branch from 4da7a3f to c236750 Compare July 12, 2023 08:11
}
}
reservedID := info.reservedID

Copy link
Collaborator

Choose a reason for hiding this comment

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

I think it's better to check lockName must be literal in planner stage

@@ -233,6 +246,9 @@ func (stc *ScatterConn) ExecuteMultiShard(
alias = state.TabletAlias
})
}
if reservedID != 0 {
setLockSession(send, innerqr, session, queries[i].BindVariables, rs.Target, reservedID, alias)
}
Copy link
Collaborator

Choose a reason for hiding this comment

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

I don't feel it's a good idea to reserve a connection in case nothing

@earayu earayu closed this Jul 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants