[Lens] Table Allow for Filtering of Rows on the string Column Value(s)

[BenB196]

Describe the feature:

With rows in Lens table, it is currently only possible to filter via an Elasticsearch filter. This has a downside of not being able to filter by the generated column values. It would be nice if you could add filters directly to tables after they have been constructed.

(I recognize that this might enter the realm of multi-part queries if you only use ES, which from my understanding currently isn't possible)

Describe a specific use case for the feature:

Lets say I have a table that looks like the below:

Thing	Count of Thing
Dog	10
Car	20
Chair	5

In Excel I can do things like filter column:

• Thing to only show Dog.
• I can filter to only show rows where Thing starts with the letter C (Car and Chair).
  • Note that this currently isn't possible if you have documents structured like:

{
  "_source": {
    "Thing": ["Dog", "Car"]
  }
  "_source": {
    "Thing": ["Chair", "Car"]
  }
  "_source": {
    "Thing": ["Chair", "Dog"]
  }
}

• As Elasticsearch filtering will return all values of the array. And you will get a row with Dog with count of 2

I can also filter to show only rows with the column value:

• Count of Thing > 7.
• This can be achieved in Lens with custom formulas from what I can tell, but this is not ideal for end users who shouldn't be required to know how to edit visualizations.

[elasticmachine]

Pinging @elastic/kibana-vis-editors @elastic/kibana-vis-editors-external (Team:VisEditors)

[flash1293]

Duplicate of #86190

[BenB196]

@flash1293 I'm not sure if the issue you linked as a duplicate is a true duplicate. While I think it might cover the second use-case:

I can also filter to show only rows with the column value:
Count of Thing > 7.

I don't think it covers the first use-case of being able to filter by the any column, as it seems like the issue you linked is just for numbers, where the first use-case is for text-based column.

Unless this closure is saying there are no plans to add this feature for text.

[flash1293]

@BenB196 Good point - I think this use case is covered by the include/exclude parameters of the terms aggregation. These are not supported in Lens yet (they are available in Visualize), but there's a separate issue here: #96585

Would that cover your use case?

[BenB196]

@flash1293 yes, after looking into it seems like include/exclude parameters would cover the use case here. Though it looks like the old aggregation table won't support my use case, as my table uses Metrics with Filter By's which don't seem to be supported in the old viz's.

Though one thing I would like to see that I don't see in either ticket, is being able to apply the filter adhoc in the visualization itself, so that an end user doesn't need to edit the visualization. Possibly in the table column drop-down:

Have an additional Filter By section, kind of like Excel:

[flash1293]

@BenB196 makes sense, I will reopen, thanks for explaining.

[gueri-fr]

+1

[smnschneider]

+1

[brynnhart]

+1

[markov00]

In order to provide better transparency of priorities, issues that will not be prioritized within the next 24 months are being closed.

Tracking request in Lens general improvements ice box, solvable possibly with ESQL #184648