-
Notifications
You must be signed in to change notification settings - Fork 34
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
Announcement : contributors needed to upgrade to new Kibana versions #62
Comments
Hey guys :) I'm working on the migration for Kibana 7.5.0 and I need some helps. So this is a git patch to apply on datasweet plugin To apply it, you have to :
|
Hi ! This is a new patch for kibana 7.6.1 : The installation instructions are :
This patch :
|
Hello, Is the 7.6.1 version of the plugin also compatible with Kibana 7.6.2 or does it need changes? Asking as we've installed the plugin on 7.6.2 however we cannot see it inside the visualization builder nor in the status page listed in the Kibana plugin list
Thanks |
Yes, I think the patch is compatible with kibana 7.6.2. My installation instructions seems to be unclear because lots of people have issues with the installation of my patch :( First, delete your attempt to avoid conflicts:
Then, use the following commands to install the plugin:
After restarting your kibana, it will work... Of course, you have to replace PATCH_PATH with the path of the extracted patch. |
Sorry
Sorry... For Windows how i can install plugin to kibana 7.6.1? |
Hi all,
We wish you a happy new year! Thanks for using and starring Kibana-datasweet-formula.
We need your help in order to keep up with the release pace of Kibana.
We are very busy on our business, and preparing a release that might change forever the way you query your elasticsearch data.
In the meantime, we want this plugin to keep up with the new Kibana version, but we are not in a position to do that by ourselves.
Are any of you willing to contribute ? If so, please let us know. Support for 7.5 would be the priority.
Best regards
Datasweet team.
The text was updated successfully, but these errors were encountered: