i upgraded to the newest Kibana version to use the new Controls.
I have a runtime field in my Data View that gets a value from the indexname:
It can be used in all visualizations without problems. I tried to add a Control for it:
But it does not show any options:
Is this still an issue with the new Controls?
I tried it with the deprecated input controls and it is working as expected:
So this seems to be a problem with the new Controls.
Am i the only one having this issue? Is it known?
I can not find any further information.
Agree I would expect it to be there....
I tested with a runtime I defined in the data view I saw the same behavior... not showing in dropdown.
I added to the actual mapping and it worked
bug / feature I asked internally, but that would be the work around.
"source": """emit((doc['dept'].value) + " : " + (doc['value'].value))"""
And it worked as expected....
Update:There is already an issues to get this solved, I can not promise a release but I was told it was "prioritized"
Thanks, i didn't even know you could give a source script for a field mapping. So is this a scripted field which will be deprecated in the future, or a runtime field, or neither?
That above is a new runtime field... Basically the newer better version of a scripted field and is the go forward method.
Me too... I'm on v8.4.3 of ES.
I switched to new controls as "suggested" by the GUI and discovered for this issue...
A little bit surprise of this.
I hope this will be solved ASAP.
Thank you for any effort the Elastic Team can put on this fix!
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.