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
Is your feature request related to a problem? Please describe.
when you upgrade to tempo 2.0 the format changes to parquet, but the old blocks remain in the previous format meaning that those blocks aren't available to query using traceql
today this returns a nondescriptive error when trying to query.
the error is "query error upstream: (500) Unsupported"
Describe the solution you'd like
return a more descriptive error outlining you can only query the data that is ingested post upgrade
or add a little info icon that on hover tells you this
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had any activity in the past 60 days.
The next time this stale check runs, the stale label will be removed if there is new activity. The issue will be closed after 15 days if there is no new activity.
Please apply keepalive label to exempt this Issue.
This issue has been automatically marked as stale because it has not had any activity in the past 60 days.
The next time this stale check runs, the stale label will be removed if there is new activity. The issue will be closed after 15 days if there is no new activity.
Please apply keepalive label to exempt this Issue.
Is your feature request related to a problem? Please describe.
when you upgrade to tempo 2.0 the format changes to parquet, but the old blocks remain in the previous format meaning that those blocks aren't available to query using traceql
today this returns a nondescriptive error when trying to query.
the error is "query error upstream: (500) Unsupported"
Describe the solution you'd like
return a more descriptive error outlining you can only query the data that is ingested post upgrade
or add a little info icon that on hover tells you this
The text was updated successfully, but these errors were encountered: