m-amano
June 17, 2020, 9:13am
1
I'm using Elasticsearch and Kibana version 7.6.1 which we just upgraded from v.7.6.0 last month.
At that time, Vega version was still v.4.3.0 but v.5.13.0 has been released earlier this month. So I want to use the latest version of Vega and not sure how to update it.
Should I update the same Elasticsearch and Kibana version again to update the Vega version?
I have not personally done this, but it appears it's possible to define a different version of Vega: https://www.elastic.co/guide/en/kibana/current/vega-graph.html#vega-schema
elastic:master ← alexwizp:vega-version
opened 12:24PM - 09 Jun 20 UTC
Looks like it will come out in a future version. Just need to wait.
m-amano
June 18, 2020, 5:44am
4
I believe it was backported to Elasticsearch version 7.x, so that I may check if I can use latest Vega version in Elasticsearch version 7.6.1.
Actually the PR for updating Vega to v5 is this one:
It is merged already and tagged for 7.9 and was backported to the 7.x branch. So let‘s see if it even still makes it into 7.8.x
I don't know if I understand you. The exact backport which is linked as well is like mentioned already this one which was merged 2 days ago.
elastic:7.x ← alexwizp:backport/7.x/pr-68639
opened 09:39AM - 16 Jun 20 UTC
Looking at the releases dates 7.6.1 came out on March 4th.
So this PR cannot be in 7.6.1. Like Aaron said, just be patient, there is no existing release that has Vega 5 up to now. If you want to use it, feel free to checkout the master branch or 7.x branch and compile Kibana and spin up a development version of kibana
# Contributing to Kibana
We understand that you may not have days at a time to work on Kibana. We ask that you read our contributing guidelines carefully so that you spend less time, overall, struggling to push your PR through our code review processes.
At the same time, reading the contributing guidelines will give you a better idea of how to post meaningful issues that will be more easily be parsed, considered, and resolved. A big win for everyone involved! :tada:
## Table of Contents
A high level overview of our contributing guidelines.
- [Effective issue reporting in Kibana](#effective-issue-reporting-in-kibana)
- [Voicing the importance of an issue](#voicing-the-importance-of-an-issue)
- ["My issue isn't getting enough attention"](#my-issue-isnt-getting-enough-attention)
- ["I want to help!"](#i-want-to-help)
- [How We Use Git and GitHub](#how-we-use-git-and-github)
- [Forking](#forking)
- [Branching](#branching)
- [Commits and Merging](#commits-and-merging)
- [Rebasing and fixing merge conflicts](#rebasing-and-fixing-merge-conflicts)
- [What Goes Into a Pull Request](#what-goes-into-a-pull-request)
show original
# Contributing to Kibana
We understand that you may not have days at a time to work on Kibana. We ask that you read our contributing guidelines carefully so that you spend less time, overall, struggling to push your PR through our code review processes.
At the same time, reading the contributing guidelines will give you a better idea of how to post meaningful issues that will be more easily be parsed, considered, and resolved. A big win for everyone involved! :tada:
## Table of Contents
A high level overview of our contributing guidelines.
- [Effective issue reporting in Kibana](#effective-issue-reporting-in-kibana)
- [Voicing the importance of an issue](#voicing-the-importance-of-an-issue)
- ["My issue isn't getting enough attention"](#my-issue-isnt-getting-enough-attention)
- ["I want to help!"](#i-want-to-help)
- [How We Use Git and GitHub](#how-we-use-git-and-github)
- [Forking](#forking)
- [Branching](#branching)
- [Commits and Merging](#commits-and-merging)
- [Rebasing and fixing merge conflicts](#rebasing-and-fixing-merge-conflicts)
- [What Goes Into a Pull Request](#what-goes-into-a-pull-request)
show original
m-amano
June 23, 2020, 1:56am
6
Thank you for your info.
system
July 21, 2020, 1:56am
7
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.