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

[Lens] Architectural requirements for calculations #68460

Closed
wylieconlon opened this issue Jun 5, 2020 · 2 comments
Closed

[Lens] Architectural requirements for calculations #68460

wylieconlon opened this issue Jun 5, 2020 · 2 comments
Labels
enhancement New value added to drive a business result Feature:Lens Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@wylieconlon
Copy link
Contributor

The most important requirement is the ability to have hidden data that is not being visualized. This data is used to calculate the final visualization. For example, if I have columns a and b, and I want to visualize a + b only, I need a way to hide the inputs. By supporting hidden data, we let the user build the visualization in steps. This makes Lens learnable.

The second most important requirement is the ability to join two tables. Without this ability, there is a huge limit on what users can express with their calculations. For example, joining will let us do month over month calculations.

The third most important requirement is the ability to apply lazily evaluated functions to the table. By building a set of generic table manipulation functions, as well as a set of generic functions to handle specific data types like numbers or strings or dates, we can build the standard library that users expect a visualization tool to have. This set of functions should resemble the relational algebra: selection, projection, filtering, and renaming are core concepts.

Finally, the Lens editor needs to take a more active role in the data flow and editing. This will let us keep the same functionality regardless of the datasource: for example, this will let us combine aggregated data with SQL data in the client.

@wylieconlon wylieconlon added Team:Visualizations Visualization editors, elastic-charts and infrastructure Feature:Lens labels Jun 5, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app (Team:KibanaApp)

@wylieconlon
Copy link
Contributor Author

Closing this because it doesn't give enough detail to the point where we can't implement it. Many of the topics have separate issues, for example the more detailed issue for "hidden data" is about changing the operations API in the datasource.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Feature:Lens Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Development

No branches or pull requests

3 participants