Uploaded image for project: 'Red Hat Internal Developer Platform'
  1. Red Hat Internal Developer Platform
  2. RHIDP-10743

Spike: investigate how to save chat history in road-core

    • Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • RHDHPAI Sprint 3266

      Task Description (Required)

       

      road-core how have chat history cache, but it's only used to be passed back to llm server upon chat quey request. there is no way to retrieve all conversations and their history

      https://github.com/road-core/service/blob/main/ols/src/cache/cache.py

      for each cache entry, it's a combination of query & response string, and also the attachement:
      https://github.com/road-core/service/blob/3ea924f4945c0677e3ba8576161b37fb14b15075/ols/app/models/models.py#L521-L569

       

      in RHDH lightspeed chat history, https://github.com/redhat-developer/rhdh-plugins/blob/main/workspaces/lightspeed/plugins/lightspeed-backend/src/handlers/chatHistory.ts
      we are able to retrieve all conversations and their history
      in addition, we store each single message as an entry, and it contains the conversation summary and also timestamp and model-info metadata

       

      This issue is to investigate what changes are needed in road-core to store what we expect. also functions required to retrieve conversations for a particular user and detailed chat history

       

       

      If this requires Change Management, complete sections below: 

      Change Request 

       

      <Select which item is being changed>

       

      [ ]  Add New Tokens

      [ ]  Rotate Tokens

      [ ]  Remove Tokens

      [ ] Others: (specify)

       

        Environment

      <Select which environment the change is being made on.  If both, open a separate issue so changes are tracked in each environment>

       

      [ ]  Stage OR

      [ ]  Prod

       

        Backout Plan

      <State what steps are needed to roll back in case something goes wrong>

       

        Downtime

      <Is there any downtime for these changes?  If so, for how long>

       

        Risk Level

      <How risky is this change?>

       

        Testing

      <How are changes verified?>

       

        Communication

      <How are service owners or consumers notified of these changes?>

              yangcao Stephanie Cao
              yangcao Stephanie Cao
              RHDH AI
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: