Skip to content
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

Allow running a set of existing queries (e.g. dashboard) on another table #72

Open
mastropi opened this issue Feb 18, 2020 · 0 comments
Labels
enhancement New feature or request nice to have

Comments

@mastropi
Copy link
Collaborator

Goal: Apply an existing search, visualization, or dashboard to a table with the same columns but with another set of data (e.g. a table that contains data collected on a different date than the original table; or the same table that now sits on a different database (e.g. Oracle vs. SQLite)).

Application: For testing purposes I wanted to re-generate the INCOME Example dashboard on the SQL Server database, based on the dashboard already generated on the SQLite database. In order to do this, I had to regenerate each of the 10+ visualizations present in the dashboard, one by one, by repeating the visualization creation process that had been performed on the SQLite table (with possible errors when trying to reproduce the exact visualization), and recreate the dashboard by selecting those visualizations.
In the end, I did not generate all the dashboard, but just 3 selected visualizations present in it.

Notes on implementation:

  • The interface should allow the user to select a different table on which the search, visualization, or dashboard should be constructed.
  • The information on the newly selected table would then impact the request body received by the server as part of the _msearch URL triggering the search, visualization, or dashboard. where the table name is given as the value of the index attribute. This information is then processed by the backend inside the processQueries() function in functionsquery.php
  • No change is expected to be necessary on the backend, since the backend will simply process the new request sent to the server containing the name of the table on which the request should be carried out.
@mastropi mastropi added enhancement New feature or request nice to have labels Feb 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request nice to have
Projects
None yet
Development

No branches or pull requests

1 participant