You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original install method (e.g. download page, yum, from source, etc.): Selected 5.0.0-SNAPSHOT on staging-cloud.elastic.co (I'll try to reproduce locally after I get the details into this issue).
Description of the problem including expected versus actual behavior:
On 4.6.1
Create scripted field 'total2x' = doc['total_counter'].value*2;
Verify the field is visible in Discover and shows the total_counter value * 2;
Create a Data Table Visualization based on a new search of index pattern 'test8' and change the Metric Aggregation from Count to Average, and then select the scripted field 'total2x'. Split Rows on Date Histogram. On 4.6.1 it works. On 5.0.0-rc1 build 3, the scripted field does not appear in the list;
Here's a screenshot of the Data Table Visualization Metric list without 'total2x' in it;
I tried in 5.0 using the scripted field as 'expression' and 'painless' with the same results (works in Discover but not in Visualization metric aggregation).
Even if I pick the 'Unique Count' aggregation (which shows Date, Number, and String types) it still does not show the scripted field in 5.0.
Errors in browser console (if relevant): none
Provide logs and/or server output (if relevant):
The text was updated successfully, but these errors were encountered:
Kibana version: 5.0.0-rc1 build 3
Elasticsearch version: 5.0.0-rc1 build 3
Server OS version: Elastic Cloud
Browser version: Chrome
Browser OS version: Windows
Original install method (e.g. download page, yum, from source, etc.): Selected 5.0.0-SNAPSHOT on staging-cloud.elastic.co (I'll try to reproduce locally after I get the details into this issue).
Description of the problem including expected versus actual behavior:
On 4.6.1
Steps to reproduce:
doc['total_counter'].value*2
;Errors in browser console (if relevant): none
Provide logs and/or server output (if relevant):
The text was updated successfully, but these errors were encountered: