[v10.2.x] InfluxDB: Parse data for table view to have parity with frontend parser #78551
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport c5f3ce1 from #78365
What is this feature?
InfluxDB has a frontend response parser which will be not used as we are moving towards backend migration. This means the query will be fetched and parsed on the backend and will return as
DataFrame
.The current data format is compatible with
timeseries
but not with thetable
view %100.Users have to use
transformations
and other techniques to reach to same view as they had before.This is a tedious process to go through. This PR is resolving that by adding a separate parsing logic for table view.
Part of #65045
Frontend Mode
Backend Mode before PR
Backend Mode after PR
Why do we need this feature?
To have parity with frontend parser and no breaking changes while having
influxdbBackendMigration
feature toggle enabled.Who is this feature for?
InfluxDB
influxql
users who have table views in their dashboardsHow to test
dashboard.json for testing
influxdbBackendMigration
feature toggle falseinfluxql
which has table.influxdbBackendMigration
feature togglePlease check that: