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

tracking: http handler txn support. #14789

Open
11 of 13 tasks
youngsofun opened this issue Feb 29, 2024 · 3 comments
Open
11 of 13 tasks

tracking: http handler txn support. #14789

youngsofun opened this issue Feb 29, 2024 · 3 comments

Comments

@youngsofun
Copy link
Member

youngsofun commented Feb 29, 2024

Summary

make sure:

  • without txn
    • old clients can work with new server
    • new clients can work with old server

steps:

@youngsofun
Copy link
Member Author

youngsofun commented Feb 29, 2024

  • old server: user get error when exec Begin
  • old client + new server: Begin/ commit / rollback may success, but txn is not working,
    • client may need to send version or capability to resolve this?

for the .session, it is better for clients to decode and save it as JSON Ast instead of struct, and send to server as it is in next query.
if some field is needed by the client, decode and get them separately. 2 advantages

  1. not compatibility issue when new field is added to the session state
  2. some field is that client do not care can be ignored when decoding to struct.

I will try this later

@hantmac
Copy link
Member

hantmac commented Mar 4, 2024

  • old server: user get error when exec Begin

  • old client + new server: Begin/ commit / rollback may success, but txn is not working,

    • client may need to send version or capability to resolve this?

for the .session, it is better for clients to decode and save it as JSON Ast instead of struct, and send to server as it is in next query. if some field is needed by the client, decode and get them separately. 2 advantages

  1. not compatibility issue when new field is added to the session state
  2. some field is that client do not care can be ignored when decoding to struct.

I will try this later

@youngsofun Which API need client call when Begin, commit, and rollback? Or use specified SQL ?

@youngsofun
Copy link
Member Author

@hantmac use specified SQL

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

No branches or pull requests

2 participants