-
Notifications
You must be signed in to change notification settings - Fork 11.6k
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
InfluxDB: Parse data for table view to have parity with frontend parser #78365
Conversation
Hello @itsmylife!
Please, if the current pull request addresses a bug fix, label it with the |
return &v | ||
} | ||
|
||
const tableResultFormatInfluxResponse1 = `{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be better to use the pattern we use in prom here for testing with the json test_data files. I don't think it is a blocker on the PR, but we should probably make an issue to update the tests in this DS.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a good call. I will also refactor the time_series
parsing since we have a lot of duplicate code with this PR. When I do that, I will refactor testing too. I'll create an issue for myself to track this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
…ntend parser (#78551) InfluxDB: Parse data for table view to have parity with frontend parser (#78365) * Use TimeSeriesWide format for table response * fix group by query result parsing * handle labels * provide a test where result has no tags * parsing results without time column * clean the code * remove the comment line * more cleaning * lint (cherry picked from commit c5f3ce1) Co-authored-by: ismail simsek <ismailsimsek09@gmail.com>
…er (#78365) * Use TimeSeriesWide format for table response * fix group by query result parsing * handle labels * provide a test where result has no tags * parsing results without time column * clean the code * remove the comment line * more cleaning * lint
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: