spring-projects / spring-projects/spring-ai
chatMemory.get(conversationId) returns unexpected timestamp
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.5k
- Forks
- 2.9k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 6
Description
Spring AI Version: 1.0.0-RC1
chatMemory.get(conversationId) returns
[
{
"messageType": "USER",
"metadata": {
"CassandraChatMemoryRepository_message_timestamp": 1747564565.737000000,
"messageType": "USER"
},
"media": [],
"text": "SSE development using springboot?"
},
{
"messageType": "ASSISTANT",
"metadata": {
"CassandraChatMemoryRepository_message_timestamp": 1747564594.962000000,
"messageType": "ASSISTANT"
},
"toolCalls": [],
"media": [],
"text": "..."
}
]
where
var chatMemory = MessageWindowChatMemory.builder() .chatMemoryRepository(this.cassandraChatMemoryRepository).build();
I did look into ai_chat_memory and found something different. By different I meant values of msg_timestamp have three more digits, similar to:
[{msg_timestamp:1747579713040,msg_type:'USER',msg_content:'Hello'}, {msg_timestamp:1747579718473,msg_type:'ASSISTANT',msg_content:'Hello'}]
@michaelsembwever
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting CassandraChatMemoryRepository and the ai_chat_memory schema or stored msg_timestamp values. Compare the timestamp representation returned by chatMemory.get(conversationId) with the persisted values, then verify that the returned timestamps use the expected precision and units.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cassandra, java, spring
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100