Skip to content

Fix/public traces postgres read#9

Merged
krishna-yb merged 6 commits intomekodata-26-03-13from
fix/public-traces-postgres-read
Mar 30, 2026
Merged

Fix/public traces postgres read#9
krishna-yb merged 6 commits intomekodata-26-03-13from
fix/public-traces-postgres-read

Conversation

@krishna-yb
Copy link
Copy Markdown

What does this PR do?

Fixes # (issue)

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • Chore (refactoring code, technical debt, workflow improvements)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Refactor (does not change functionality, e.g. code style improvements, linting)
  • This change requires a documentation update

Mandatory Tasks

  • Make sure you have self-reviewed the code. A decent size PR without self-review might be rejected.

Checklist

  • I haven't read the contributing guide
  • My code doesn't follow the style guidelines of this project (pnpm run format)
  • I haven't commented my code, particularly in hard-to-understand areas
  • I haven't checked if my PR needs changes to the documentation
  • I haven't checked if my changes generate no new warnings (npm run lint)
  • I haven't added tests that prove my fix is effective or that my feature works
  • I haven't checked if new and existing unit tests pass locally with my changes

Switch GET /api/public/traces to tracingPrisma-backed queries so public trace reads work in Yugabyte/Postgres-only deployments without ClickHouse.
Route public observations by-id and filter paths through PostgreSQL-safe logic, and align related web/shared/worker typing and lint fixes so root-path API behavior and validation are consistent end-to-end.
@krishna-yb krishna-yb marked this pull request as ready for review March 30, 2026 15:12
@krishna-yb krishna-yb merged commit 36dc486 into mekodata-26-03-13 Mar 30, 2026
2 checks passed
@ashetkar ashetkar deleted the fix/public-traces-postgres-read branch March 31, 2026 05:10
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.

1 participant