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

Lucene cannot process a conversation and crashes #4180

Closed
AitorAlgorta opened this issue Sep 25, 2024 · 0 comments · Fixed by #4181
Closed

Lucene cannot process a conversation and crashes #4180

AitorAlgorta opened this issue Sep 25, 2024 · 0 comments · Fixed by #4181
Assignees
Labels

Comments

@AitorAlgorta
Copy link
Contributor

Describe the bug

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:

  1. Installed Airy using the standard installation instructions.
  2. Created conversations through the app, then tried to run Kafka Streams to restore state.
  3. 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant