-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[XY] Expression unification #127115
Comments
Pinging @elastic/kibana-presentation (Team:Presentation) |
Lens should support palette expression function already: Add support of palette expression function instead of string
What exactly is this referring to? |
@flash1293, there is such expression chain:
These filters are applied to the datasource expressions, like I don't remember the code of those expressions, so, need to investigate it when the time will come and propose the useful solution in case of the troubles. |
I see, for Lens this wouldn't be relevant because we aren't manipulating filters this way (it's just the kibana context, then esaggs). I see it being relevant for Canvas. |
Yes. And this ability is provided by the data plugin and we were moving the canvas in this direction not so long time ago. As I understand, a lot of parts of Kibana will rely on it in the future, as the only way of manipulating filters. |
Plan
xy_vis
andlens_xy_chart
configuration possibilities with highlighting missing features - [XY] Adapt forxyVis
. #127712 (author: @VladLasitsa)Additional types for the existing arguments
palette
type fromstring
topalette
- [XY]system_palette
andpalette
support. #128053 (author: @Kunzetsov).visdimension
at fields:splitAccessor
,accessors
,xAccessor
. - [XY] Supportvis_dimension
type for accessors #129612 (author: @VladLasitsa)Global features, required for using xy in Lens/VisTypes/Canvas.
xyVis
andlayeredXyVis
layers. #128056 - [XY]xyVis
andlayeredXyVis
. #128255 (author: @Kunzetsov)filters
are applied to the expression functions, executed at thetable
arguments of thelayers
. (author: @Kunzetsov)minTimeBarInterval
arg #128726 (author: @VladLasitsa)pointseries
input type as possible toxyVis
. Add default accessors and make them optional toxyVis
, if the input type ispointseries
, as mentioned in the xy vis proposal. - [XY] Add support ofpointseries
input type #131919 (author: @VladLasitsa)Missing features, required at VisEditors
xy
implementationsplitRowDimension
,seriesDimension
, zDimension. (author: @Kunzetsov)splitRowAccessor
andsplitColumnAccessor
- allow split by row and column (inxy_vis
-Split chart
) ([XY]xyVis
split chart. #130229)dataLayer.splitAccessor
- allow multiple split accessors for one layer. [XY] Allow multiple split accessors #134566 (author: @VladLasitsa)zDimension
- allow to provide field name of mark size metric onDatum
. Only used with line/area series. Add support to define size ratio forzDimension
. (radiusRatio
arg) - ([XY] Mark size configuration. #130361)seriesParams
args:showCircles
,lineWidth
,circlesRadius
) - ([XY]pointsRadius
,showPoints
andlineWidth
. #130391)seriesParams
arg:drawLinesBetweenPoints
) - ([XY] Lines visibility at the lines chart. #130452)addTimeMarker
arg) - ([XY] AddaddTimeMarker
arg #131495) (author: @VladLasitsa)orderBucketsBySum
(allow to order ordinal x values by descending) - ([XY]orderBucketsBySum
added. #130457)addTooltip
arg) - ([XY]showTooltip
argument. #130530)detailedTooltip
arg) - ([XY] Detailed tooltip. #131116)categoryAxes
are x - axes,valueAxes
are y-axes): - [XY] Addaxes
support #129476 (author: @VladLasitsa)categoryAxes.scale.mode/valueAxes.axisParams.scale.mode
arg)categoryAxes.position/valueAxes.axisParams.position
arg)categoryAxes.scale.boundsMargin/valueAxes.axisParams.scale.boundsMargin
arg)categoryAxes.labels.color/valueAxes.axisParams.labels.color
arg)categoryAxes.labels.filter/valueAxes.axisParams.labels.filter
arg)categoryAxes.labels.truncate/valueAxes.axisParams.labels.truncate
arg)xyVis
. #132192, [XY] Reference lines overlay fix. #132607Final steps of the plan
cc @crob611, @stratoula, @flash1293, @alexwizp, @VladLasitsa
co-author: @VladLasitsa.
The text was updated successfully, but these errors were encountered: