You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some conversations in the DocumentMapper class are being passed as null, which is causing unexpected behavior in the application when trying to index them in Lucene.
To Reproduce
Steps to reproduce the behavior:
Installed Airy using the standard installation instructions.
Created conversations through the app, then tried to run Kafka Streams to restore state.
Observed that some conversations are null, leading to errors during the restore process and indexing.
Expected behavior
Conversations should not be passed as null. Proper validation should be implemented to handle cases where conversations are missing or incomplete without breaking the state restoration process.
Screenshots
N/A
Additional context
The issue is affecting the fromConversationIndex method in DocumentMapper.java, where some conversations lack required fields such as id, channelId, and createdAt.
Logs show NullPointerExceptions when attempting to index conversations with missing data.
The text was updated successfully, but these errors were encountered:
Describe the bug
Some conversations in the
DocumentMapper
class are being passed asnull
, which is causing unexpected behavior in the application when trying to index them in Lucene.To Reproduce
Steps to reproduce the behavior:
null
, leading to errors during the restore process and indexing.Expected behavior
Conversations should not be passed as
null
. Proper validation should be implemented to handle cases where conversations are missing or incomplete without breaking the state restoration process.Screenshots
N/A
Additional context
fromConversationIndex
method inDocumentMapper.java
, where some conversations lack required fields such asid
,channelId
, andcreatedAt
.NullPointerExceptions
when attempting to index conversations with missing data.The text was updated successfully, but these errors were encountered: