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

Command Migration: ('JSON.RESP', 'JSON.DEBUG', 'JSON.INGEST') #1030

Closed
4 tasks
AshwinKul28 opened this issue Oct 8, 2024 · 11 comments · Fixed by #1277
Closed
4 tasks

Command Migration: ('JSON.RESP', 'JSON.DEBUG', 'JSON.INGEST') #1030

AshwinKul28 opened this issue Oct 8, 2024 · 11 comments · Fixed by #1277
Assignees
Labels
migration -- command Migrates current eval to a refactored eval for all protocols functionality

Comments

@AshwinKul28
Copy link
Contributor

This issue tracks the migration of the mentioned commands - ('JSON.RESP', 'JSON.DEBUG', 'JSON.INGEST') to make them compatible across the three protocols supported by the Dice database: RESP, HTTP, and WebSocket.
DiceDB now supports more than one protocols (Resp/http/websocket). We don't want eval operation of each command to be strictly bound with any of the protocols. Currently eval function return statements of each command is bounded to the RESP protocol.

The migration is required because:

  • The current implementation is specific to the RESP protocol
  • Evaluation functions of each command must be refactored to ensure protocol-agnostic behavior.
  • Evaluation functions should return raw responses instead of protocol specific responses.

The goal is to make the command logic protocol-independent, allowing all three protocols to call the same core functionality seamlessly.

Requirements

  • Refactor the evaluation function of [Command Name] to be generic.
  • Ensure the evaluation function does not include protocol-specific logic.

Migration Steps

  1. Analyze Current Implementation

    • Review the current codebase to understand how the command logic is implemented.
  2. Refactor Return Logic

    • Create a new function with the function definition as evalXXX(args []string, store *dstore.Store) *EvalResponse under the file /internal/eval/store_eval.go
    • Analyse return statements of the eval and modify them to send raw types without encoding
    • Use errors in the return statements from /errors/migrated_errors.go file
    • Use perdefined responses from /internal/clientio/resp.go file as RespType variables
  3. Command/Worker specific Changes

    • Make IsMigrated flag to true in the commands information under /internal/eval/commands.go file.
    • Use the newly written eval function against the NewEval parameter in the same command structure.
    • Delete the old eval function from the /internal/eval/eval.go file.
    • Add the migrated command to the /internal/worker/CommandsMeta map and make it's type as SingleShard
  4. Update Unit Tests

    • Refactor existing unit tests to accommodate the new implementation.
    • Add new unit tests if necessary to cover all possible cases.
  5. Integration Tests

    • Run all integration tests to ensure successful migration.
    • Ensure that each protocol (RESP, HTTP, WebSocket) works correctly after migration.

Checklist

  • Migrated the evalXXX function with the latest definition
  • Update or add unit tests for the new implementation.
  • All unit tests pass successfully.
  • Ensure all integration tests pass successfully.

Additional Notes

  • Describe any edge cases that need to be handled in the generic function.
  • Mention any protocol-specific optimizations required in wrappers.

If there are any questions or concerns about this migration, please mention them here.

Related Issues/PRs

  • Sample implementation for the Get, Set, GetSet and SetEx can be found in this Pull Request.
@ayushsatyam146
Copy link
Contributor

I can take this up @AshwinKul28

@AshwinKul28
Copy link
Contributor Author

Hey @ayushsatyam146 assigned the other one to you!

@HarshKhatore
Copy link

Hi, can I try this one?

@lucifercr07
Copy link
Contributor

@HarshKhatore assigned, thanks for contributing.

@AshwinKul28
Copy link
Contributor Author

HI @HarshKhatore , I hope you are doing well. Do you happen to have any updates on this? If you've any doubts please let us know on the discord.

@HarshKhatore
Copy link

Hi @AshwinKul28 , apologies for the delay, I will work on this issue this week and let you know for any questions, thanks.

@AshwinKul28
Copy link
Contributor Author

Hey @HarshKhatore hope you are doing well, can you please update on the current progress of this task? If you have any blockers feel free to discuss here or on the discord.

@soumya-codes soumya-codes added the migration -- command Migrates current eval to a refactored eval for all protocols functionality label Oct 17, 2024
@mohit-nagaraj
Copy link
Contributor

Hey @HarshKhatore whts the update

@HarshKhatore
Copy link

Hi, I will commit a draft PR by today, thanks.

@c-harish
Copy link
Contributor

Hi, @HarshKhatore. Are you still working on this? If not, I can pick this up.

@apoorvyadav1111
Copy link
Contributor

Hi @c-harish , thanks for picking this up. Please refer to #1226 as some of the commands are part of the PR. Please migrate the ones remaining.

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
migration -- command Migrates current eval to a refactored eval for all protocols functionality
Projects
None yet
8 participants