Skip to content

Conversation

@Nimesh-0000
Copy link

Fix the issue where browser-generated UUIDs can have duplicates due to browser limitations, causing data loss in BanyanDB's Measure module (which doesn't support updates).

Solution:
Modified BrowserErrorLogRecord#id() to generate a composite internal ID combining the browser-provided uniqueId with the timestamp. This ensures each error log entry has a unique storage ID even if browser UUIDs collide.

Changes:

  • Modified BrowserErrorLogRecord.java to use {uniqueId}_{timestamp} for internal ID.
  • Updated browser-protocol.md documentation.
  • Added BrowserErrorLogRecordTest.java unit tests to verify uniqueness.

Related: Browser logs issue with duplicated UUID.

@wu-sheng
Copy link
Member

wu-sheng commented Jan 7, 2026

That issue targets BanyanDB instead of OAP to resolve this.

@wu-sheng wu-sheng closed this Jan 7, 2026
@wu-sheng
Copy link
Member

wu-sheng commented Jan 7, 2026

Please notice the issue title prefix and milestone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants